Search results

Cool. Thanks for digging, I found some of the same links while looking into this. While I wait for the patch going into KVM, what is the different ways to prevent this? Is there anything I can do to disable SSM and/or something on host or VM? (bios/kernel/proxmox/vm-config) - except to stay on...

root@delta:/var/log# qm config 108 agent: 1 boot: c bootdisk: scsi0 cipassword: ********** ciuser: root ide2: ceph:vm-108-cloudinit,media=cdrom,size=4M ipconfig0: ip=dhcp memory: 2048 name: web net0: virtio=36:33:E5:EC:7A:6F,bridge=vmbr0 onboot: 1 scsi0...

So from the changelog pve-qemu-kvm (6.0.0-4) bullseye; urgency=medium * drop the ancient workaround that force disabled SMM due to observing VM hangs on old kernel versions. * monitor/qmp: fix race with clients disconnecting early resulting in other clients receiving a message...

Downgrading to those three packages and everything is good again. So this seems to be a regression going from pve-qemu-kvm 6.0.0-3 to 6.0.0-4

Hi. Last night I did a dist-upgrade of the my whole home 3 node proxmox cluster. I was allready 7.0 and upgraded a few packages to their latest version root@foxtrot:/var/log# egrep " (upgrade) " dpkg.log 2021-09-14 13:35:30 upgrade libpve-storage-perl:all 7.0-10 7.0-11 2021-09-14 13:35:31...