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/hypervisor/1308341 | |
| 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/hypervisor/1308341')
| -rw-r--r-- | results/classifier/gemma3:12b/hypervisor/1308341 | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/hypervisor/1308341 b/results/classifier/gemma3:12b/hypervisor/1308341 new file mode 100644 index 000000000..c09748c1f --- /dev/null +++ b/results/classifier/gemma3:12b/hypervisor/1308341 @@ -0,0 +1,9 @@ + +Multiple CPUs causes blue screen on Windows guest (14.04 regression) + +Configuring a Windows 7 guest using more than one CPU cases the guest to fail. This happens after a few hours after guest boot. This is the error on the blue screen: +"A clock interrupt was not received on a secondary processor within the allocated time interval" + +After resetting, the guest will never boot and a new bluescreen with the error "STOP: 0x0000005c" appears. Shutting down the guest completely and restarting it will allow it to boot and run for a few hours again. + +The guest was created using virt-manager. The error happens with or without virtio devices. \ No newline at end of file |