Hi Philippe, thanks for replying.
The 'kernel_irqchip' parameter is a bit confusing to me. It looks like
the documentation was updated from it defaulted to 'off' as a -machine
parameter, to now it will default to 'on' as an -accel parameter.
This bug described how the value for 'default_kernel_ir
Public bug reported:
Hello,
I am not sure if this qualifies as a "bug"; it is be more of an unknown
issue with default settings. However, since the default value of q35
default_kernel_irqchip_split was changed seemingly due to similar user
feedback, I thought this was important to share..
AMD Na
I tested this again on the latest Qemu and Linux kernel and cannot
reproduce it anymore, so this can be closed now..
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1792523
Title:
usb passthrough not
The usb-host devices have the problem.
It does not seem to matter if 1 or all 3 are specified.. I had thought
maybe only one of them was causing the issue.. but all of them are
affected if '-daemonize' is specified at startup.
Correct, the vfio-pci device 1:00.x is an Nvidia GPU+audio, and 4:00.0
Public bug reported:
Below is the full Qemu command used to launch the VM. Have been using
this same setup since Qemu 2.12, plus a couple of cherry picked patch
commits fixing ide-hd and e1000e in Windows guests. Both sets of patches
have now been merged to 3.0, so decided to update to 3.0.
The V
Hello, I can also confirm that if you have a series of NVMe devices, at
first when just the OVMF boot menu has loaded, using qemu with a
-monitor and typing 'info pci', it appears that all are given valid bus
addresses.
However, once the Windows 10 x64 installer iso loads, it seems that
every othe
