summary refs log tree commit diff stats
path: root/gitlab/issues/target_i386/host_missing/accel_missing/771.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_i386/host_missing/accel_missing/771.toml')
-rw-r--r--gitlab/issues/target_i386/host_missing/accel_missing/771.toml22
1 files changed, 0 insertions, 22 deletions
diff --git a/gitlab/issues/target_i386/host_missing/accel_missing/771.toml b/gitlab/issues/target_i386/host_missing/accel_missing/771.toml
deleted file mode 100644
index 67315483..00000000
--- a/gitlab/issues/target_i386/host_missing/accel_missing/771.toml
+++ /dev/null
@@ -1,22 +0,0 @@
-id = 771
-title = "No interrupts are delivered to the guest after rebooting Windows 98"
-state = "opened"
-created_at = "2021-12-13T16:30:39.299Z"
-closed_at = "n/a"
-labels = ["target: i386"]
-url = "https://gitlab.com/qemu-project/qemu/-/issues/771"
-host-os = "Debian"
-host-arch = "x86-64"
-qemu-version = "QEMU emulator version 6.1.0 (Debian 1:6.1+dfsg-8+b1)"
-guest-os = "Windows 98 Second Edition (the issue can be reproduced with the first edition as well)"
-guest-arch = "x86-32"
-description = """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."""
-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 = """None"""