kvm 0.84 doesn't create three drives in the guest

[Mathias Gug]

Binary package hint: kvm

Running kvm 1:84+dfsg-0ubuntu8~ppa5 on a hardy host.

With the following command, only two drives show up in the guest (vda, vdb) while three are expected (+vdc):

/usr/bin/kvm -M pc -m 128 -smp 1 -monitor pty -no-reboot -boot d -kernel /home/mathiaz/vm/tests_isos/jaunty-server-amd64/vmlinuz -initrd /home/mathiaz/vm/tests_isos/jaunty-server-amd64/initrd.gz -append file=/raid5.preseed quiet -- debconf/priority=critical locale=en_US console-setup/ask_detect=false console-setup/layoutcode=us -drive file=/home/mathiaz/vm/tests_isos/jaunty-server-amd64-raid5/vm//root1.qcow2,if=virtio,index=0 -drive file=/home/mathiaz/vm/isos/9.04-20090413/jaunty-server-amd64.iso,if=ide,media=cdrom,index=2,boot=on -drive file=/home/mathiaz/vm/tests_isos/jaunty-server-amd64-raid5/vm//root2.qcow2,if=virtio,index=1 -drive file=/home/mathiaz/vm/tests_isos/jaunty-server-amd64-raid5/vm//root3.qcow2,if=virtio,index=3 -net nic,macaddr=52:54:00:d4:51:95,vlan=0,model=virtio -net tap,fd=21,script=,vlan=0 -usb -vnc 0.0.0.0:3

[Soren Hansen (soren)]

The virtio block device driver doesn't approve of gaps in the indexing of your disks, so you shouldn't skip index=2 when using virtio. I consider that a workaround, though, and think the bug should be fixed.

[Mathias Gug (mathiaz)]

kvm 1:62+dfsg-0ubuntu8+libvirt 0.4.0-2ubuntu8.1 is able to boot a guest which sees three block devices.

[Mathias Gug (mathiaz)]

Here is the kvm command line that is working (kvm 1:62+dfsg-0ubuntu8+libvirt 0.4.0-2ubuntu8.1):

/usr/bin/kvm -M pc -m 128 -smp 1 -monitor pty -no-reboot -kernel /home/mathiaz/vm/tests_isos/jaunty-server-amd64/vmlinuz -initrd /home/mathiaz/vm/tests_isos/jaunty-server-amd64/initrd.gz -append file=/raid5.preseed quiet -- debconf/priority=critical locale=en_US console-setup/ask_detect=false console-setup/layoutcode=us -drive file=/home/mathiaz/vm/isos/9.04-20090414/jaunty-server-amd64.iso,if=ide,media=cdrom,boot=on -drive file=/home/mathiaz/vm/tests_isos/jaunty-server-amd64-raid5/vm//root1.qcow2,if=virtio -drive file=/home/mathiaz/vm/tests_isos/jaunty-server-amd64-raid5/vm//root3.qcow2,if=virtio -drive file=/home/mathiaz/vm/tests_isos/jaunty-server-amd64-raid5/vm//root2.qcow2,if=virtio -net nic,macaddr=52:54:00:3b:95:25,vlan=0,model=virtio -net tap,fd=10,script=,vlan=0 -usb -vnc 0.0.0.0:0

[Launchpad Janitor (janitor)]

This bug was fixed in the package kvm - 1:84+dfsg-0ubuntu11

---------------
kvm (1:84+dfsg-0ubuntu11) jaunty; urgency=low

  * debian/patches/add-all-virtio-drives.patch: Fix bugs where the caller
    does not specify a perfectly defined list of virtio drives starting at
    index=0 and having no gaps in indices; LP: #360832, #360825
  * debian/patches/fix-qcow-corruption: Cherry-pick from kvm stable git
    branch, fixes at least one cause of qcow2 image corruption; no reports
    yet of this in Ubuntu, but I'm being proactive about this one;
    LP: #361938
  * debian/source_kvm.py: dpkg -l was a little too heavy, compress this
    output considerably

 -- Dustin Kirkland <email address hidden> Fri, 17 Apr 2009 09:59:58 -0500