On Mon, 2023-12-11 at 09:54 +0200, James Gowans wrote: > > > > What problem are you running into with your rebase that worked with > > reboot notifiers that is not working with syscore_shutdown? > > Prior to this commit [1] which changed KVM from reboot notifiers to > syscore_ops, KVM's reboot notifier shutdown callback was invoked on > kexec via kernel_restart_prepare. > > After this commit, KVM is not being shut down because currently the > kexec flow does not call syscore_shutdown. I think I missed what you're asking here; you're asking for a reproducer for the specific failure? 1. Launch a QEMU VM with -enable-kvm flag 2. Do an immediate (-f flag) kexec: kexec -f --reuse-cmdline ./bzImage Somewhere after doing the RET to new kernel in the relocate_kernel asm function the new kernel starts triple faulting; I can't exactly figure out where but I think it has to do with the new kernel trying to modify CR3 while the VMXE bit is still set in CR4 causing the triple fault. If KVM has been shut down via the shutdown callback, or alternatively if the QEMU process has actually been killed first (by not doing a -f exec) then the VMXE bit is clear and the kexec goes smoothly. So, TL;DR: kexec -f use to work with a KVM VM active, now it goes into a triple fault crash. JG _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
