On 5/11/26 19:59, Pierrick Bouvier wrote:
On 5/11/2026 10:48 AM, Philippe Mathieu-Daudé wrote:
On 11/5/26 17:48, Cédric Le Goater wrote:
Hello,
On 5/6/26 15:55, Philippe Mathieu-Daudé wrote:
Introduce a source set common to system / user. Start it
with the files built in both sets: 'cpu_models_user.c'
and 'gdbstub.c' No logical change intended.
Signed-off-by: Philippe Mathieu-Daudé <[email protected]>
Reviewed-by: Ilya Leoshkevich <[email protected]>
Message-Id: <[email protected]>
This change introduced a regression with PCI passthrough which
stopped working. Guest kernel reports :
[ 0.156501] zpci: PCI is not supported because CPU facilities 69
or 71 are not available
and other devices (ap, ccw) are impacted too I think.
Is it something we could test with the mainstream CI, or does this
requires specific hardware?
It could be tested with a tcg arm vm + nested VM with PCI passthrough.
Yes, adding VFIO tests to the QEMU upstream CI would be great.
However, the problem is that you need to cross-compile QEMU in CI to
test current version to launch the nested VM.
Intel comes to mind first :)
Couldn't we install the QEMU CI build artifacts into a VM matching
the configuration in which they were built ? I assume the artifacts
remain available for some time.
We could then install them in an L1 VM with a predefined emulated
igb device and assigned that device to an L2 VM.
I think this would also benefit the QEMU CI in other ways, as
nested setups allow tests to run with higher privileges.
This would imply to have a "standard" target environment (like debian
with X,Y,Z deps preinstalled) which CI does not have at the moment.
Why one "standard" target ? All arch are impacted, as well as various
distro flavors.
So in practice, it's hard to test it.
It is.
Thanks,
C.
