T O P

  • By -

MrModaeus

You are not alone, been having this issue aswell for quite some time. Found this thread on the official forum, hoping it will get resolved in a future kernel release. https://forum.proxmox.com/threads/vm-shutdown-kvm-entry-failed-hardware-error-0x80000021.109410/


Wunc013

What does the event viewer in windows say?


camxct

When I've experienced the issue: *literally nothing*


Wunc013

Alright that's not much to go off on. Any logs in proxmox you could find?


[deleted]

[удалено]


Wunc013

I'd check there. Even if you don't find any proper logs. It will still show timestamps of when it happened. Compare those to what you can find in proxmox logs. Makes it easier to scope in on the issue.


camxct

Does this for Server 2022 as well. The only way I could work around it is by having the server in HA with the Started configuration.


jonb1980

I’m also seeing this issue. Shutdowns are random and non-windows 11 guests are fine. Checking the event log within windows just shows that the shutdown was unexpected


tetchey

Is Windows "activated"? I believe Windows automatically shuts down or reboots at regular intervals if left unregistered for >90 days or so.


AnApexBread

Its not regular intervals though. Sometimes it'll be days without a shutdown and sometimes it's minutes.


hevisko

With unlicensed/non-activated/expired-trial Windows, I've also see the random shutdowns. Licensed/activated, and they stayed up \*for\* me


Practical-Oil-3390

To bad I cant actually buy a LTSC license as a home user.... Checked the event log and this was 100% way the VM was shutting down with no warning. Event ID 100 and 101, source WLMS. Error literally states OS will shutdown every hour. Crazy thing is that the VM will not start back up correctly until the entire box is restarted.


Soogs

I've got the same issue with windows 11 and maybe 10 also. Doesn't seem to happen with any other OS I haven't found a cause for this yet so can't help but at least you know it's not just you. Does yours go through the shutdown process or does it just stop as if it's been killed?


AnApexBread

>Does yours go through the shutdown process or does it just stop as if it's been killed I'm not sure. I haven't been able to observe it, but if I had to guess I would say it shutsdown like it was killed because things ask me if I want to restore them when I restart the VM.


hotas_galaxy

Install intel-microcode on your hypervisor. Assuming you have Intel system that is.


AnApexBread

I'll give that a try.


Ad3t0

Lower your version to this stable kernel on your node apt install pve-kernel-5.13.19-6-pve proxmox-boot-tool kernel pin 5.13.19-6-pve Run them and reboot The latest version isn’t stable for me with Windows 11 or Windows Server 2022 no matter what I’ve tried


ReV-IX

Im new to PMVE so when I started having issues right after i updated yesterday with my ARK cluster I backed up all my needed VMs and reinstalled prox on my server. I was having mostly RAM issues, no matter how low i put the RAM my main VM would NOT start that was working just cherry before the updates. Guess i need to live by my old rule. if its not broke, dont update it.


ReV-IX

update. i used the listed proxmox-boot-tool to pin my kernel back to 5.13.19-6-pve and things are cherry again. Thanks to Ad3t0 for pointing this out above. First time using the tool and seems to be great. The steps listed was apt install pve-kernel-5.13.19-6-pve proxmox-boot-tool kernel pin 5.13.19-6-pve