diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/kvm/1534382 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/kvm/1534382')
| -rw-r--r-- | results/classifier/gemma3:12b/kvm/1534382 | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/kvm/1534382 b/results/classifier/gemma3:12b/kvm/1534382 new file mode 100644 index 000000000..c532bdb77 --- /dev/null +++ b/results/classifier/gemma3:12b/kvm/1534382 @@ -0,0 +1,21 @@ + +loadvm makes Windows 7 x86 guest crash with some CPUs + +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. \ No newline at end of file |