vhost-net requested but could not be initialized

Florent

Member
Apr 3, 2012
91
2
8
Hi all,

On a test cluster, I can't start VM after migrating them on RBD :

Code:
kvm: -netdev  type=tap,id=net0,ifname=tap139i0,script=/var/lib/qemu-server/pve-bridge,vhost=on:  vhost-net requested but could not be initialized
kvm: -netdev  type=tap,id=net0,ifname=tap139i0,script=/var/lib/qemu-server/pve-bridge,vhost=on:  Device 'tap' could not be initialized
TASK ERROR: start failed:  command '/usr/bin/kvm -id 139 -chardev  'socket,id=qmp,path=/var/run/qemu-server/139.qmp,server,nowait' -mon  'chardev=qmp,mode=control' -vnc  unix:/var/run/qemu-server/139.vnc,x509,password -pidfile  /var/run/qemu-server/139.pid -daemonize -name  mariadb-drupal-merge.dev.limawi.ch -smp 'sockets=1,cores=1' -nodefaults  -boot 'menu=on' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -k fr -m  1024 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device  'usb-tablet,id=tablet,bus=uhci.0,port=1' -device  'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive  '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=rbd:pve01-rbd01/vm-139-disk-1:mon_host=192.168.0.200 192.168.0.202   192.168.0.203:id=pvenodes:auth_supported=cephx:keyring=/etc/pve/priv/ceph/PVE01-RBD01.keyring,if=none,id=drive-virtio0,cache=writeback,aio=native'  -device  'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100'  -netdev  'type=tap,id=net0,ifname=tap139i0,script=/var/lib/qemu-server/pve-bridge,vhost=on'  -device  'virtio-net-pci,mac=16:4D:1B:BB:3A:A5,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300''  failed: exit code 1

On a node, VM cannot start (never), on another node VM starts after a few retries (4-5 tries then starts)...

What could be the problem ?

All nodes are on 3.10 pve kernel, up to date 3.2 pve, ceph firefly.

Thank you :)
 
also post your VM config:

> qm config VMID
 
Here is another VM config that cannot start :

Code:
bootdisk: virtio0
cores: 1
description: 192.168.0.138%0A
ide2: none,media=cdrom
memory: 1024
name: mariadb-api-ref.dev.limawi.ch
net0: virtio=36:A1:98:F2:BE:EC,bridge=vmbr1
ostype: l26
sockets: 1
virtio0: PVE01-RBD01:vm-143-disk-1,cache=writeback,size=8G

vmbr1 is up (some VM are always in that bridge)...
 
VM 143 finally started on that node, after more than 20 tries (without changing anything...)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!