Windows Server 2012 R2 on Proxmox 5.1-36 freezing without reason

M

Mecanik

Well-Known Member
Mar 2, 2017
173
4
58
32
Hello,

After I used out all my options, I feel like you guys are the only ones that can advise me or point me to the problem. Basically I have a node running Proxmox 5.1-36 and a running VM with Windows Server 2012 R2 link cloned from a template that I freshly prepared.

Node specs:
  • Intel i7-7700K OC
  • 64GB DDR4 2400 MHz
  • 2x450GB NVMe
Template specs:
  • Windows Server 2012 R2 official image from Microsoft with all updates to date
  • QEMU agent installed
  • All VirtIO drivers installed
  • Ballon services installed and running
VM specs:
  • 32 GB RAM, with "Automatically allocate memory within this range" ( 4096 - 32768 )
  • 1 CPU Sockets and 4 Cores, kvm64
  • 200 GB HDD, no cache or other options, in .qcow2 format
  • VirtIO network device
  • KVM virtualization
  • OS Type: Microsoft Windows 8.x/2012/2012r2
  • SCSI Controller: VirtIO SCSI
  • BIOS: Default (SeaBios)
  • Qemu agent: yes
The node is in a very good condition, so I cannot complain/blame that. The VM freezes without any reason in random times, and windows even logs does not show anything.

I have tried to swap RAM options to "fixed" + "balooning", same result. I have also tried to switch CPU options, same result. I have tried basically everything, and I cannot believe this.

I have a dozen other nodes running Proxmox 4.4 and I never had such issues...

Can you please advise me what to do ? I really want to use version 5 of Proxmox.

Many Thanks
 
Please also add the output of:

> pveversion -v
 
tom said:
Please also add the output of:

> pveversion -v
Click to expand...

Hi tom, sure here you go:

  • proxmox-ve: 5.1-26 (running kernel: 4.13.4-1-pve)
  • pve-manager: 5.1-36 (running version: 5.1-36/131401db)
  • pve-kernel-4.13.4-1-pve: 4.13.4-26
  • pve-kernel-4.10.17-1-pve: 4.10.17-18
  • libpve-http-server-perl: 2.0-6
  • lvm2: 2.02.168-pve6
  • corosync: 2.4.2-pve3
  • libqb0: 1.0.1-1
  • pve-cluster: 5.0-15
  • qemu-server: 5.0-17
  • pve-firmware: 2.0-3
  • libpve-common-perl: 5.0-20
  • libpve-guest-common-perl: 2.0-13
  • libpve-access-control: 5.0-7
  • libpve-storage-perl: 5.0-16
  • pve-libspice-server1: 0.12.8-3
  • vncterm: 1.5-2
  • pve-docs: 5.1-12
  • pve-qemu-kvm: 2.9.1-2
  • pve-container: 2.0-17
  • pve-firewall: 3.0-3
  • pve-ha-manager: 2.0-3
  • ksm-control-daemon: 1.2-2
  • glusterfs-client: 3.8.8-1
  • lxc-pve: 2.1.0-2
  • lxcfs: 2.0.7-pve4
  • criu: 2.11.1-1~bpo90
  • novnc-pve: 0.6-4
  • smartmontools: 6.5+svn4324-1
  • zfsutils-linux: 0.7.3-pve1~bpo9
Also, I noticed that it enters in KSM very slow compared to my other Proxmox 4.4... it stays at 80% RAM a lot until it enters in KSM.
 
I know this probably isn't it in your case, but I recently ran into a situation where I had somehow created a logical thin volume disk which was (potentially) larger than the logical volume it existed on. So the Windows guest thought it had plenty of room, but the volume was maxed out. I saw a 100% usage on one of my storages in the web gui and I had to do an lvextend

Mine was locking up when it tried to write files.
 
tom said:
you can compare your package list with the package list on:

https://pve.proxmox.com/wiki/Downlo...Proxmox_Virtual_Environment_5.x_to_latest_5.1
Click to expand...

I don't get it, I have more kernel versions now:

  • proxmox-ve: 5.1-38 (running kernel: 4.13.13-5-pve)
  • pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)
  • pve-kernel-4.13.4-1-pve: 4.13.4-26
  • pve-kernel-4.13.13-5-pve: 4.13.13-38
  • pve-kernel-4.10.17-1-pve: 4.10.17-18
  • 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-20
  • 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-16
  • pve-qemu-kvm: 2.9.1-6
  • 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.4-pve2~bpo9
 
I removed the other kernels, and left only
  • pve-kernel-4.13.13-5-pve: 4.13.13-38
As in the documentation. Hope the problem is gone...
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back