diff options
author | Thomas Huth <thuth@redhat.com> | 2025-04-14 13:30:27 +0200 |
---|---|---|
committer | Thomas Huth <thuth@redhat.com> | 2025-04-23 07:51:25 +0200 |
commit | 5c2bae2155b162f7355ca759881c5fdaaf7bc209 (patch) | |
tree | c096ce489e583b267e1a355afa3b4fc210366743 /hw/avr/arduino.c | |
parent | a820caf8444c963faf69228e4a0a0d4673c24ab5 (diff) | |
download | qemu-5c2bae2155b162f7355ca759881c5fdaaf7bc209.zip qemu-5c2bae2155b162f7355ca759881c5fdaaf7bc209.tar.gz qemu-5c2bae2155b162f7355ca759881c5fdaaf7bc209.tar.bz2 |
tests/functional: Convert the SMMU test to the functional framework
This test was using cloudinit and a "dnf install" command in the guest
to exercise the NIC with SMMU enabled. Since we don't have the cloudinit
stuff in the functional framework and we should not rely on having access
to external networks (once our ASSETs have been cached), we rather boot
into the initrd first, manually mount the root disk and then use the
check_http_download() function from the functional framework here instead
for testing whether the network works as expected.
Unfortunately, there seems to be a small race when using the files
from Fedora 33: To enter the initrd shell, we have to send a "return"
once. But it does not seem to work if we send it too early. Using a
sleep(0.2) makes it work reliably for me, but to make it even more
unlikely to trigger this situation, let's better limit the Fedora 33
tests to only run with KVM.
Finally, while we're at it, we also add some lines for testing writes
to the hard disk, as we already do it in the test_intel_iommu test.
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Eric Auger <eric.auger@redhat.com>
Message-ID: <20250414113031.151105-14-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'hw/avr/arduino.c')
0 files changed, 0 insertions, 0 deletions