[Pkg-libvirt-maintainers] Bug#565767: Bug#565767: libvirt-bin: VM doesn't work after upgrade: qemu: Could not initialize device 'tap'

[Guido Günther]

Hi,
On Thu, Jan 28, 2010 at 06:36:17PM +0100, Tino Keitel wrote:
> On Mon, Jan 18, 2010 at 20:38:15 +0100, Tino Keitel wrote:
> > On Mon, Jan 18, 2010 at 20:31:30 +0100, Guido Günther wrote:
> > > Is /dev/net/tun there? What does libvirtd's output say? Please run
> > > libvirtd in debug mode.
> > > Cheers,
> > 
> > Yes, it was there. Meanwhile, I downgraded to 0.7.2 because I needed
> > something usable.
> 
> Hi,
> 
> now I have this problem on a Sid installation:
> 
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/home/scorpion USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 4 -name mguard0 -uuid 7ac787ad-365e-43f5-9552-64b620d11a62 -monitor unix:/var/lib/libvirt/qemu/mguard0.monitor,server,nowait -boot c -drive if=ide,media=cdrom,index=2 -drive file=/var/lib/libvirt/images/kvm-mguard0,if=ide,index=0,boot=on -net nic,macaddr=52:54:00:38:53:95,vlan=0,model=e1000,name=e1000.0 -net tap,ifname=m0d0,vlan=0,name=tap.0 -net nic,macaddr=52:54:00:67:67:eb,vlan=1,model=e1000,name=e1000.1 -net tap,ifname=m0d1,vlan=1,name=tap.1 -net nic,macaddr=52:54:00:52:ed:a2,vlan=2,model=e1000,name=e1000.2 -net tap,ifname=m0d2,vlan=2,name=tap.2 -net nic,macaddr=52:54:00:4a:6e:47,vlan=3,model=e1000,name=e1000.3 -net tap,ifname=m0d3,vlan=3,name=tap.3 -serial pty -parallel none -usb -vnc 127.0.0.1:0 -k de -vga cirrus 
> warning: could not configure /dev/net/tun: no virtual network emulation
> qemu: Could not initialize device 'tap'
> 
> I already have set these options in qemu.conf:
> 
> $ grep root /etc/libvirt/qemu.conf
> user = "root"
> group = "root"

This won't help since this is being created from libvirtd which runs as
root anyway (assuming you're using qemu:///system). We'd need:

* the libvirtd log, please run libvirtd in debug mode e.g. as root:

LIBVIRT_DEBUG=1 /usr/sbin/libvirtd

* The command you use to start the vm
* The domain xml
* Did you try with only a single network interface?

Cheers,
 -- Guido