Further to this, it appears to be a race condition with reading from the i8042 controller. I have turned on debugging of PS2 and KBD and filtered out the event that causes the issue. I have split the below up to show the valid reads for the mouse and then the sequence that triggers a reset when the keyboard is used.
KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x08 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x00 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x02 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x00 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x18 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0xfe KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x02 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x00 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x08 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x00 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x01 KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x00 KBD: kbd: read status=0x3d KBD: kbd: read status=0x1d <-- the status changed on the 2nd call. KBD: kbd: read status=0x1d KBD: kbd: read data=0x9e KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x18 KBD: kbd: read data=0xff <-- two data reads without checking status KBD: kbd: read status=0x3d <-- guest looking for mouse movements KBD: kbd: read status=0x3d KBD: kbd: read data=0x02 <-- first byte KBD: kbd: read status=0x3d KBD: kbd: read status=0x3d KBD: kbd: read data=0x00 <-- 2nd byte KBD: kbd: read status=0x1c <-- no more data, there should be two more bytes KBD: kbd: read status=0x1c KBD: kbd: read status=0x1c here the host attempts to reset the device KBD: kbd: write cmd=0xd4 <-- write to mouse cmd KBD: kbd: read status=0x1c KBD: kbd: read status=0x1c KBD: kbd: read status=0x1c KBD: kbd: write data=0xff <-- reset mouse kbd: write mouse 0xff -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1722884 Title: keyboard input while mouse moving triggers mouse failure Status in QEMU: New Bug description: When QEMU is getting a ton of mouse input events if keys are pressed on the keyboard the scan code will be corrupted causing erroneous behavior. I have confirmed this problem in the latest version in git (530049bc1dcc24c1178a29d99ca08b6dd08413e0). After the erroneous behavior the operating system issues a keyboard reset which prevents the mouse from functioning until the operating system is restarted. This seems to only occur if the PS2 mouse is being used as the input, the tablet input device doesn't exhibit this behavior. The same problem was reported here also: https://openxt.atlassian.net/browse/OXT-562 Host : Debian 9 CPU : Ryzen 1700X RAM : 16GB Kernel: 4.12.0-0.bpo.2-amd64 Guest : Windows 10 (KVM) RAM : 8GB (1GB Huge pages) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1722884/+subscriptions
