Windows 2003 64bit stability?

[royceybaby]

Hi,

Is anyone else having problems with Windows 2003 64bit VM's locking up with 100% CPU and/or blue screening with Windows stop errors?

We are running Proxmox 1.5 on the 2.6.32 kernel.

Thanks,
Royce

 

[royceybaby]

We still can't work out why our 64bit windows 2003 VM's are locking up with 100% CPU. Has anybody else seen this problem or can help us find a solution?

I have one such machine in that state now if there is anything I can do to narrow down the problem.

Thanks,
Royce

 

[yatesco]

On the host, can you post the results of:

- top
- iotop (you might need to install this)
- pverversion -v

also, how many other virtual machines are there?

on the guest, can you print a screen shot of task-manager showing all processes ordered by CPU (highest first). I expect it will be 'svchost' though which isn't very helpful

 

[royceybaby]

There are 5 vm's in total running from this node (we have a two node pve cluster). We cannot seem to get into the windows virtual machine as it seems to have hanged and all we get via the VNC console is a grey screen.

Please find below the results of the commands.

top

top - 15:02:16 up 27 days,  4:04,  1 user,  load average: 0.09, 0.30, 0.27
Tasks: 228 total,   1 running, 227 sleeping,   0 stopped,   0 zombie
Cpu(s): 16.3%us,  8.3%sy,  0.0%ni, 75.1%id,  0.2%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:  16424700k total, 15962832k used,   461868k free,  5094992k buffers
Swap: 15728632k total,   732232k used, 14996400k free,   230484k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
32215 root      40   0 4298m 4.0g 1088 S  100 25.7   2046:23 kvm
   87 root      25   5     0    0    0 S   27  0.0   7036:27 ksmd
31815 root      40   0 3268m 2.8g  976 S   23 18.0   5489:59 kvm
30968 root      40   0 2240m 2.0g  972 S   21 12.6   4431:54 kvm
10164 root      40   0 4228m 3.6g 1100 S   12 23.3   5347:26 kvm
16325 root      40   0 4288m 4.0g  976 S    8 25.6   2024:05 kvm
 2969 www-data  40   0  257m  36m 4252 S    4  0.2   0:00.57 apache2
31592 root      40   0 88248  23m 2120 S    2  0.1   0:03.08 pvedaemon

iotop

Total DISK READ: 0 B/s | Total DISK WRITE: 233.46 K/s  PID USER      DISK READ  DISK WRITE   SWAPIN    IO>    COMMAND
2979 root           0 B/s  233.46 K/s  0.00 %  0.00 % kvm -monitor unix:/var/run/qemu-server/112.mon,server,nowait -vnc unix:/var/run/qemu-server/1
3584 root           0 B/s       0 B/s  0.00 %  0.00 % pvedaemon worker   
1 root           0 B/s       0 B/s  0.00 %  0.00 % init [2]   
2 root           0 B/s       0 B/s  0.00 %  0.00 % [kthreadd]   
3 root           0 B/s       0 B/s  0.00 %  0.00 % [migration/0]   
4 root           0 B/s       0 B/s  0.00 %  0.00 % [ksoftirqd/0]   
5 root           0 B/s       0 B/s  0.00 %  0.00 % [watchdog/0]   
6 root           0 B/s       0 B/s  0.00 %  0.00 % [migration/1]   
7 root           0 B/s       0 B/s  0.00 %  0.00 % [ksoftirqd/1]   
8 root           0 B/s       0 B/s  0.00 %  0.00 % [watchdog/1]   
9 root           0 B/s       0 B/s  0.00 %  0.00 % [migration/2]

pveversion

pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-4
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
ksm-control-daemon: 1.0-3

Thank you for your help.
Royce

 

[yatesco]

Without seeing what is happening in the windows machine....

I notice you are using a tiny bit of your swap file - have you overcommitted the memory on this machine? No idea if that is the problem (I thought the OS would just shut down the entire process, i.e. the entire machine so probably isn't the problem as the KVM process is still there).

How many VCPUs did you assign it? I have run into problems rebooting the machine with multiple VCPUs, but that was before proxmox - haven't tried it recently.

If nobody else offers anything, I would hard boot the guest, login with the console, restart it and see what happens. It it restarts properly then start task manager and watch what happens for a bit. Not very helpful - sorry.