VM shutdown, KVM: entry failed, hardware error 0x80000021

[samuele]

If you still have the time @t.lamprecht uploaded a new kernel 5.15.39-4 yesterday - which contains the same fix, but in a version that is more likely to get merged upstream - so testing would be much appreciated!


In general I'd say as long as there is a kernel on the machine that does boot and work - you can of course remove old ones (you can always reinstall them later if you really want to) - but make sure that you have a running kernel left

Hi,
Some minutes ago I installed the new kernel version 5.15.39-4 and restarted the node.
I also installed the new version pve-kernel-helper.
After one week I will reply this post with the feedback about it.

Thanks!

 

[samuele]

Hi,
Some minutes ago I installed the new kernel version 5.15.39-4 and restarted the node.
I also installed the new version pve-kernel-helper.
After one week I will reply this post with the feedback about it.

Thanks!

Hi,
I've installed the new kernel on other two servers and no errors occurred.
All VMs are up and stable

 

[RedVortex]

Upgraded to 5.15.39-4 on 3 servers that were having the issue and the Windows VM have been stable for the last 2 weeks. It does seem there is a slight performance impact with this new kernel though but at least it is stable.

Thanks for the fix !

 

[piggie-mickie]

Short update: I have upgraded to 5.15.39-4 a week ago and also removed the setting kvm.tdp_mmu=N
So far all my VM are running stable and do not crash during backup. Especially my Exchange server was an issue.

But now I have another issue after this change: almost each day I have at least one VM which won't be backed up by PBS, I get the error similar like: backup write data failed: command error: protocol canceled.

Then I usually was able to backup this machine individually in offline mode. But often next day I had another VM with similar issue.

Now I have reverted the mmu setting kvm.tdp_mmu=N but keep the kernel version 5.15.39-4 and all backups are running normal so far. The PBS server is also a VM running on same ProxMox host and the backup target is a Synology NAS.

 

[timproxmox]

If you still have the time @t.lamprecht uploaded a new kernel 5.15.39-4 yesterday - which contains the same fix, but in a version that is more likely to get merged upstream - so testing would be much appreciated!


In general I'd say as long as there is a kernel on the machine that does boot and work - you can of course remove old ones (you can always reinstall them later if you really want to) - but make sure that you have a running kernel left

Just wondering if the fixes has been added to the upstream yet or the estimated time on the merge?

 

[t.lamprecht]

What do you mean with upstream? Our kernel hast the fix since a while and is rolled out on all supported repositories.

 

[timproxmox]

What do you mean with upstream? Our kernel hast the fix since a while and is rolled out on all supported repositories.

Apologies, I am not familiar with your processes. I thought when @Stoiko Ivanov mentioned "is more likely to get merged with upstream" that it was still in a test phase. We have applied the fix and thank you for this community which helped bring closure to this issue.

 

[trisweb]

Thanks for the fix! Could someone potentially update this wiki page to remove reference to the workaround and replace with a note about the updated kernel with fix? https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Older_Hardware_and_New_5.15_Kernel

 

[t.lamprecht]

Thanks for the fix! Could someone potentially update this wiki page to remove reference to the workaround and replace with a note about the updated kernel with fix? https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Older_Hardware_and_New_5.15_Kernel

Yeah makes sense to do, and done now.

 

[Testani]

Hi,
I've installed the new kernel on other two servers and no errors occurred.
All VMs are up and stable

How to update? apt update / upgrade keep me @
proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)

 

[Neobin]

How to update? apt update / upgrade keep me @
proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)

https://forum.proxmox.com/threads/im-unable-to-upload-files-to-my-proxmox-server.114541/#post-495356

PS.: Never use only: apt upgrade with Proxmox products; ever use: apt full-upgrade (or: apt dist-upgrade)!:
https://forum.proxmox.com/threads/proxmox-ve-7-1-released.99847/page-8#post-463941

 

[moonman]

Hello, I'm suffering a problem with windows server 2022 on proxmox VE, no hyperV installed.
That was recently updated from WS2008R2, and we had 0 problems.

The machine only hangs for a while while doing lots of iops, always when using windows disk optimizer. maybe syncing with google drive for the first time. Maybe in 10-15 minutes comes back, it depends on the load. No IO delay on the hypervisor, maximum was 3.15% this week.

It looses connectivity, qemu tools drop comunication, the machine display on the hypervisor doesn't work, but it's working by itselft after a while it recovers conectivity and it doesn't restart.
It has two disks, one conected to a ZFS NVME RAID1 for the OS, and another to an LVM RAID1 for DATA.

Moved the data disk to another pool, made no differece.
Tried the disks with native and io_uring Async IO, made no difference.
Reduced read/write limits and op/s on disks, made no difference.
Tried with several proxmox kernel 5.13 and 5.15, made no difference.




Syslog throws this:

pvedaemon[2320607]: VM 105 qmp command failed - VM 105 qmp command 'guest-network-get-interfaces' failed - got timeout

I would create a new thread. I don't believe the issue in this thread is related to what you are experiencing.

 

[MarkyMark]

The issue in my case was, Win10 Pro VM was going stop and then start again periodically (~1..5mins). The solution seems to be disabling the C-state option in BIOS as described in this post:
https://www.reddit.com/r/Proxmox/comments/16rw5kk/proxmox_8_not_stable/