summary refs log tree commit diff stats
path: root/gitlab/issues_text/target_i386/host_missing/accel_missing/752
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues_text/target_i386/host_missing/accel_missing/752')
-rw-r--r--gitlab/issues_text/target_i386/host_missing/accel_missing/75213
1 files changed, 0 insertions, 13 deletions
diff --git a/gitlab/issues_text/target_i386/host_missing/accel_missing/752 b/gitlab/issues_text/target_i386/host_missing/accel_missing/752
deleted file mode 100644
index a9b99b34d..000000000
--- a/gitlab/issues_text/target_i386/host_missing/accel_missing/752
+++ /dev/null
@@ -1,13 +0,0 @@
-vmmouse device gets attached twice, one without i8042 associated
-Description of problem:
-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
-Steps to 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