I was retrying the same on x86 just t see if it is arch depending at all. But to start with, when using disks as fake multipath via kvm they should not use metadata (qcow2) nor caching. Hence changing that to format=raw,cache=none
$ qemu-img create -f raw /tmp/ubuntu-disk.raw 8G Formatting '/tmp/ubuntu-disk.raw', fmt=raw size=858993459 $ qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -boot menu=on \ -device virtio-scsi-pci,id=scsi -drive if=none,id=mpatha,file=/tmp/ubuntu-disk.raw,format=raw,cache=none,file.locking=off \ -device scsi-hd,drive=mpatha,serial=MPIO \ -drive if=none,id=mpathb,file=/tmp/ubuntu-disk.raw,format=raw,cache=none,file.locking=off \ -drive file=/tmp/ubuntu-24.04.2-live-server-amd64.iso,media=cdrom \ -device scsi-hd,drive=mpathb,serial=MPIO \ -net nic,model=virtio \ -net user,hostfwd=::2222-:22 \ ... I ran this right on my system, so no need to mess with -nographic. In hindsight that made copying output screenshots :-/ Install #1 worked fine I tried to stay as default as possible, which in regard to disks gave me (see screenshots that follow) Install #2 onto the same - for a more relaxed approach than hitting keys fast I added "-boot d" to this second invocation of qemu It fails and I see the same -EBUSY messages. But aren't those red-herrings as that is from boot and the installer properly detected the disk state. Only on actually going to deployment did it crash. I've sent the full report so Dan can compare that with what was attached by IBM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080474 Title: ubuntu installation failing for systems having SAN disk To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2080474/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
