summary refs log tree commit diff stats
path: root/gitlab/issues_text/target_i386/host_missing/accel_missing/771
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-05-30 16:52:07 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-05-30 16:52:17 +0200
commit9260319e7411ff8281700a532caa436f40120ec4 (patch)
tree2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues_text/target_i386/host_missing/accel_missing/771
parent225caa38269323af1bfc2daadff5ec8bd930747f (diff)
downloadqemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz
qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip
gitlab scraper: download in toml and text format
Diffstat (limited to 'gitlab/issues_text/target_i386/host_missing/accel_missing/771')
-rw-r--r--gitlab/issues_text/target_i386/host_missing/accel_missing/77114
1 files changed, 14 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_i386/host_missing/accel_missing/771 b/gitlab/issues_text/target_i386/host_missing/accel_missing/771
new file mode 100644
index 000000000..9a8fb2117
--- /dev/null
+++ b/gitlab/issues_text/target_i386/host_missing/accel_missing/771
@@ -0,0 +1,14 @@
+No interrupts are delivered to the guest after rebooting Windows 98
+Description of problem:
+After Windows 98 is rebooted in QEMU, the guest freezes: the system is unresponsive to key presses and the boot splash animation halts.  The guest performs fine before the reboot.
+
+Closer examination reveals that no hardware interrupts are delivered to the guest.  BIOS Data Area variables like the keyboard buffer and the system clock are not updated.  Even non-maskable interrupts fail to be delivered, as witnessed by installing an option ROM that hooks interrupt vector 2 and issuing the `nmi` command in the monitor.
+
+The only remedy seems to be to exit the QEMU process entirely and launch it again.
+Steps to reproduce:
+0. Install Windows 98 into the guest.  (Since the normal installation process already involves a couple of reboots, it is possible to hit the issue already at step zero.)
+1. Boot it; it may be into Safe Mode, but the protected-mode graphical environment must at least attempt to load.  (I managed sometimes to reproduce the bug without the system having loaded fully.)
+2. Reboot. This may be a clean reboot, or it may be a hard reboot (`system_reset` or equivalent)
+3. Observe the system freeze.
+Additional information:
+None