Issues with Proxmox Windows 2016 VM unresponsive and can only be reset

koolandrew

Member
Jul 7, 2021
29
1
8
24
We have four nodes in a cluster with the same hardware. It is a Dell M910 blade server with loads of cpu and ram, nowhere near capacity. The VM is running up to 25% capacity of ram , 15% cpu and 80% hd. I have put the vm on a host where it is the only one, and updated that host to the lastest version.

The only way to get it back online is to reset it, any other methods do not work.

It has not occurred again since i did all this, but i have tried on two other hosts in the same cluster prior to this.

There are similar threads in the forum, but there normally seems to be an obvious issue like old firmware or cpu running too high.

Questions:
1. Are there specific logs that i should look at the see what the issue might be?
2. Should i upgrade the kernel. I have attached the host config, and it is a running a 5.x kernel, and i have seen online that there is a 6.x kernel. I have never done anything like this before, so i am cluless when it comes to this detail.

My concern is that it starts happening to some of my more mission critical vm's. This one is certainly annoying but a quick reset gets it up and running.

Any response on this

***Day later***
I thought i had sent this. It happened again about four hours ago...I am not sure what to do..it is the only vm on the host
I have attached the logs from the server, but i have just noticed now it is at 100% cpu..

1713664583499.png

i have reset the vm and here is the config.

qm config 12104
boot: order=virtio0;ide2
cores: 2
ide2: none,media=cdrom
machine: pc-i440fx-7.1
memory: 16384
meta: creation-qemu=7.1.0,ctime=1675992238
name: net3
net0: virtio=00:0c:29:2e:6c:21,bridge=vmbr0,firewall=1,tag=12
numa: 0
onboot: 1
ostype: win8
smbios1: uuid=bae0b39d-58e7-4bd2-aaa0-30f97a92771a
sockets: 4
virtio0: local-zfs:vm-12104-disk-0,format=raw,iothread=1,size=280G
vmgenid: d52ec29d-f6a9-473e-8495-54bb1ed452e0

And here is the logs from the host, i think it happened around 17:00
 

Attachments

  • proxmox-ve 8.1.0 (running kernel 5..txt
    1.9 KB · Views: 1
  • proxmox server logs.txt
    24.9 KB · Views: 1
Could it be a random rogue/broken process within your VM that took all the CPU and make everything else unresponsive?
 

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!

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!