Re: [PATCH 0/6] target/arm: Fix functional test failures in KVM-only builds

2026-05-07 Thread Pierrick Bouvier
On 5/7/2026 12:47 PM, Peter Maydell wrote:
> If you build QEMU with --disable-tcg on an AArch64 system, some of the
> "make check-functional" tests fail. This patchset fixes them.
> 
> The first patch fixes a bug in QEMU proper, where we broke the
> "x-remote" machine because we forgot to mark it up as being
> OK to expose in the qemu-system-arm and qemu-system-aarch64
> binaries, the way we do for "none" and for all the actual Arm
> machine types.
> 
> The rest are tweaks to the tests:
>  * tests that run '-machine virt,virtualization=on' need to
>check for failure because the machine reports that the hypervisor
>can't support nested virt
>  * tests that use a specific CPU type need to either be
>restricted to TCG-only, or else changed to use 'max' instead
>(since that's the only CPU that will work on both TCG and KVM)
> 
> thanks
> -- PMM
> 
> Peter Maydell (6):
>   hw/remote/machine.c: Mark x-remote machine as OK for AArch64 and
> AArch32
>   tests/functional/test_virt_vbsa: Skip UEFI test if virtualization not
> supported
>   tests/functional/test_kvm.py: Use -cpu max, not cortex-a72
>   tests/functional/test_kvm.py: Skip if virtualization not supported
>   tests/functional/test_hotplug_pci.py: Require TCG
>   tests/functional/test_tuxrun: Restrict to TCG
> 
>  hw/remote/machine.c  |  3 +++
>  tests/functional/aarch64/test_hotplug_pci.py |  1 +
>  tests/functional/aarch64/test_kvm.py | 12 ++--
>  tests/functional/aarch64/test_tuxrun.py  |  2 ++
>  tests/functional/aarch64/test_virt_vbsa.py   | 10 +-
>  5 files changed, 25 insertions(+), 3 deletions(-)
> 

For series:
Reviewed-by: Pierrick Bouvier 




[PATCH 0/6] target/arm: Fix functional test failures in KVM-only builds

2026-05-07 Thread Peter Maydell
If you build QEMU with --disable-tcg on an AArch64 system, some of the
"make check-functional" tests fail. This patchset fixes them.

The first patch fixes a bug in QEMU proper, where we broke the
"x-remote" machine because we forgot to mark it up as being
OK to expose in the qemu-system-arm and qemu-system-aarch64
binaries, the way we do for "none" and for all the actual Arm
machine types.

The rest are tweaks to the tests:
 * tests that run '-machine virt,virtualization=on' need to
   check for failure because the machine reports that the hypervisor
   can't support nested virt
 * tests that use a specific CPU type need to either be
   restricted to TCG-only, or else changed to use 'max' instead
   (since that's the only CPU that will work on both TCG and KVM)

thanks
-- PMM

Peter Maydell (6):
  hw/remote/machine.c: Mark x-remote machine as OK for AArch64 and
AArch32
  tests/functional/test_virt_vbsa: Skip UEFI test if virtualization not
supported
  tests/functional/test_kvm.py: Use -cpu max, not cortex-a72
  tests/functional/test_kvm.py: Skip if virtualization not supported
  tests/functional/test_hotplug_pci.py: Require TCG
  tests/functional/test_tuxrun: Restrict to TCG

 hw/remote/machine.c  |  3 +++
 tests/functional/aarch64/test_hotplug_pci.py |  1 +
 tests/functional/aarch64/test_kvm.py | 12 ++--
 tests/functional/aarch64/test_tuxrun.py  |  2 ++
 tests/functional/aarch64/test_virt_vbsa.py   | 10 +-
 5 files changed, 25 insertions(+), 3 deletions(-)

-- 
2.43.0