Hi, since about half a year ago, we're getting user reports about guest reboot issues with KVM/QEMU[0]. The most common scenario is a Windows Server VM (2012R2/2016/2019, UEFI/OVMF and SeaBIOS) getting stuck during the screen with the Windows logo and the spinning circles after a reboot was triggered from within the guest. Quitting the kvm process and booting with a fresh instance works. The issue seems to become more likely, the longer the kvm instance runs. We did not get such reports while we were providing Linux 5.4 and QEMU 5.2.0, but we do with Linux 5.11/5.13/5.15 and QEMU 6.x. I'm just wondering if anybody has seen this issue before or might have a hunch what it's about? Any tips on what to look out for when debugging are also greatly appreciated! We do have debug access to a user's test VM and the VM state was saved before a problematic reboot, but I can't modify the host system there. AFAICT QEMU just executes guest code as usual, but I'm really not sure what to look out for. That VM has CPU type host, and a colleague did have a similar enough CPU to load the VM state, but for him, the reboot went through normally. On the user's system, it triggers consistently after loading the VM state and rebooting. So unfortunately, we didn't manage to reproduce the issue locally yet. With two other images provided by users, we ran into a boot loop, where QEMU resets the CPUs and does a few KVM_RUNs before the exit reason is KVM_EXIT_SHUTDOWN (which to my understanding indicates a triple fault) and then it repeats. It's not clear if the issues are related. There are also a few reports about non-Windows VMs, mostly Ubuntu 20.04 with UEFI/OVMF, but again, it's not clear if the issues are related. [0]: https://forum.proxmox.com/threads/100744/ (the forum thread is a bit chaotic unfortunately). Best Regards, Fabi
