KVM 0.13.0 for Proxmox VE 1.6 (for 2.6.32 and 2.6.35) - pvetest repository

dietmar · Oct 29, 2010

Frank.Pawlik said:
Is there a change that vhost-net will be backported to 2.6.32?

Maybe later (not now). But if you report errors we can try to fix them.

Frank.Pawlik · Oct 29, 2010

qm start vmid.conf says:

'unable to parse value of 'vlan0''

pve-manager: 1.6-7 (pve-manager/1.6/5277)
running kernel: 2.6.35-1-pve
pve-kernel-2.6.32-4-pve: 2.6.32-25
pve-kernel-2.6.35-1-pve: 2.6.35-7
qemu-server: 1.1-24
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-15
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

name: test
ide2: local:iso/virtio-win-1.1.11-0.iso,media=cdrom
bootdisk: virtio0
ostype: w2k3
memory: 4096
sockets: 1
onboot: 1
cores: 2
boot: cd
freeze: 0
cpuunits: 10000
acpi: 1
kvm: 1
virtio0: local:108/vm-108-disk-virtio0.qcow2
vlan0: virtio=EA:08:6C:50

C:93,vhost=on
virtio1: local:108/vm-108-disk-1.qcow2
args: -cpu host

Whats wrong?

dietmar · Oct 29, 2010

Frank.Pawlik said:
Whats wrong?

Please remove that 'vhost=on'

Frank.Pawlik · Oct 29, 2010

'Please remove that 'vhost=on''
?
Is vhost automatically on?

dietmar · Oct 29, 2010

Frank.Pawlik said:
Is vhost automatically on?

Yes (if you use virtio, and vhost_net module is loaded)

spirit · Oct 29, 2010

same problem with win2003 32bit install,

crashing at begin of install, i can't choose floppy.

(in 2003 x64, i can choose floppy driver, but it crash after).

Frank.Pawlik · Oct 29, 2010

dietmar said:
Yes (if you use virtio, and vhost_net module is loaded)

Ah. Works.
Seems not to be faster.
I will make some tests.

edwards · Oct 29, 2010

for me installing windows 2003 64x was working like a charm, but I used for networking virtio and was not known by windows(weird) and switch it to realtek. Now works fine.

