This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/144
** Changed in: qemu
Status: New => Expired
** Bug watch
Hi,
Seeing this same thing! And I'm on Ubuntu 20.10, so pretty current :-).
vt82c686b-usb-uhci doesn't seem to be accessible any more, but trying
qemu-xhci => no joy, still have to reset the VM after each startup, to
get the keyboard and mouse working.
Is this expected?
Thanks!
--
You received
Doesn't happen when adding another UHCI controller and explicitly
connecting the keyboard to it, like: -device vt82c686b-usb-uhci,id=myusb
-device usb-host,bus=myusb.0,hostbus=3,hostaddr=2
Is QEMU just incorrectly connecting my full-speed USB keyboard to USB 2.0 EHCI
instead of USB 1.x UHCI?
Or i
Same problem with qemu 2.8 from Ubuntu Cloud Archive.
Is that enough to consider the bug highly likely in latest upstream version
too? I don't have a QEMU build system at hand right now..
** Changed in: qemu
Status: Incomplete => New
--
You received this bug notification because you are
Thanks Thomas, definitely worth to check.
@Colin - if you want a quick and easy short with qemu 2.8 you can try [1].
[1]: https://wiki.ubuntu.com/OpenStack/CloudArchive
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.la
Have you tried whether it works with the latest upstream version of QEMU
(currently version 2.9) - since you've marked this as upstream QEMU
problem, too?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which
