apt install proxmox-kernel-6.2.16-12-pve
Yes, this newer kernel should also fix the 100% CPU freeze bug for Windows VMs.
A reboot will cause the new kernel to be booted.
In case you cannot reboot your host, you could take a look at KernelCare for kernel live patching. Unfortunately they only have support up to Proxmox VE 7 for now.
root@stu:~# pveversion -v
proxmox-ve: 8.0.2 (running kernel: 6.2.16-12-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.3
proxmox-kernel-6.2.16-12-pve: 6.2.16-12
proxmox-kernel-6.2: 6.2.16-12
proxmox-kernel-6.2.16-10-pve: 6.2.16-10
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.5
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.8
libpve-guest-common-perl: 5.0.4
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.2-1
proxmox-backup-file-restore: 3.0.2-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.3
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.8-2
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-5
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.7
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1
root@stu:~# uname -r
6.2.16-12-pve
root@stu:~# qm config 101
agent: 1
balloon: 2048
bios: ovmf
boot: order=scsi0
cores: 2
cpu: host
efidisk0: cpool-01:vm-101-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hotplug: disk,network,usb,memory,cpu
machine: pc-q35-8.0
memory: 4096
meta: creation-qemu=8.0.2,ctime=1692891555
name: SELMA
net0: virtio=0A:52:7B:37:D3:5B,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win11
scsi0: cpool-01:vm-101-disk-1,cache=writeback,discard=on,iothread=1,size=80G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=d9802007-9108-4e71-887c-143523931f00
sockets: 1
startup: order=1,up=120
vga: qxl
vmgenid: c6c99b82-9bc6-425b-b306-2561223767c2
if you are experiencing a similar issue, please share the output ofAny news on that issue?
pveversion -v
, the VM configuration and some information about your host, e.g. CPU, RAM, used storages, etc.. Anything interesting in the system logs/journal around the time the issue happens?