These steps have resolved my issue.If the 5.13 kernel is not in the list then install it with
Will watch my VMs for a week to see if it really helpedCode:apt install pve-kernel-5.13.19-6-pve
Thanks all!
These steps have resolved my issue.If the 5.13 kernel is not in the list then install it with
Will watch my VMs for a week to see if it really helpedCode:apt install pve-kernel-5.13.19-6-pve
I hope this can be fixed with Kernel 5.15 as well.These steps have resolved my issue.
Thanks all!
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 hope this can be fixed with Kernel 5.15 as well.
do you think proxmox plan on releasing a new ISO image as the 7.2 runs 5.15I 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....
Why? You can always install an older/alternative Kernel after Setup....do you think proxmox plan on releasing a new ISO image as the 7.2 runs 5.15
And do you have Intel-Microcode installed?goot morning
Installed a Windows Server 2019 last week - same issue - in average 1 shutdown per day. mostly in the night around 4 am.
MyHost:
View attachment 37501
Did you change the kernel version to "5.13.19-6-pve"?Since the last update of kvm few days ago I didn't have cpu error on windows machines, but still have to have Async IO set to threads or native on vm's installed on samba share
After switch kernel "pve-kernel-5.13.19-6-pve". no more crashes my windows vm for 3days.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
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.After switch kernel "pve-kernel-5.13.19-6-pve". no more crashes my windows vm for 3days.
Microcode is ok when it's first crash.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.
proxmox-boot-tool kernel list
proxmox-boot-tool kernel pin 5.15.35-1-pve
nano /etc/default/grub
change this line
GRUB_CMDLINE_LINUX_DEFAULT="quiet mitigations=off"
update-grub2
reboot
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.35-1-pve root=/dev/mapper/pve-root ro quiet mitigations=off
check if you boot with grub or systemd-boot - as described in the reference documentation:and update grub config like this:
boot-tool refreshcheck 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)
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.35-1-pve root=/dev/mapper/pve-root ro quiet mitigations=off
the command is proxmox-boot-tool ?boot-tool refresh
-bash: boot-tool: command not found
systemd-boot not installed my system. copy pase problem . I want to copy that:the command is proxmox-boot-tool ?
:~# systemd-boot
-bash: systemd-boot: command not found
again wrong - please read the docmentation I linkedsystemd-boot not installed my system. copy pase problem . I want to copy that:
proxmox-boot-tool status
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-pve
and update grub config like this:
afer reboot :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=off
will it be work without vm crash ?