Windows VM stopped unexpectedly at ~4am according to its Event Viewer, no relative info in host's logs

pgis

New Member
Jun 11, 2021
27
3
3
123
Looked in syslog in the Web UI - nothing other than storage checks.
Looked in `/var/log/kern.log` as well - nothing logged during that period.

It also seemed to have an issue as soon as I restarted the VM. After the Windows logo posted, it was killed by the OOM Killer according to the logs. Not sure if this may just be another issue or not. I'm doing some reading up on the memory management situation too. Could be that RAM is over-provisioned somehow... If it ran out of memory at ~4am I would expect to see OOM Killer entries around that time...

Thanks for any ideas!

edit: pve 7.2, and Win VM is Win 10 with updates disabled and no access to internet.
 
This happened a second time, and now there's an entry for OOM killer... will allow for host to use more RAM and see what happens...
 

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!