1 files changed, 21 insertions, 0 deletions

diff --git a/gitlab/issues/target_i386/host_x86/accel_KVM/2609.toml b/gitlab/issues/target_i386/host_x86/accel_KVM/2609.toml
new file mode 100644
index 000000000..13a33780f
--- /dev/null
+++ b/gitlab/issues/target_i386/host_x86/accel_KVM/2609.toml
@@ -0,0 +1,21 @@
+id = 2609
+title = "Blue screen in Windows XP"
+state = "closed"
+created_at = "2024-10-05T09:30:01.873Z"
+closed_at = "2024-10-20T12:21:16.168Z"
+labels = ["accel: KVM", "guest: Windows", "host: x86", "target: i386"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/2609"
+host-os = "Ubuntu 24.04.1 LTS (GNU/Linux )"
+host-arch = "x86_x64"
+qemu-version = "9.1.0"
+guest-os = "n/a"
+guest-arch = "n/a"
+description = """When starting the installation of Windows XP  when using a virtioblk device you immediately get a bluescreen: `STOP: 0x000000A5 (0x00000002, 0x8A1A6008, 0xE1018808, 0x8A1B7F00)`. I think this happens even before it loads the SATA drivers that are slipstreamed in the ISO.
+
+After a lot of Googling about this error 0x000000A5 I found some posts suggesting that changing the machine type from `q35` to `pc-q35-2.10` solves the issue. And it worked. Anything above 2.10 (for example 2.11) and the bluescreens return.
+
+So I always used this solution, but in QEMU 9.1.0 it warns that `pc-q35-2.10` will be removed soon. This would mean there is no way anymore to install XP to a SATA disk unattendly."""
+reproduce = """1. Use a virtioblk disk and SATA drivers
+2. Start the Windows XP installer
+3. Bluescreen will appear"""
+additional = "n/a"