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: http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x/current/legacy-images/ (notice that <eoan> http://ports.ubuntu.com/ubuntu-ports/dists/eoan/main/installer-s390x still works). As far as I can tell the URL change was done by intention and to indicate that the default installer for 20.04 is no longer d-i, but subiquity. The '--cdrom' is a valid option for many cases, but unfortunately not for all, since it doesn't allow the '-extra-args' argument - '-extra- args' only works in combination with '--location', not with '--cdrom'. I currently see two options, one is renaming the URL back and the second option is to directly specify kernel and initrd, like: ubuntu@s1lp11:~$ virt-install --name ubuntu20-guest1 --memory 4096 --vcpus 4 --disk "size=4" --install kernel=http://ports.ubuntu.com /ubuntu-ports/dists/focal/main/installer-s390x/current/legacy- images/generic/kernel.ubuntu,initrd=http://ports.ubuntu.com/ubuntu- ports/dists/focal/main/installer-s390x/current/legacy- images/generic/initrd.ubuntu --network "network=default" As far as I can tell netboot images/files at 'ports.ubuntu.com' are all d-i only. For subiquity one needs to grab kernel and initrd for potential netbooting from the focal-live-server-s390x.iso or the iso itself. Btw. preseed is the non-interactive installation method based on d-i. With the new subiquity installer the preseed successor is 'autoinstallation' - for more details let me refer to: Automated Server Installs for 20.04 https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls Automated Server Installs Config File Reference https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/ConfigReference JSON Schema for autoinstall config https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/ConfigSchema Autoinstall Quick Start https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/QuickStart Autoinstall Quick Start for s390x https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/QuickStart/s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872941 Title: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Invalid Status in virt-manager package in Ubuntu: New Bug description: Installer version: Latest https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x Description/Reproduction: Start virt-install with the following options: virt-install \ --name ubuntu20-guest1 \ --memory 4096 \ --vcpus 4 \ --disk "size=4" \ --location http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \ --network "network=default" Error: ERROR Error validating install location: Could not find an installable distribution at 'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x' The location must be the root directory of an install tree. See virt-install man page for various distro examples. Looking at previous releases I would guess it expects an "images" directory instead of the new "classic-images" directory. I'm aware of the workaround to specify kernel/initramfs directly but that shouldn't be a solution. == Comment: #2 - Andre Wild1 <andre.wi...@ibm.com> - 2020-04-15 03:51:21 == (In reply to comment #0) > Installer version: Latest > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x > Sorry I've copied the wrong link. This is the link I've used successfully in the past: http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1872941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
