| Message ID | bug-215964-28872-hTIOr72Rhq@https.bugzilla.kernel.org/ (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [Bug,215964] nVMX: KVM(L0) does not perform a platform reboot when guest(L2) trigger a reboot event through IO-Port-0xCF9 | expand |
diff --git a/target/i386/cpu.c b/target/i386/cpu.c index e46ab8f774..008fd93ff1 100644 --- a/target/i386/cpu.c +++ b/target/i386/cpu.c @@ -5968,6 +5968,7 @@ static void x86_cpu_reset(DeviceState *dev) /* init to reset state */ env->hflags2 |= HF2_GIF_MASK; + env->hflags &= ~HF_GUEST_MASK; cpu_x86_update_cr0(env, 0x60000010); env->a20_mask = ~0x0;
https://bugzilla.kernel.org/show_bug.cgi?id=215964 --- Comment #5 from Sean Christopherson (seanjc@google.com) --- Definitely sounds like a QEMU bug. Jim pointed out that you might have an older version of QEMU, which seems likely given the fix went into v5.1.0 and lack of clearing HF_GUEST_MASK would result in the behavior you're seeing. Can you try running v5.1.0 or later? Specifically, something with this commit. commit b16c0e20c74218f2d69710cedad11da7dd4d2190 Author: Paolo Bonzini <pbonzini@redhat.com> Date: Wed May 20 10:49:22 2020 -0400 KVM: add support for AMD nested live migration Support for nested guest live migration is part of Linux 5.8, add the corresponding code to QEMU. The migration format consists of a few flags, is an opaque 4k blob. The blob is in VMCB format (the control area represents the L1 VMCB control fields, the save area represents the pre-vmentry state; KVM does not use the host save area since the AMD manual allows that) but QEMU does not really care about that. However, the flags need to be copied to hflags/hflags2 and back. In addition, support for retrieving and setting the AMD nested virtualization states allows the L1 guest to be reset while running a nested guest, but a small bug in CPU reset needs to be fixed for that to work. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>