Since there are some discussions about this ticket on other communication channels, I want to clarify and sum up the situation here:
An installation on a DASD disk that is virtio-attached, like: virt-install --name focal --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.1234 --cdrom ./install_image.iso works with d-i since, there is a 'non-standard way' (or one may call it 'hack') to identify that a certain disk that is passed over via virtio is not (as usual) a SCSI disk, but a DASD (based on the partition table). We think that the clean way is to pass/attach DASD disks as ccw devices (what they actually are), but we will look into this, since it worked with d-i. Since this is a non-straight forward way to identify disk geometry, something like this would require 'extra coding' (or again some hacking). However, nobody should be blocked by this, since there is still the focal / 20.04 legacy d-i image available, that allows such virt-install installation, like (in short): virt-install --name focal --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.261e --cdrom ./ubuntu-20.04-legacy-server-s390x.iso (for details see the attachment) Even if the legacy d-i image is based on 20.04 GA, an installation (with access to the archives) will end up as a proper 20.04.1 installation (as of today), since the installer updates by default to the latest package levels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893775 Title: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
