@hws also note that we have patched Ubuntu's virt-install & worked with
upstream on landing things there too.
If one is using non-Ubuntu virt-install, they need to patch it first, to
be usable to deploy focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm not sure what is expected to happen from your side.
The patch is included in virt-manager version 1:2.2.1-3ubuntu2 an newer:
virt-manager (1:2.2.1-3ubuntu2) focal; urgency=medium
* Fix legacy-images path for focal. LP: #1872941
and we got positive feedback that it works.
And I just retried
FYI:
It seems that the issue is still present in the currently available
focal/universe packages:
virt-manager 1:2.2.1-3ubuntu2
If you run into this issue, like I did, the upstream version like Christian
Ehrhardt mentioned above is needed.
See also:
FYI
Upstream implemented it similar in
https://github.com/virt-manager/virt-manager/commit/b55b7e94622dd039d00b6e21b5d28d44ab944693
I submitted the one missing bit in
https://github.com/virt-manager/virt-manager/pull/115
Neither of the above is in a new release yet.
--
You received this
I am working on implementing network config & network .iso discovery
On s390x, when using virt-install, do you really want to configure
networking at all or do you want it to simply dhcp, self-find the right
iso, download that and attempt booting that?
Or do you still want interactive experience
RFE got created: # 141996
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu 20.04] virt-install fails to detect path after images folder
name has changed
To manage
I guess you want for
ftp://cdimage.ubuntu.com/cdimage/releases/20.04/release/ to publish an
.ins file that HMC could load, and then be able to bring up network and
possibly default to said url to use .iso from there to complete the
install.
--
You received this bug notification because you are a
Upstream pull request to resolve this for virt-install is not merged
https://github.com/virt-manager/virt-manager/pull/101
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu
Hi Peter,
for the (s390x) kernel and initrd of d-i (legacy) usage, the URL is still:
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-s390x
The problem was that virt-install expected .../current/images as tail and
refused to work with .../current/legacy-images, but this is solved
hi, all, while reading this thread I can't really follow which link
would work with virt-install.
I've tried all of them but virt-install keep telling there is no distro.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Christian - there is a separate ticket open for this, it's LP 1854513.
May I suggest to leave a comment there and/or clicking the link "Does this bug
affect you?" at the top left? That would be helpful - thank you!
--
You received this bug notification because you are a member of Ubuntu
I think that's a brilliant question.
I can go on explaining that how we build & publish the new thing, is
unlike how we build and publish the old thing, and that it's all a bit
non-trivial, but literary that's all irrelevant from the virt-install
users' point of view.
We are discussing subiquity
** Changed in: ubuntu-z-systems
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu 20.04] virt-install fails to detect path after images
If the legacy d-i netboot images are not going to be published/supported
20.04.1 onwards, do we have an equivalent replacement that's able to perform
the same function?
The mini.iso allows me to boot my 384 Mb ram VPS without a cd-rom drive
into the installation environment by just loading the
This bug was fixed in the package virt-manager - 1:2.2.1-3ubuntu2
---
virt-manager (1:2.2.1-3ubuntu2) focal; urgency=medium
* Fix legacy-images path for focal. LP: #1872941
-- Dimitri John Ledkov Fri, 17 Apr 2020 18:26:25
+0100
** Changed in: virt-manager (Ubuntu)
** Changed in: ubuntu-z-systems
Assignee: Canonical Server Team (canonical-server) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu 20.04] virt-install
** Description changed:
+
+ For 20.04.0 d-i is changing from /images/ to /legacy-images/ in it's
directory structure.
+
+ For 20.04.1+ it will not exist at all.
+
+ For all Ubuntu releases virt-install should learn how to use cloud-
+ images from https://cloud-images.ubuntu.com/ which are
** Changed in: virt-manager (Ubuntu)
Status: Invalid => Confirmed
** Changed in: virt-manager (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately installer-arch/ is hardcoded portion of the prefix in the
internal archive publishing, internal mirroring, and external mirroring,
thus I cannot change it to legacy-installer-arch.
Also these will only exist for a short period of time until June, so I
don't see the point of
** Branch linked: lp:~xnox/debian-installer/legacy-installer-arch-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu 20.04] virt-install fails to detect path after images
** Branch linked: lp:~xnox/debian-cd/legacy-installer-arch-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu 20.04] virt-install fails to detect path after images folder
Frank pointed out that virt-install uses:
--location http://ports.ubuntu.com/ubuntu-ports/dists/focal/main
/installer-s390x
Meaning, it is sensitive to "/images/" changing to "/legacy-images/".
However, instead of changing images to legacy-images, we could instead
change "installer-" prefix to
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu 20.04] virt-install fails to detect path after images folder
name has changed
To manage
Renaming the artefacts was a compromise. the other option was to not
publish them at all.
d-i artefacts will not exist for 20.10 release, nor for 20.04.1 release,
on any architecture. Thus renamed d-i artefacts is a transitional period
of ~3 months until 20.04.1 is released.
cloud-images for
** Also affects: ubuntu-cdimage
Importance: Undecided
Status: New
** Changed in: ubuntu-cdimage
Status: New => Opinion
** Changed in: virt-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The URL is changed intentionally, to notify all users that these images
are deprecated and will not be updated after 20.04.0 GA, and will no
longer be published in the future.
You should not be using virt-install, and simply boot the s390x cloud-
image in-place, with suitable cloud-config drive
First of all, both examples from comment #3 work (subiquity also
installs that way).
I guess it's obvious that the '--location' doesn't work with the directory tree
anymore due to the change in the URL from
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x/current/images/
to:
Agreed @cborntra, if that is your use case then those two ways are not
equivalent.
Then for now I only know of the "workaround to specify kernel/initramfs
directly" that you are aware of as well.
Let's see what feedback Andrew gets when asking to change the path back.
--
You received this bug
Actually the following works pretty well for getting to the old-style installer
on s390x.
Instead of a location to the install-dir, just hand it an ISO (can also be a
local file).
virt-install --name ubuntu20-guest1 --memory 4096 --vcpus 4 --disk
"size=4" --cdrom
in the function _set_url_paths it makes up the defaults:
# generic
url_prefix = "current/images"
...
# s390x specific as it can't find "normal" kernel/initrd there
hvmroot = "%s/generic/" % url_prefix
kernel_basename = "kernel.%s" % self._debname
That will construct
Note that the virt-manager package is in the "universe" archive.
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Server Team (canonical-server)
** Changed in: ubuntu-z-systems
Importance: Undecided => Critical
** Also affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872941
Title:
[Ubuntu 20.04] virt-install fails to detect path after
33 matches
Mail list logo
