Still an issue as of QEMU 6.0.0rc2.
I can't (still) exclude that it's an issue on the host side, although,
when it comes to USB passthrough, I don't have issues with similar
devices (mice, keyboards etc.).
The module blacklist workaround works.
--
You received this bug notification because you
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714331
Title:
Virtual machines not working anymore on 2.10
Status in QEMU:
Invalid
Bug
> The change in QEMU 4.0 is only a change in defaults of the machine
type, it can be entirely reverted in the VM config with
kernel_irqchip=on or with libvirt. Using a
machine type prior to the q35 4.0 machine type would also avoid it.
There are no performance issues with these configurations
ok, so, if I understand correctly, the workaround is:
- set `x-no-kvm-intx=on` and enable MSI in the guest (via regedit or
module params)
which may lead to a performance regression (at least under certain
circumstances).
Is it therefore preferrable, performance and configuration-wise, to use
> Does adding "kernel_irqchip=on" to the comma separated list of options
for -machine resolve it?
Yes, that solved it, thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1826422
Title:
Public bug reported:
The commit b2fc91db84470a78f8e93f5b5f913c17188792c8 seemingly introduced
a regression on my system.
When I start QEMU, the guest and the host hang (I need a hard reset to
get back to a working system), before anything shows on the guest.
I use QEMU with GPU passthrough
So! These are the options and respective logs; they still don't make the
controller work - it doesn't work at all.
# option 1
-device nec-usb-xhci \
-device usb-tablet \
-device
usb-host,vendorid=0x$VGAPT_XBOX_PAD_VEND_ID,productid=0x$VGAPT_XBOX_PAD_PROD_ID
\
# log
libusb: error
Public bug reported:
I can't properly passthrough my Xbox One controller to a virtual
machine; it causes USB disconnections on the host, ultimately preventing
it to work (at all) on the guest
I've seen a few other cases reported in other websites, which show the
same symptoms:
-
