bug with virtio Lan drivers

[mikhmv]

Look like Proxmox have bug with virtio drivers.

I am using KVM with XP x32 guest. all updates installed.
Problem is when I am using virtion drivers for network and trying to copy files by samba Virtual Machine turn off by self. I tried to copy around 10Gb files each have size from 1 to 20 mb. It is happen either if i initiate coping files in VM and copy from other machine to VM either initiate from other machine. I checked only copying to VM. It is start to copying but in some moment (everytime different) I found that VM was turn off.

This problem don't happen if i use other adapter (for example e1000) but processor loading for e1000 larger than for virtio.

 

[tom]

Look like Proxmox have bug with virtio drivers.

I am using KVM with XP x32 guest. all updates installed.
Problem is when I am using virtion drivers for network and trying to copy files by samba Virtual Machine turn off by self. I tried to copy around 10Gb files each have size from 1 to 20 mb. It is happen either if i initiate coping files in VM and copy from other machine to VM either initiate from other machine. I checked only copying to VM. It is start to copying but in some moment (everytime different) I found that VM was turn off.

This problem don't happen if i use other adapter (for example e1000) but processor loading for e1000 larger than for virtio.

which version of virtio drivers?
which proxmox ve version (pveversion -v)?

 

[uwetr]

Look like Proxmox have bug with virtio drivers.

I am using KVM with XP x32 guest. all updates installed.
Problem is when I am using virtion drivers for network and trying to copy files by samba Virtual Machine turn off by self.

same problems here....

I've installed a new OpenSuSE 11.1 onto a proxmox system by using virtio for HDD and NIC.

This one should become my file server, so I initiated a NFS based copy of ~500GB to the virt. OSS11.1 for 4 times. Each try leaded into the situation that the virt. box was "turned off". No trace in /var/log/warn or /var/log/messages, it simply lloks as someone pushed the power button...

Thanks for your information that you don't have probs with e1000 drivers, I'll try this ASAP...

cheers,
Uwe


PS: currently 21:29, the e1000 driver is still doing the the copy job (~180GB so far). So IMHO it seems to be a problem with the virtio drivers...

PPS: Next morning 07:56: 290 GB copied, the filesystem is gone :-(
e2fsck is reporting errors on filesystem.
Looks like the virtio driver for the HDDs is an unstable story too?

 

[mikhmv]

Sorry for delay with reply.

max@proxmox:/$ pveversion -v
pve-manager: 1.1-3 (pve-manager/1.1/3718)
qemu-server: 1.0-10
pve-kernel: 2.6.24-5
pve-kvm: 83-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.23-1pve1
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

Virtio drivers I guess newest: NETKVM-20081229.iso

Thanks

 

[uwetr]

oops, seems I'm a bit outdated with pve-manager and qemu-server:

gastgeber2:~# pveversion -v
pve-manager: 1.1-1 (pve-manager/1.1/3664)
qemu-server: 1.0-7
pve-kernel: 2.6.24-5
pve-kvm: 83-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.23-1pve1
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

...will 'apt-get dist-upgrade' now

cheers,
Uwe

 

[uwetr]

update:

The copy job (~500GB) of the first virt. machine was successfully after using virt. IDE-HDD and virt. E1000 NICs.
This system is runing without any downtime or problems since then, but CPU consumption is a bit high due to the missing virtio.

I've started to migrate my 2nd machine now, it's my PDC so it's carriyng the Win-User-Profiles (~100GB).
Since I did the apt-get dist upgrade meanwhile I thought it would be a good idea to retry with virtio ... it wasn't .-(

After ~80GB the machine was "switched off" again.. :-(

So I'll use e1000 & IDE for that guest too, hopefully there will be an update one day regarding this problem.


cheers,
Uwe