Virtio with multiple devices of the same type

[Will Trives <will@trivescon.com.au>]

Hello guys,

Bug: A virtual machine/guest can only have one virtio block device and
one virtio network device.

Example command line: 

qemu-system-x86_64 -drive file=disk.qcow2,if=virtio,boot=on -net nic,model=virtio,macaddr=50:18:99:55:4E:43 -net tap -net nic,model=virtio,macaddr=51:17:99:55:4D:43 -net tap 

What will happen is the virtual machine will boot, and slowly grind to a
halt with the two network interfaces not working at all. 

qemu-system-x86_64 -drive file=disk.qcow2,if=virtio,boot=on -drive file=disk2.qcow2,if=virtio

With this one, instead of getting two virtual disks, the kernel hangs on bootup.

qemu-system-x86_64 -drive file=disk.qcow2,if=virtio,boot=on -net nic,model=virtio,macaddr=50:18:99:55:4E:43 -net tap -net nic,model=rtl8139,macaddr=51:17:99:55:4D:43 -net tap

With this one, even though only the first network device is a Virtio one, neither work.

When only using ONE virtio block and ONE virtio net, it works as it's supposed to.


This is observed :

* On a 64 bit host with an Intel Q6600 cpu
* Host is 64 bit, guest 64 bit.
* latest Linux git kernel (which has the new virtio code in it from Rusty) both for host and guest
* the latest KVM userspace (with --with-patched-kernel or by syncing to the latest kvm git tree)
* the behaviour with the network devices is observed regardless of whether the network drive is compiled in or modular.

I was wondering if this is helpful or can be replicated, if not perhaps my guest which is running Archlinux64 is doing something strange.


Regards,

Will Trives




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel