diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:24:58 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:27:06 +0000 |
| commit | 33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch) | |
| tree | 406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1308341 | |
| parent | adedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff) | |
| download | qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip | |
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1308341')
| -rw-r--r-- | results/scraper/launchpad-without-comments/1308341 | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1308341 b/results/scraper/launchpad-without-comments/1308341 new file mode 100644 index 000000000..7bd2939ef --- /dev/null +++ b/results/scraper/launchpad-without-comments/1308341 @@ -0,0 +1,8 @@ +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 |