summary refs log tree commit diff stats
path: root/gitlab/issues/target_i386/host_missing/accel_missing/752.toml
blob: d60b4db7ca457b52d44d6407e5dc3927a41a37bf (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
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"