VM shutdown, KVM: entry failed, hardware error 0x80000021
- Thread starter tzzz90
- Start date
I am sure they will be fixed. But we have already decided to stick with 5.13 and will be much more conservative the next couple of month with updates and specially with new kernels....
I saw 4 times same error after upgrade 7.2. PVE 7.2 host and windows server 2022,q35v6 guest with kvm64.
It crash every 8-12 hours
install intel microcode and check my host's VT settings in bios. not fixed yet
Update: I switched "pve-kernel-5.13.19-6-pve" kernel now
My host:
CPU(s)
8 x Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz (1 Socket)
Kernel Version
Linux 5.15.35-1-pve #1 SMP PVE 5.15.35-3 (Wed, 11 May 2022 07:57:51 +0200)
pve-manager/7.2-4/ca9d43cc
It crash every 8-12 hours
install intel microcode and check my host's VT settings in bios. not fixed yet
Update: I switched "pve-kernel-5.13.19-6-pve" kernel now
My host:
CPU(s)
8 x Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz (1 Socket)
Kernel Version
Linux 5.15.35-1-pve #1 SMP PVE 5.15.35-3 (Wed, 11 May 2022 07:57:51 +0200)
pve-manager/7.2-4/ca9d43cc
Attachments
Last edited:
After switch kernel "pve-kernel-5.13.19-6-pve". no more crashes my windows vm for 3days.
You can also check if current Kernel and Intel-Microcode or "Mitigation=off" in GRUB helps if you have time and accept that it might crash again.
It looks like this workaround also helps. Cause some day the "old" Kernel will be "not supported" so we need valid workarounds with current Versions.
Microcode is ok when it's first crash.
You said switch new kernel (5.15) :
Code:
proxmox-boot-tool kernel list
proxmox-boot-tool kernel pin 5.15.35-1-pveand update grub config like this:
Code:
nano /etc/default/grub
change this line
GRUB_CMDLINE_LINUX_DEFAULT="quiet mitigations=off"
update-grub2
reboot
Code:
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.35-1-pve root=/dev/mapper/pve-root ro quiet mitigations=offwill it be work without vm crash ?
Last edited:
check if you boot with grub or systemd-boot - as described in the reference documentation:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_edit_kernel_cmdline
(also verify that the parameter is active by checking the output of `cat /proc/cmdline` after reboot)
boot-tool refresh
-bash: boot-tool: command not found
it's look grub
after reboot :
Code:
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.35-1-pve root=/dev/mapper/pve-root ro quiet mitigations=off
Last edited:
systemd-boot not installed my system. copy pase problem
. I want to copy that:
Code:
:~# systemd-boot
-bash: systemd-boot: command not foundthat means my system use grub boot loader
again wrong - please read the docmentation I linkedsystemd-boot not installed my system. copy pase problem
the command would have been:
Code:
proxmox-boot-tool statusIn any case - since the commandline parameter shows up in /proc/cmdline - you're right and are using grub
Now I'm switched new kernel (5.15.35-1-pve) with "mitigations=off". I'm testing few days after inform you.
Wish me luck.