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

[martin]

We just released the latest KVM 0.13.0 to our pvetest repository.

Release notes:

- pve-qemu-kvm (0.13.0-2)

• do not install unnecessary blobs (manually install blobs, use --disable-blobs)
• update migration and vnc keymap patches for 0.13.0
• many bugfixes

- qemu-server (1.1-23)

• use new -netdev syntax for network devices. This enables tcp offload settings, and we can use 'vhost=on' for virtio-net

Everybody using the 2.6.32 or 2.6.35 kernel branch is encouraged to test and give feedback!
__________________
Best regards,
Martin Maurer

 

[valshare]

Hi Martin,

have upgraded our testmachine to the latest:

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-23
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
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

Now my testmachine did´t come up. Can you help?

kvm: -netdev type=tap,id=vmtab112i0,ifname=vmtab112i0,script=/var/lib/qemu-server/bridge-vlan: Duplicate ID 'vmtab112i0'      for netdev

start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/112.mon,server,nowait -vnc unix:/var/run/qemu-server/112.vnc,password -pidfile /var/run/qemu-server/112.pid -daemonize -usbdevice tablet -name testmachine -smp sockets=1,cores=1 -nodefaults -boot menu=on,order=cad -vga cirrus -tdf -localtime -rtc-td-hack -k de -drive file=/dev/pve-i4500r/vm-112-disk-1,if=ide,index=0,boot=on -drive if=ide,index=2,media=cdrom -m 1024 -netdev type=tap,id=vmtab112i0,ifname=vmtab112i0,script=/var/lib/qemu-server/bridge-vlan -device e1000,mac=2A:80:A0:A0:8B:45,netdev=vmtab112i0 -netdev type=tap,id=vmtab112i0,ifname=vmtab112i0,script=/var/lib/qemu-server/bridge-vlan -device virtio-net-pci,mac=1E:15:88:87:7E:E6,netdev=vmtab112i0 -netdev type=tap,id=vmtab112i0,ifname=vmtab112i0,script=/var/lib/qemu-server/bridge-vlan -device rtl8139,mac=C6:99:65:2A:D3:73,netdev=vmtab112i0 -rtc-td-hack' failed with exit code 1

Config File from the machine:

name: testmachine
ide2: none,media=cdrom
sockets: 1
bootdisk: ide0
ostype: wxp
memory: 1024
onboot: 0
vlan0: e1000=2A:80:A0:A0:8B:45,virtio=1E:15:88:87:7E:E6,rtl8139=C6:99:65:2A:D3:73
boot: cad
freeze: 0
cpuunits: 3000
acpi: 1
kvm: 1
description: 
cores: 1
ide0: KVM-DATA-01:vm-112-disk-1
migrate_downtime: 0
migrate_speed: 0
args: -rtc-td-hack

Regards, Valle

 

[tom]

we just uploaded a fix to pvetest, enables the use of more than one NIC again.
(the new package is qemu-server_1.1-24_amd64.deb)

can you test?

 

[valshare]

Hi Tom,

thanx for the fix. Machine is now running.

 

[tom]

great, thanks for feedback

 

[spirit]

virtio win drivers (viostor.sys) is broken with qemu-kvm 0.13. (blue screen of the dead).

New install of windows with floppy said that drivers are not compatible.

