[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
** No longer affects: subiquity (Ubuntu) ** No longer affects: subiquity (Ubuntu Focal) ** No longer affects: subiquity (Ubuntu Groovy) ** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- 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/subiquity/+bug/1893775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
** Also affects: subiquity Importance: Undecided Status: New ** Changed in: subiquity Status: New => In Progress ** Changed in: subiquity Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson) -- 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/subiquity/+bug/1893775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
** Attachment added: "virt-install_with_legacy d-i-image.txt" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893775/+attachment/5427706/+files/virt-install_with_legacy%20d-i-image.txt -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
** Tags added: fr-662 -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
It seems from a quick look that parted just embeds a (ancient) copy of fdasd to do the identification, so I don't think there's any real benefit to using parted over fdasd directly. It would really be more in keeping with how we expect things to work to have a udev rule that would run fdasd on block devices and record in udev somehow if they are dasds and maybe that's something we should work towards in 21.04 but maybe we should also think of a way to make this work in focal (starting by making changes to probert, I guess). -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
So the history of this msdos/dasd partitioning table stuff in the old installer were as follows: LTC-135429 https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1534629 LTC-136054 https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1527328 https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1537942 LTC-137464 https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411 LTC-149975 https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1650300 https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1595495 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815916 partman-partitioning (110ubuntu3) xenial; urgency=medium * Set s390x partitioning tables (parted label type) to dasd. LP: #1534629, LP: #1527328, LP: #1537942. -- Dimitri John Ledkov Tue, 09 Feb 2016 19:32:43 + partman-partitioning (110ubuntu4) xenial; urgency=medium [ Viktor Mihajlovski ] * Revert to using msdos partitioning table on s390x as a fallback, however use dasd partitioning table if advised to do so by partman. LP: #1548411 -- Dimitri John Ledkov Mon, 29 Feb 2016 14:27:51 + partman-partitioning (112ubuntu1) yakkety; urgency=medium * Resynchronise with Debian. Remaining changes: - On s390x use msdos partition table by default, unless partman advises dasd. -- Dimitri John Ledkov Fri, 12 Aug 2016 09:52:51 +0100 But also this: partman-base (190) unstable; urgency=medium [ Viktor Mihajlovski ] * Add disk label type to device directory, such that e.g. partman-partitioning can elect dasd partitioning table for dasd drives. [ Dimitri John Ledkov ] * On s390[x], prevent using extended partitions on DASD drives that can only hold 3 partitions. Parted doesn't have special knowledge about that and claims that msdos partition table on DASD drives can hold the usual maximum number of partitions types. -- Christian Perrier Sun, 13 Nov 2016 07:45:31 +0100 The code there is: s390|s390x) if [ -e ./label ]; then disklabel=$(cat label) fi # FBA devices have parted label dasd, but should not use dasd # partition table. Maybe FBA|ECKD type should be exposed by # partman-base and/or parted. LP: #1650300 device=$(sed 's|.*/||' ./device) if grep -q "(FBA ).*$device" /proc/dasd/devices; then disklabel=msdos fi if [ "$disklabel" != dasd ]; then disklabel=msdos fi echo $disklabel;; In partman-base we also limit msdos to primary partitions only on dasd +#ifdef __s390__ + /* DASD drives can only do 3 partitions */ + && strcmp(disk->dev->model, "IBM S390 DASD drive") +#endif and disk label is saved to a file. It is extremely limiting if installer cannot create/recreate/reformat the drive, and has such hardcoded bad guesses. In the past, qemu did not have vfio-ccw, but now it does. Surely, the new libvirt/qemu in focal, when given a --disk path=/dev/disk/by- path/ccw-0.0.1601 it must be emulating vfio-ccw if at all possible as then on the guest it would appear as a /dev/dasda, and be correctly processed. So on s390x, the old installer - default to use ms-dos partition table, with primary partitions only, with default layout having less than 4 partitions. - if previously detected DASD partition table, use DASD, unless operating on FBA in that case use msdos again The above I think was ultimately driven by "lowlevel formateded FBA or ECKD drives" without a dasd partition table. In such cases, it was reported in qemu/kvm as "unknown" and thus "msdos with 3 partitions" was used which seemed to work, but is extremely fragile. In the new installer, I do no wish to support partition tables that are limited by a very small upper bound of 2TiB. My laptop has that, and it's trivial to over-provision/thinly provision such sizes. Is it reasonable to say that: - nvme, zfcp, virtio-scsi will use GPT - dasd ECKD devices must use vfio-ccw if passed directly to KVM, and uses dasd partition table - If vfio-ccw is not available, one can partition it on the host, create LVM or ext4 storage pool, and passthrough LVM volume or qcow2 file via virtio-scsi - passing through dasd devices as virtio-scsi in the guest must not be allowed - dasd FBA is still confusing to me as it seems to not support neither dasd nor gpt partition table Or what are you proposing we should be using across all storage variants, with/without passthrough? I am interested to know what should be used for DASD-FBA passthrough from host to guest as virtio-scsi. I am also interested to know if we can pass more information from host to guest via virtio-scsi to indicate what sort of backing storage is in use. If it's zfcp, nvme, DASD-ECKD, DASD-FBA, whether or not it
Re: [Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
On Mon, Sep 7, 2020 at 4:50 PM Dimitri John Ledkov <1893...@bugs.launchpad.net> wrote: > > I thought that one must use vfio-ccw to passthrough dasd drives, not > virtio-scsi. Yes - You can provide any block device (even image files) as virtio-blk/virtio-scsi the same as on any other platform. But indeed to "pass through" a dasd vfio-ccw would be the right and only way that comes to mind (AFAIK). /me shakes his fist at the underlying truth that the storage server has normal modern disks and emulates ECKD on top of them to later cause these issues when it no more behaves like the kind of disks it originally is composed of :-/ -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
Request to always force ms-dos partition table in KVM was requested before. However, surely it is virtualization/layering violation, when a physical host device which is not virtio-scsi compatible is passed through to qemu which emulates it as scsi, despite the underlying device on the host not able to create GPT, extended partitions, etc. Can we please prohibit passing through /dev/dasda to qemu as virtio-scsi provider on qemu and/or virtio layer? If one passes /dev/dasda to qemu, it must show up as /dev/dasd* inside the guest too. As there is no way for the guest to know or figure out that the passthrough device is actually masquerading a dasd drive. Can you please explain again, why is it correct and desired to provide /dev/vda in the guest with /dev/dasda on the host, when the two types are incompatible with each other? ** Changed in: subiquity (Ubuntu Groovy) Status: New => Incomplete ** Changed in: subiquity (Ubuntu Focal) Status: New => Incomplete -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
I thought that one must use vfio-ccw to passthrough dasd drives, not virtio-scsi. -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
'parted' with either '-l' or 'print' for example points to that fact that a
dasd is used (here a pristine DASD w/o partitions after using 'virt-install
--name groovy --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.1601 --cdrom
./groovy-live-server-s390x.iso'):
"
$ parted /dev/vda print
Model: Virtio Block Device (virtblk)
Disk /dev/vda: 7385MB
Sector size (logical/physical): 4096B/4096B
Partition Table: dasd
Disk Flags:
Number Start End Size File system Flags
"
[
In contrast to a direct dasd usage (on z/VM) that of course points to dasd,
too, but here with different ('normal') block device name an partitions:
"
$ sudo parted /dev/dasda print
Model: IBM S390 DASD drive (dasd)
Disk /dev/dasda: 7385MB
Sector size (logical/physical): 512B/4096B
Partition Table: dasd
Disk Flags:
Number Start End SizeFile system Flags
1 98.3kB 7385MB 7384MB ext4
"
]
--
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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
Here's the udev data for /dev/vda: P: /devices/css0/0.0.0002/0.0./virtio2/block/vda N: vda L: 0 S: disk/by-path/ccw-0.0. E: DEVPATH=/devices/css0/0.0.0002/0.0./virtio2/block/vda E: SUBSYSTEM=block E: DEVNAME=/dev/vda E: DEVTYPE=disk E: MAJOR=252 E: MINOR=0 E: USEC_INITIALIZED=545942 E: ID_PATH=ccw-0.0. E: ID_PATH_TAG=ccw-0_0_ E: DEVLINKS=/dev/disk/by-path/ccw-0.0. E: TAGS=:systemd: How can we tell from this that it's a dasd? I'm surprised that there is not an ID_PART_TYPE if parted identifies the drive as dasd -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
I just retried (just to be sure) with having done an explicit fdasd and dasdfmt upfront (even if my DASD was already prepared before, but it may have had some LVM leftovers), but don't see a different - same situation. ** Attachment added: "04092020.tgz" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893775/+attachment/5407636/+files/04092020.tgz -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
** Tags added: installer -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
I think if you use an already formatted dasd in the KVM this should work. If you use a completely blank one, I don't know that there's a way for the guest to tell that it's backed by a dasd vs some other block device? -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
I could recreate and can confirm the same for groovy. If the installation was started with: sudo virt-install --name groovy --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.1601 --cdrom ./groovy-live-server-s390x.iso the installer uses /dev/vda that is usually an indicator for virtio device rather than a DASD disk (the size of 6.877G is the correct net size of the used DASD Mod9 disk): Guided storage configuration[ Help ] Configure a guided storage layout, or create a custom one: (X) Use an entire disk [ /dev/vda local disk 6.877G ▾ ] [X] Set up this disk as an LVM group [ ] Encrypt the LVM group with LUKS Passphrase: Confirm passphrase: ( ) Custom storage layout [ Done ] [ Back ] I've added /var/logs and /var/crash. ** Attachment added: "02092020.tgz" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893775/+attachment/5406927/+files/02092020.tgz ** Changed in: subiquity (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => Critical ** Changed in: ubuntu-z-systems Status: New => Triaged ** Also affects: subiquity (Ubuntu Groovy) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Also affects: subiquity (Ubuntu Focal) 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/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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin20041 -- 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
[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD
** Package changed: linux (Ubuntu) => subiquity (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/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
