Server restarts unexpectedly without any alerts appearing in the monitoring tool.
Server restarts unexpectedly without any alerts appearing in the monitoring tool.
I'm running a windows server VM on proxmox and it randomly shuts down. The last one was the first one I was actually there to witness but it's happened a total of 6 times: (this is filtered to just show the unexpected shutdowns) When I go back in the log and look around the time the shutdown occurs there's nothing useful. The only thing in the log before it happens in a bunch of 'service x entered running state' & the 1 warning that there was 'No valid response received from manually configured peer time.windows.com' This is basically a fresh install of Server 2022, only thing running was some HFS servers, a discord bot, & a minecraft server. All of which have ran before without issue on the old install of Server 2019.
Bingo, PROXMOX is showing this log: June 24 17:57:27 proxmox QEMU[3753287]. KVM encountered a failure with hardware error 0x80000021. If you're using an Intel machine without unrestricted mode, the issue likely stems from the guest entering an invalid state. This could happen if the guest is running in big real mode, which isn't supported on newer Intel chips. The kernel suggests setting kvm_intel.dump_invalid_vmcs=1 to view internal KVM status.
Details from the log show specific registers and flags indicating a CPU assertion failure related to CPU attributes. After several checks, it appears the system is trying to access virtualized resources but something went wrong during execution.
Later entries note that port 2 and port 3 entered disabled states, followed by attempts to clean up and finalize the session. By the end, everything appears to be running in a virtualized environment.
The VM stayed operational for nearly 13 hours, which is unusual for its performance. This suggests it wasn’t in sleep mode, even though most server setups disable that feature by default. I’m currently reviewing a PROXMOX Forum discussion about the hardware error code 0x80000021 in your logs—it matches the issue you’re experiencing. Much of the initial discussion focuses on nested virtualization, Proxmox version 7.2, kernel releases, and Intel processors like Skylake. Are you using any nested virtualization? Which CPU model are you running? What PROXMOX version and kernel are you on? Feel free to share more details if it would be useful.
Confirmed Hyper-V is disabled. Adjusted VM's CPU setting to 'kvm64' based on forum advice, but effectiveness remains uncertain until the system stops responding.
What BIOS version and chipset are you running? Do you have the same issue when using a standard 2022 reference image?
Everything functioned smoothly in 2019, suggesting a shift occurred with 2022 affecting QEMU/KVM. The specific change remains unclear. I've been using PROXMOX for many years, but this isn't an issue I've encountered before. Keep an eye on it and let me know if it arises within the next day.
It hasn't occurred yet; the system is still active. 2019 ran directly on hardware, which means the issue likely stems from something related to Proxmox.
Exploring the PROXMOX forum thread more thoroughly could be useful if the problem continues. The two scenarios seem very similar, making it a potentially helpful reference. How long have you been using this new setup? A day, a week, or a month? These recurring intermittent issues are the hardest to identify and resolve.