1 files changed, 22 insertions, 0 deletions

diff --git a/gitlab/issues/target_i386/host_missing/accel_missing/2897.toml b/gitlab/issues/target_i386/host_missing/accel_missing/2897.toml
new file mode 100644
index 000000000..989083814
--- /dev/null
+++ b/gitlab/issues/target_i386/host_missing/accel_missing/2897.toml
@@ -0,0 +1,22 @@
+id = 2897
+title = "Can't boot SeaBIOS based VM when using -display gtk, works fine with vnc or sdl"
+state = "closed"
+created_at = "2025-03-31T22:08:46.797Z"
+closed_at = "2025-04-02T02:33:29.981Z"
+labels = ["GUI", "GUI::GTK", "target: i386"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/2897"
+host-os = "Debian 12 and Ubuntu 22.04 (and probably everything else)"
+host-arch = "x86_64"
+qemu-version = "QEMU emulator version 9.2.91  (But... I did just build 10.0.0-rc1)"
+guest-os = "n/a"
+guest-arch = "n/a"
+description = """When using -display gtk, SeaBIOS hangs nondeterministicly. Changing to -display sdl or -display vnc lets it boot."""
+reproduce = """1. Run `qemu-system-x86_64 -display gtk` and the VM will not complete BIOS POST.
+2. Run `qemu-system-x86_64 -display sdl` and the VM will complete BIOS POST."""
+additional = """This ONLY happens with SeaBIOS. Using a UEFI BIOS to boot the VM does not cause this issue. 
+
+I realise this is a crazy bug. I suspect that the only way it could have slipped through testing is because it *requires* human interaction.
+
+There is no difference with using --accel kvm or not, but I have provided the smallest possible command line to duplicate the issue, which is literally just `qemu-system-x86_64 -display gtk`
+
+#"""