(i've try the drivers from rhev 2.2 and also from here http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ ).


Has someone a build of git http://git.kernel.org/?p=virt/kvm/kvm-guest-drivers-windows.git;a=summary ?

 

[tom]

what version of windows do you use, is this a fresh install on KVM 0.13.0 or did you upgrade the KVM? I always use the ISO to provide the drivers, new installs works here.

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.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-14
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

 

[spirit]

i try with new install (driver on floppy , windows said not compatible) and existing vm, blue screen of the dead on viostor.sys.

forget to say, it's on win2003 x64.

i dont have win2008 for testing.


working proxmox:

pve-manager: 1.6-5 (pve-manager/1.6/5261)
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-22
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.12.5-2
ksm-control-daemon: 1.0-4


not working (pvetest):

veversion -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

 

[tom]

there are no drivers for win2003-64 in this package (http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/)

 

[spirit]

???

i can install win2003 x64 ,with these packages (rhev and fedora) on the stable version of proxmox ....

 

[spirit]

(fedora package): virtio-win-1.1.11-0.vfd

txtsetup.oem

[Disks]
d1 = "OEM DISK (SCSI) WinXP/32-bit",\disk1,\i386\WinXP
d2 = "OEM DISK (SCSI) Win2003/32-bit",\disk1,\i386\Win2003
d3 = "OEM DISK (SCSI) Win2003/64-bit",\disk1,\amd64\Win2003

[Defaults]
SCSI = WXP32

[scsi]
WXP32 = "Red Hat VirtIO SCSI Disk Device WinXP/32-bit"
WNET32 = "Red Hat VirtIO SCSI Disk Device Win2003/32-bit"
WNET64 = "Red Hat VirtIO SCSI Disk Device Win2003/64-bit"



rhev packages (virtio-drivers-1.0.0-45801.vfd)
txtsetup.oem
Disks]
d1 = "OEM DISK (SCSI) WinXP/32-bit",\disk1,\i386\WinXP
d2 = "OEM DISK (SCSI) Win2003/32-bit",\disk1,\i386\Win2003
d3 = "OEM DISK (SCSI) Win2003/64-bit",\disk1,\amd64\Win2003

[Defaults]
SCSI = WXP32

[scsi]
WXP32 = "Red Hat VirtIO SCSI Disk Device WinXP/32-bit"
WNET32 = "Red Hat VirtIO SCSI Disk Device Win2003/32-bit"
WNET64 = "Red Hat VirtIO SCSI Disk Device Win2003/64-bit"

 

[tom]

???

i can install win2003 x64 ,with these packages (rhev and fedora) on the stable version of proxmox ....

I just unpack the ISO image; there is no driver - point me to the driver DIR on this ISO image you are using - under viostor I cannot find a win2003 folder nor a winxp folder with driver for amd64.

 

[spirit]

i'm using floppy

 

[tom]

how do you add the floppy image to the guest?

 

[spirit]

command line launch kvm (cause we don't have floppy in proxmox webinterface)

/usr/bin/kvm -monitor unix:/var/run/qemu-server/103.mon,server,nowait -vnc unix:/var/run/qemu-server/103.vnc,password -pidfile /var/run/qemu-server/103.pid -daemonize -usbdevice tablet -name testwin64 -smp sockets=1,cores=1 -nodefaults -boot menu=on,order=da -vga cirrus -tdf -localtime -rtc-td-hack -k fr -drive file=/var/lib/vz/template/iso/win2003x64-sp2.iso,if=ide,index=2,media=cdrom -drive file=/dev/disk/by-id/scsi-3600144f0f62f0e0000004cc80d210006,if=virtio,index=0 -m 1000 -netdev type=tap,id=vlan0d0,ifname=vmtab103i0d0,script=/var/lib/qemu-server/bridge-vlan -device virtio-net-pci,mac=76:3D:9D:29:44:E2,netdev=vlan0d0 [B]-fda /var/lib/vz/template/iso/virtio-win-1.1.11-0.vfd    [/B]

but as i said, i have also the problem with an already installed vm. (blue screen at windows startup).


i'll try with win2003 32bit this afternoon.

 

[tom]

ok, got it. the floppy image contains just other drivers as the ISO image - quite confusing.
and I confirm that these drivers from this floppy image leads to a blue screen on windows 2003 - 64 bit.

pls report your results with 2003-32.

 

[tom]

...and report it to the provider of the package.

 

[Frank.Pawlik]

How to enable vhost-net?
I added vlan0: virtio=EA:08:6C:50C:93,vhost=on to vmid.conf
and 'unable to parse value of vlan0' occurs.

 

[dietmar]

How to enable vhost-net?

You need to use kernel 2.6.35 and:

ftp://download.proxmox.com/debian/dists/lenny/pvetest/binary-amd64/qemu-server_1.1-24_amd64.deb

from the 'pvetest' repository.

 

[Frank.Pawlik]

No luck with 2.6.35.
Ethernet device disapears.

Is there a change that vhost-net will be backported to 2.6.32?