Windows 2000 in KVM (silent death)

[Wakko]

Hello!

I use Proxmox with 2 OpenVZ VMs and 2 KVM VMs. And KVM virtual machine with my Windows 2000 sometimes "disappears". In logs I can see only:

Feb 11 19:41:24 yakko kernel: vmbr0: port 3(tap103i0d0) entering disabled state
Feb 11 19:41:24 yakko kernel: vmbr0: port 3(tap103i0d0) entering disabled state
Feb 11 19:41:24 yakko kernel: vmbr0: port 4(tap103i0d1) entering disabled state
Feb 11 19:41:24 yakko kernel: vmbr0: port 4(tap103i0d1) entering disabled state
Feb 11 19:42:52 yakko qm[15276]: VM 103 monitor command failed - VM not running

yakko:~# uname -a
Linux yakko 2.6.32-4-pve #1 SMP Wed Dec 15 14:04:31 CET 2010 x86_64 GNU/Linux

yakko:~# pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.7-30
pve-kernel-2.6.32-4-pve: 2.6.32-30
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4

yakko:~# top | head -n 5
top - 20:47:18 up 26 days,  1:09, 10 users,  load average: 0.17, 0.13, 0.07
Tasks: 333 total,   2 running, 331 sleeping,   0 stopped,   0 zombie
Cpu(s):  4.6%us,  2.4%sy,  0.1%ni, 90.6%id,  2.0%wa,  0.0%hi,  0.2%si,  0.0%st
Mem:  12276600k total,  4913796k used,  7362804k free,   107760k buffers
Swap:  8388600k total,   145096k used,  8243504k free,  2031188k cached

yakko:~# cat /proc/cpuinfo | grep name | uniq
model name      : Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz

yakko:~# cat /etc/qemu-server/103.conf
ostype: w2k
memory: 1024
sockets: 1
name: Windows_2000_(TORRENT)
bootdisk: virtio0
onboot: 1
cores: 2
boot: cd
freeze: 0
cpuunits: 1000
acpi: 1
kvm: 1
virtio0: local:103/vm-103-disk-1.qcow2
virtio1: /dev/sde,backup=no
ide2: none,media=cdrom
vlan0: virtio=00:0C:29:07:21:F0,virtio=00:0C:29:07:21:FA

In this VM I had only clean Windows 2000 Professional and two processes of uTorrent.

 

[udo]

Hi,
you can try the e1000-driver instead of virtio (but i think not, that's solve the issue).
Sometimes i got strange effects with openvz on the 2.6.32-kernel (but normal the whole node freeze). Can you try the 2.6.18-kernel or do you need driver from 2.6.32?

Udo