Fix has been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=c87759ce876a7a0b17c2b
** Changed in: qemu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
Just to provide an update, patches are posted to revert this change in
both the q35 4.1 machine type for the next release as well as introduce
a q35 4.0.1 machine type making the same change for 4.0-stable.
References:
https://patchwork.ozlabs.org/patch/1099695/
https://patchwork.ozlabs.org/patch/
> 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 that
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 that
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
QEM
Not just NVIDIA, forcing a NIC to use INTx also fails and it's apparent
from the host that the device is stuck with DisINTx+. Looks like the
resampling mechanism that allows KVM to unmask the interrupt is broken
with split irqchip.
--
You received this bug notification because you are a member o
This seems related to INTx (legacy) interrupt mode, which NVIDIA GeForce
will use by default. Using regedit in a Windows VM or adjusting
nvidia.ko module parameters of a Linux VM can enable the driver to use
MSI, which seems unaffected. We also have the vfio-pci device option x
-no-kvm-intx=on, w
> 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:
Regressi
Does adding "kernel_irqchip=on" to the comma separated list of options
for -machine resolve it?
--
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:
Regression: QEMU 4.0 hangs the host (*bi
