1 files changed, 23 insertions, 0 deletions

diff --git a/gitlab/issues/target_i386/host_missing/accel_missing/752.toml b/gitlab/issues/target_i386/host_missing/accel_missing/752.toml
new file mode 100644
index 00000000..d60b4db7
--- /dev/null
+++ b/gitlab/issues/target_i386/host_missing/accel_missing/752.toml
@@ -0,0 +1,23 @@
+id = 752
+title = "vmmouse device gets attached twice, one without i8042 associated"
+state = "closed"
+created_at = "2021-11-28T22:53:30.554Z"
+closed_at = "2021-12-20T04:46:00.143Z"
+labels = ["target: i386"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/752"
+host-os = "Fedora 34"
+host-arch = "amd64"
+qemu-version = "6.1.92 (v6.2.0-rc1-96-gdd4b0de459)"
+guest-os = "Windows, MS-DOS"
+guest-arch = "i386"
+description = """I'm developing [a driver for the VMware mouse device](https://github.com/NattyNarwhal/vmwmouse). I know this works properly on VMware, but I'm trying it in QEMU too.
+
+[My full notes](https://github.com/NattyNarwhal/vmwmouse/issues/1), but most relevant is:
+
+* a vmmouse instance gets initialized twice (confirmed in qtree), one with i8042 the first time, one without the second time
+* the second vmmouse instance is the one receiving the events, passing them to the i8042 device's fake event handler
+* obviously, a crash because ISAKBDDevice should never be null"""
+reproduce = """1. Load VMware mouse driver
+2. Move cursor (I recommend waiting until Windows loads before doing so, it is very easy to corrupt the guest filesystem if you do it while Windows is loading)
+3. Crash"""
+additional = "n/a"