vhost=on not working

flow

Renowned Member
Nov 10, 2010
34
8
73
Hello everybody,

i wanted to test the new syntax regarding -netdev and vhost=on with virtio-net, but unfortunately it doesn't work for me.

I updated to the latest stable 1.7 PVE. Here's my pveversion -v output:


pveversion -v
pve-manager: 1.7-10 (pve-manager/1.7/5323)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.7-29
pve-kernel-2.6.32-4-pve: 2.6.32-29
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-26
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-9
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-2
ksm-control-daemon: 1.0-4

Maybe i'm missing something, but here's what i have done so far:

I added vhost=on in /etc/qemu-server/vmid.conf on the vlan0 line.

Tried to start the VM (KVM) wit "qm start VMID", it starts but with the following output on the shell:
"unable to parse value of 'vlan0'"

Then i tried to start the VM on the shell with the complete line of "qm showcmd VMID" with the modifications proposed on http://www.linux-kvm.org/page/VhostNet

The output of this is: "Device 'tap' could not be initialized"


Has someone any idea what i am doin wrong?

Thanks in advance :)
 
you do not need to add it in vmid.conf.
 
and use 2.6.35 kernel branch.
 
I thougt after reading the changelog that the vhost_net module would be included in the 2.6.32 branch.
After a lsmod it seems that that was a misunderstanding :)

Unfortunately using 2.6.35 is not an option for me because of the missing OpenVZ capability.
Are there any plans to include vhost capability into the 2.6.32 branch?