Some windows server 2003 are shutting down automatically in Proxmox VE 5.1

[jarenas]

Hello,

Since a few days, some mv WS2003 are shutting down automatically (not forced stops). The vm are shutting down as if someone pressed start, shut down. After that, when I start the machine I found in the event viewer, the next thing:

Event ID 6008 "The previous system shutdown at Time on Date was unexpected."

This is happening only with some windows server 2003 machines.

Edit: not only ws2003, there are also some ws2008 and ws2012 that are shutting download randomly.

 

[wolfgang]

Hi,

are your Windows key valid because Windows turn off if you have no valid Keys.

Or do you see anything in the syslog?

 

[jarenas]

Hi,

are your Windows key valid because Windows turn off if you have no valid Keys.

Or do you see anything in the syslog?

Yes all of them are valid keys, in the windows syslog I only saw this [Event ID 6008 "The previous system shutdown at Time on Date was unexpected."], and in the proxmox syslog I saw nothing, I saw only a backup that was running when it happened.

Could it be a problem because of the backup?

 

[wolfgang]

Which version do you use?

pveversion -v

 

[jarenas]

Which version do you use?

pveversion -v

This version:
proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)

 

[wolfgang]

Please send the output of

pveversion -v

 

[jarenas]

Please send the output of

proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
pve-manager: 5.1-41 (running version: 5.1-41/0b958203)
pve-kernel-4.13.13-2-pve: 4.13.13-32
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-18
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

 

[davlaw]

Is this by chance during a backup? Because I was lazy there are one or 2 vm that I did not install virtio and found that they did not survive backups.

 

[jarenas]

Is this by chance during a backup? Because I was lazy there are one or 2 vm that I did not install virtio and found that they did not survive backups.

Oh, maybe this is the problem, my vm aren't virtio too.

 

[davlaw]

Did that help any?

 

[jarenas]

Did that help any?

I couldn't stop yet the vm, because they must be working until I have a backup vm, so I can't test it yet. I'll post the results when the changes have been done.

Sorry for my English.

 

[sumsum]

Do they realy Shut down or just disconnect the Network ?

 

[jarenas]

Do they realy Shut down or just disconnect the Network ?

They totally shutdown

 

[Vasu Sreekumar]

I faced another issue with Promxox 5.1-46 and windows 2003.

After few hours it shows blue screen.

I tried all possible combinations of CPU, Drive and other settings, still same issue.

It was a running KVM on Proxmox 3.4, issue started after migrating to 5.1.46.

Any suggestions?

 

[jarenas]

I have just changed the hard drives to virtio, I'll say next week if they are working fine after the backups

 

[Sorcerer]

I have the same Problem with an old Win2003 VM and ProxMox 5.1
Will also try to change the hard drives to virtio and will report if it helps.

 

[1nerdyguy]

I hate to say it, but don't expect this to be fixed. Win2k3 is dead and gone, and developing fixes for a dead OS more than likely isn't a top priority. I'd recommend instead of wasting time troubleshooting the 2k3 issue, put your time into migrating those servers to a newer, supported OS.