I`m doing this test too so for me everything works good after upgrade. I did it from/with apt apt-get update && apt-get dist-upgrade.

promox:~# pveversion -v
pve-manager: 1.6-7 (pve-manager/1.6/5277)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-25
pve-kernel-2.6.32-4-pve: 2.6.32-25
qemu-server: 1.1-24
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-15
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-2
ksm-control-daemon: 1.0-4

macday · Oct 29, 2010

Frank.Pawlik said:
qm start vmid.conf says:

'unable to parse value of 'vlan0''

pve-manager: 1.6-7 (pve-manager/1.6/5277)
running kernel: 2.6.35-1-pve
pve-kernel-2.6.32-4-pve: 2.6.32-25
pve-kernel-2.6.35-1-pve: 2.6.35-7
qemu-server: 1.1-24
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-15
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

name: test
ide2: local:iso/virtio-win-1.1.11-0.iso,media=cdrom
bootdisk: virtio0
ostype: w2k3
memory: 4096
sockets: 1
onboot: 1
cores: 2
boot: cd
freeze: 0
cpuunits: 10000
acpi: 1
kvm: 1
virtio0: local:108/vm-108-disk-virtio0.qcow2
vlan0: virtio=EA:08:6C:50C:93,vhost=on
virtio1: local:108/vm-108-disk-1.qcow2
args: -cpu host

Whats wrong?

I think you don´t need to put "vhost=on" to your config-file. It is parsed through QemuServer.pm

chrisalavoine · Nov 3, 2010

Have upgraded to 2.6.35:

Code:

ess-prox-003:~# pveversion -v
pve-manager: 1.6-7 (pve-manager/1.6/5277)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.6-7
pve-kernel-2.6.35-1-pve: 2.6.35-7
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-24
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-15
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-2
ksm-control-daemon: 1.0-4

vhost=on and -netdev are active on my VM's. Running 5 Windows XP machines on this host but not seeing any significant iperf improvement. Do I need to update drivers on Windows XP boxes?

I will be doing further tests with existing ubuntu/centos and Windows server machines.

c

chrisalavoine · Nov 3, 2010

Am also seeing a much higher load on the Proxmox host than before. All Windows XP VM's are idle but I'm seeing a load average of around 0.50, previously it was ~0.02

Chris.

tom · Nov 3, 2010

I assume the higher load is caused by KSM.

chrisalavoine · Nov 3, 2010

tom said:
I assume the higher load is caused by KSM.

Sorry, my mistake - I didn't realise that KSM was active on this release.

Do you think I need to update my virtio drivers on the Windows XP machines?

Driver date: 18/06/2009
Driver version: 1.0.0.31383

Chris.

tom · Nov 3, 2010

I also do not see any improvements on windows guest. linux guests performs well with virtio.

chrisalavoine · Nov 3, 2010

Have updated virtio driver on Windows guests to:

driver date: 10/08/2010
driver version: 5.1.209.605

Still no improvement in iperf results.

Chris.

chrisalavoine · Nov 3, 2010

I can confirm big improvements on Linux (Ubuntu) guests.

Old kernel:
Around 930 Mbits/sec

New kernel:
Around 2.1 Gbits/sec

Chris.

spirit · Nov 4, 2010

I have had a look in the code, QemuServer.pm file,

vhost is only supported in kvm 0.13, but new -netdev and -device are already supported in kvm 0.12.

original code

Code:

 foreach my $nic (@{$vlan->{nics}}) {
                my $device = $nic->{model};
                my $vhostparam = '';
                if ($nic->{model} eq 'virtio') {
                    $use_virtio = 1;
                    $device = 'virtio-net-pci';
                    $vhostparam = ',vhost=on' if $kernel_has_vhost_net;
                };
                if ($vernum < 13000) {
                    push @$cmd, '-net', "nic,vlan=$i,model=$nic->{model},macaddr=$nic->{macaddr}";
                } else {
                    push @$cmd, '-netdev', "type=tap,id=${k}d$j,ifname=${ifname}d$j,script=/var/lib/qemu-server/bridge-vlan$vhostparam";
                    push @$cmd, '-device', "$device,mac=$nic->{macaddr},netdev=${k}d$j";
                }
                $j = $j + 1;
            }

modified code

Code:

foreach my $nic (@{$vlan->{nics}}) {
                my $device = $nic->{model};
                my $vhostparam = '';
                if ($nic->{model} eq 'virtio') {
                    $use_virtio = 1;
                    $device = 'virtio-net-pci';
[B]                  if ($vernum > 13000) {[/B]
                    $vhostparam = ',vhost=on' if $kernel_has_vhost_net;
                  [B]}[/B]
                };
                if ($vernum < [B]12000[/B]) {
                    push @$cmd, '-net', "nic,vlan=$i,model=$nic->{model},macaddr=$nic->{macaddr}";
                } else {
                    push @$cmd, '-netdev', "type=tap,id=${k}d$j,ifname=${ifname}d$j,script=/var/lib/qemu-server/bridge-vlan$vhostparam";
                    push @$cmd, '-device', "$device,mac=$nic->{macaddr},netdev=${k}d$j";
                }
                $j = $j + 1;
            }

dietmar · Nov 5, 2010

spirit said:
vhost is only supported in kvm 0.13, but new -netdev and -device are already supported in kvm 0.12.

While that is true, we do not want to support that for 0.12. We will replace the 0.12 package in a few days, so it is not really worth the effort.

Frank.Pawlik · Nov 9, 2010

I made some tests with iperf from Windows7 (real host) to Windows2003 (kvm) now.

a. 2.6.35 with vhost-net: 71.4
b. 2.6.35 without vhost-net: 72.23
c. 2.6.32: 75.16

Virtio 5.1.209.605 on kvm.

tom · Nov 9, 2010

it seems that vhost-net does not improve performance on windows, at least with the current drivers.

KVM 0.13.0 for Proxmox VE 1.6 (for 2.6.32 and 2.6.35) - pvetest repository

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Distinguished Member

Attachments

Member

New Member

Member

Renowned Member

Renowned Member

Proxmox Staff Member

Renowned Member

Proxmox Staff Member

Renowned Member

Renowned Member

Distinguished Member

Proxmox Staff Member

Member

Proxmox Staff Member

We value your privacy