Server 2003 Hangs on Restart

[Raymond Burns]

Anytime I restart KVM Windows Server 2003, it hangs and must be "Reset" via the web manager.

root@Node2:/var/log# pveversion -vpve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-22-pve
proxmox-ve-2.6.32: 3.0-107
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-22-pve: 2.6.32-107
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

VM .config

oot: cdn
bootdisk: ide0
cores: 2
ide0: local:101/vm-101-disk-1.qcow2,format=qcow2,size=100G
ide2: local:iso/Windows_Server_2003.iso,media=cdrom,size=603364K
memory: 2048
name: windows2003
net0: e1000=2E:C9:57:17:F7:93,bridge=vmbr0
onboot: 1
ostype: wxp
sockets: 1
startup: order=3

VM was using 2 sockets and 1 core. Successfully reporting 2 cores within Windows Task Manager. Had issue with reboot hanging
VM was changed to 2 cores and 1 socket. Successfully reporting 2 cores within Windows Task Manager. Has issue with reboot hanging

VM can successfully shutdown without any issues
VM OS is Windows Server 2003 Enterprise Edition with Service Pack 2
Latest Windows Updates have been applied
One driver issue remains with "PCI Device". Resolution may be http://pve.proxmox.com/wiki/Dynamic_Memory_Management, but there is no location given in the wiki to download BLNSVR.
Would this cause Windows 2003 Enterprise Edition to hang on a Windows Initiated Restart.

 

[kotakomputer]

See http://pve.proxmox.com/wiki/Windows_2012_guest_best_practices
[h=3]Prepare[/h]

• First, download VIRTIO drivers from here: http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/

This guide also applied to any Windows version, including: xp, 7 and 8, server 2000, 2003, 2008, and 2012.

 

[macday]

Anytime I restart KVM Windows Server 2003, it hangs and must be "Reset" via the web manager.

root@Node2:/var/log# pveversion -vpve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-22-pve
proxmox-ve-2.6.32: 3.0-107
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-22-pve: 2.6.32-107
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

VM .config

oot: cdn
bootdisk: ide0
cores: 2
ide0: local:101/vm-101-disk-1.qcow2,format=qcow2,size=100G
ide2: local:iso/Windows_Server_2003.iso,media=cdrom,size=603364K
memory: 2048
name: windows2003
net0: e1000=2E:C9:57:17:F7:93,bridge=vmbr0
onboot: 1
ostype: wxp
sockets: 1
startup: order=3

VM was using 2 sockets and 1 core. Successfully reporting 2 cores within Windows Task Manager. Had issue with reboot hanging
VM was changed to 2 cores and 1 socket. Successfully reporting 2 cores within Windows Task Manager. Has issue with reboot hanging

VM can successfully shutdown without any issues
VM OS is Windows Server 2003 Enterprise Edition with Service Pack 2
Latest Windows Updates have been applied
One driver issue remains with "PCI Device". Resolution may be http://pve.proxmox.com/wiki/Dynamic_Memory_Management, but there is no location given in the wiki to download BLNSVR.
Would this cause Windows 2003 Enterprise Edition to hang on a Windows Initiated Restart.

Hello,

I had the same problem. After installing the Hotfix from Micro$oft KB945119 the problem was gone.

Cheers
Mac

 

[cjmurray]

I had the same problem. After installing the Hotfix from Micro$oft KB945119 the problem was gone.

Apologies for my premature post; this seemed to be resolved in our environment with the above hotfix, however the issue has returned since. I'll troubleshoot further.

Chris

 

[macday]

Apologies for my premature post; this seemed to be resolved in our environment with the above hotfix, however the issue has returned since. I'll troubleshoot further.

Chris

I ended up troubleshooting win2k3...I migrated every active directory to zentyal...and every terminal server to win81...so problem´s gone

mac

 

[cjmurray]

Ah, that wasn't the answer I was hoping for!


I did some further troubleshooting before seeing a recommendation in another thread to reduce the number of virtual cores from 4 to 2, so I've used that workaround although not ideal.

Interesting that the hotfix did seem to resolve the problem temporarily though.




In case it's ever of any use to anyone, the troubleshooting was:


Boot into safe mode.
Restart. VM hangs. Not driver related?
Stop VM.


Start VM.
Now back in normal mode.
Restart. Hangs, as expected.
Stop VM.


Change NICs to realtek.


Start VM.
Restart. Still hangs, so maybe not NIC hardware related.
Stop VM.


Change NICs back to e1000.


Start VM.
Restart. still hangs, as expected. Just getting some consistency.
Stop VM.


Currently has 1 socket, 4 cores.
Changed to 1 socket, 2 cores.


Start VM.
Restart. Doesn't hang!
Restart one more time to double-check. Doesn't hang.


Gracefully shutdown.


Change to 2 socket, 2 cores.


Start VM.
Restart. Hangs. So it's the magical number '4'?
Stop VM.


Is it made any better by different CPU type? Change CPU type from KVM64 to Qemu64.


Start VM.
Restart. Hangs.
Stop VM.


Change CPU type back to KVM64, 4 sockets, 1 core.


Sticks at:
"Booting from ROM...
iPXE (PCI 00:13.0) starting execution..."


Change CPU type to 1 socket, 2 cores


Start VM
Restart. Doesn't hang. That'll do.



I also built a new VM from scratch with 1 socket and 4 cores, which also hung during the install (while it restarted), so although it looked like some VMware conversions were to blame initially, that turns out to not be the case.

 

[catimbal2012]

Good afternoon, I've been looking for the kb945119 update for a while and I can't find it anywhere for server 2003 standard, if anyone has it