Windows Server 2016 freezing

[Enzo Damato]

I have a Windows Server Standard 2016 VM running Exchange server that is freezing every time it is booted up. I have checked disk space, and it is not an issue. When the freeze occurrs, I can not interact with the VM or ping it on the network.

Here is the output of pveversion -v

proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

 

[sb-jw]

Could you send us the VM Config (qm config VMID)?

 

[Raikoryu]

I have the same problem, and since the author didn't come back, here's my own config:

agent: 1
bootdisk: scsi0
cores: 2
ide2: local:iso/17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us_1.iso,media=cdrom
memory: 8192
name: WinServer
net0: virtio=D6:E7:9B:54:0D:XX,bridge=vmbr0
numa: 0
ostype: win10
sata0: /dev/sdd2,size=732.4G
scsi0: local-lvm:vm-102-disk-1,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=f60afaf8-4670-48b0-9903-fe86axxxxxx
sockets: 1

Proxmox 5.2.1 / Windows Server 2019

 

[SamirD]

I have the same problem, and since the author didn't come back, here's my own config:

agent: 1
bootdisk: scsi0
cores: 2
ide2: local:iso/17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us_1.iso,media=cdrom
memory: 8192
name: WinServer
net0: virtio=D6:E7:9B:54:0D:XX,bridge=vmbr0
numa: 0
ostype: win10
sata0: /dev/sdd2,size=732.4G
scsi0: local-lvm:vm-102-disk-1,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=f60afaf8-4670-48b0-9903-fe86axxxxxx
sockets: 1

Proxmox 5.2.1 / Windows Server 2019

Are you running 2019 or 2016 like the OP?

 

[Raikoryu]

I'm running 2019.

 

[sb-jw]

You should update to the new PVE 6 and re-check if the problem still existing.
From release to release, the support for windows are better. So Server 2019 is a bit newer, maybe a upgrade to PVE 6 would help to solve this.

 

[mac.linux.free]

I also got this issue on an 2016 terminalserver.

I got rid of it not using virtio-scsi but virtio-block. So for now it is fixed at least for me.

btw. I´m using virtio drivers 0.1.173.6

 

[Raikoryu]

Thank you.
Subsidiary question: is it possible to upgrade without losing my VMs and having to reinstall from scratch?
I couldn't find any way to do it easily through a USB stick, for example.
Thank for the help.

 

[SamirD]

Thank you.
Subsidiary question: is it possible to upgrade without losing my VMs and having to reinstall from scratch?
I couldn't find any way to do it easily through a USB stick, for example.
Thank for the help.

Upgrade windows or Proxmox?

 

[mac.linux.free]

Thank you.
Subsidiary question: is it possible to upgrade without losing my VMs and having to reinstall from scratch?
I couldn't find any way to do it easily through a USB stick, for example.
Thank for the help.

Sure you can. Shutdown VM. Add Virtio-Block device. Start VM. Install drivers. Shutdown VM. Delete added Virtio-Block. Detach SCSI-device. Attach HDD with Virtio-Block as storage. Change boot priority in options. Start VM.

 

[Raikoryu]

I want to upgrade Proxmox. Thanks.

 

[mac.linux.free]

https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0