[Bug 1855617] Re: savevm with hax saves wrong register state

[Thomas Huth]

The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.

If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.

Thank you and sorry for the inconvenience.


** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1855617

Title:
  savevm with hax saves wrong register state

Status in QEMU:
  Incomplete

Bug description:
  I use qemu-i386 with IntelHaxm on Windows 10 x64 host with Windows 7 x86 
guest. I run the guest till OS loads and create a snapshot with savevm, then 
close qemu, run it again and try to load the snapshot with loadvm. The guest 
crashes or freezes. I dumped registers on snapshot creation and loading (in 
Haxm) and found that they are different.
  When returning from Haxm in hax_vcpu_hax_exec, there is no regular register 
read. I found hax_arch_get_registers function which reads registers from Haxm 
and is called from a synchronization procedure. I placed a breakpoint on it, 
ran qemu and found that it is hit one time during guest OS boot. Exactly these 
registers where saved in the snapshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1855617/+subscriptions