Public bug reported:
Running qemu with kvm enabled and -cpu set to some of the more "modern" CPUs,
and having Windows 7 x86 as the guest.
After guest OS loads, start some app (I started "cmd"), then do "savevm".
After that, do some more activity (I closed cmd window and opened IE),
then do "loadvm" of the previously saved snapshot.
loadvm shows briefly the state that the system was in at the snapshot time,
then guest OS crashes (blue screen).
Originally I saw this problem on qemu 1.4.0,
then I also tried qemu 2.5.0 and found the same problem.
The CPUs that I tried were mostly those that support NX bit (core2duo,
qemu64, kvm64, Nehalem, etc.)
If I use the default CPU, or some other like qemu32/kvm32,
the problem does not occur.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1534382
Title:
loadvm makes Windows 7 x86 guest crash with some CPUs
Status in QEMU:
New
Bug description:
Running qemu with kvm enabled and -cpu set to some of the more "modern" CPUs,
and having Windows 7 x86 as the guest.
After guest OS loads, start some app (I started "cmd"), then do "savevm".
After that, do some more activity (I closed cmd window and opened IE),
then do "loadvm" of the previously saved snapshot.
loadvm shows briefly the state that the system was in at the snapshot time,
then guest OS crashes (blue screen).
Originally I saw this problem on qemu 1.4.0,
then I also tried qemu 2.5.0 and found the same problem.
The CPUs that I tried were mostly those that support NX bit (core2duo,
qemu64, kvm64, Nehalem, etc.)
If I use the default CPU, or some other like qemu32/kvm32,
the problem does not occur.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1534382/+subscriptions
