Brian Kroth wrote: > Guido Günther <a...@sigxcpu.org> 2010-03-28 14:53: [] >> Could you try to add execute this "by hand" and find the offending >> option? >> -- Guido > > Yeah, I did that. It's as the other bug I linked said. Basically, > libvirt changed the way it arranges the command lines from the XML so > that what was this in <=0.7.5: > > -net nic,macaddr=52:54:00:a1:90:92,vlan=0,model=virtio,name=virtio.0 -net > tap,fd=22,vlan=0,name=tap.0 > > became this in 0.7.7 (possibly also 0.7.6): > > -device > virtio-net-pci,vlan=0,id=net0,mac=52:54:00:a1:90:92,bus=pci.0,addr=0x4 -net > tap,fd=23,vlan=0,name=hostnet0 > > The problem appears to be that qemu 0.12.3 (possibly for earlier > versions as well) doesn't parse the "-device virtio-net..." option as > being a NIC, so it fails to boot from it. I have tried this with other > NIC models as well and they all result in the same problem - if the NIC > definition is given as a "-device" instead of a "-net nic", then qemu > refuses to boot from it.
Very good findings. It appears to be a kvm bug after all, -- I don't see a way to tell it to boot from network with -device..-net pair, only with -net..-net pair. Confirmed. I'll check this in more detail. Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
