[PVE-User] Problems starting VMs

[Severin Kacianka]

Hello,

today I upgraded a host from an early 2.0 release to the latest one (via
apt-get upgrade) and have problems starting the VMs (Note: I did not
restart this server for quite some - so the problem does not have to be
connected with the upgrade). I can start one VM, but then get error
messages like these:
kvm: -netdev
type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,vhost=on:
could not configure /dev/net/tun (tap100i0): Device or resource busy
kvm: -netdev
type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,vhost=on:
Device 'tap' could not be initialized

When it failed to work via the web interface I copied the command from
the web interface and ran them on the server directly, these are the two
commands:
/usr/bin/kvm -id 103 -chardev
'socket,id=qmp,path=/var/run/qemu-server/103.qmp,server,nowait' -mon
'chardev=qmp,mode=control' -vnc
unix:/var/run/qemu-server/103.vnc,x509,password -pidfile
/var/run/qemu-server/103.pid -daemonize -name backup -smp
'sockets=2,cores=8' -cpu Westmere -nodefaults -boot 'menu=on' -vga
cirrus -k en-us -m 2048 -usbdevice tablet -drive
'file=/var/lib/vz/images/103/vm-103-disk-2.raw,if=none,id=drive-virtio1,aio=native,cache=none'
-device
'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb'
-drive
'file=/var/lib/vz/template/iso/debian-6.0.4-amd64-netinst.iso,if=none,id=drive-ide2,media=cdrom,aio=native'
-device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200'
-drive
'file=/var/lib/vz/images/103/vm-103-disk-1.raw,if=none,id=drive-virtio0,aio=native,cache=none'
-device
'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=101'
-netdev
'type=tap,id=net0,ifname=tap103i0,script=/var/lib/qemu-server/pve-bridge,vhost=on'
-device
'virtio-net-pci,mac=2E:A5:38:2A:26:54,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'

(this one works)

/usr/bin/kvm -id 100 -chardev
'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon
'chardev=qmp,mode=control' -vnc
unix:/var/run/qemu-server/100.vnc,x509,password -pidfile
/var/run/qemu-server/100.pid -daemonize -name server-backup -smp
'sockets=2,cores=4' -cpu Westmere -nodefaults -boot 'menu=on' -vga
cirrus -k en-us -m 1024 -usbdevice tablet -drive
'file=/var/lib/vz/images/100/vm-100-disk-2.raw,if=none,id=drive-virtio1,aio=native,cache=none'
-device
'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb'
-drive
'file=/var/lib/vz/template/iso/debian-6.0.4-amd64-netinst.iso,if=none,id=drive-ide2,media=cdrom,aio=native'
-device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200'
-drive
'file=/var/lib/vz/images/100/vm-100-disk-1.raw,if=none,id=drive-virtio0,aio=native,cache=none'
-device
'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=101'
-drive
'file=/var/lib/vz/images/100/vm-100-disk-3.raw,if=none,id=drive-virtio2,aio=native,cache=none'
-device
'virtio-blk-pci,drive=drive-virtio2,id=virtio2,bus=pci.0,addr=0xc'
-netdev
'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,vhost=on'
-device
'virtio-net-pci,mac=1A:4F:15:D7:CD:40,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'

(this one gives these error:
kvm: -netdev
type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,vhost=on:
could not configure /dev/net/tun (tap100i0): Device or resource busy
kvm: -netdev
type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,vhost=on:
Device 'tap' could not be initialized
)

lsof shows this:

# lsof /dev/net/tun
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
kvm     2305 root   11u   CHR 10,200      0t0 8053 /dev/net/tun

what is weird is that another VM starts without a problem:


/usr/bin/kvm -id 104 -chardev
'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server,nowait' -mon
'chardev=qmp,mode=control' -vnc
unix:/var/run/qemu-server/104.vnc,x509,password -pidfile
/var/run/qemu-server/104.pid -daemonize -name filesrv2 -smp
'sockets=2,cores=8' -cpu Westmere -nodefaults -boot 'menu=on' -vga
cirrus -k en-us -m 2048 -usbdevice tablet -drive
'file=/var/lib/vz/images/104/vm-104-disk-2.raw,if=none,id=drive-virtio1,aio=native,cache=none'
-device
'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb'
-drive
'file=/var/lib/vz/template/iso/debian-6.0.4-amd64-netinst.iso,if=none,id=drive-ide2,media=cdrom,aio=native'
-device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200'
-drive
'file=/var/lib/vz/images/104/vm-104-disk-1.raw,if=none,id=drive-virtio0,aio=native,cache=none'
-device
'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=101'
-netdev
'type=tap,id=net0,ifname=tap104i0,script=/var/lib/qemu-server/pve-bridge,vhost=on'
-device
'virtio-net-pci,mac=62:71:A5:74:D8:91,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'

lsof then shows: #lsof /dev/net/tun
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
kvm     2305 root   11u   CHR 10,200      0t0 8053 /dev/net/tun
kvm     2560 root   11u   CHR 10,200      0t0 8053 /dev/net/tun

My pveversion is this:
# pveversion -v
pve-manager: 2.2-26 (pve-manager/2.2/c1614c8c)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-80
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-80
pve-kernel-2.6.32-12-pve: 2.6.32-68
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-1
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-28
qemu-server: 2.0-64
pve-firmware: 1.0-21
libpve-common-perl: 1.0-37
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-34
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1

What could be the reason for this? How can I pin point the problem?

Thank you for your time and best regards,
Severin