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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
