770de68535
pci_devfn properties accept both integer and string values, but integer 1 and string '1' have different meanings: The integer value means device 0, function 1 whereas the string value '1' is short for '1.0' and means device 1, function 0. This test wants the string version so that the device actually becomes visible for the guest. device_add hides the problem because it goes through QemuOpts, which turns all properties into strings - this is a QEMU bug that we want to fix, but that cancelled out the bug in this test. Fix the test first so that device_add can be fixed afterwards. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20241122224042.149258-1-kwolf@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com> |
||
|---|---|---|
| .. | ||
| avocado_qemu | ||
| boot_linux.py | ||
| boot_linux_console.py | ||
| boot_xen.py | ||
| hotplug_blk.py | ||
| hotplug_cpu.py | ||
| intel_iommu.py | ||
| kvm_xen_guest.py | ||
| linux_ssh_mips_malta.py | ||
| machine_aspeed.py | ||
| migration.py | ||
| README.rst | ||
| replay_kernel.py | ||
| replay_linux.py | ||
| reverse_debugging.py | ||
| smmu.py | ||
| tuxrun_baselines.py | ||
| vnc.py | ||
============================================= Integration tests using the Avocado Framework ============================================= This directory contains integration tests. They're usually higher level, and may interact with external resources and with various guest operating systems. For more information, please refer to ``docs/devel/testing.rst``, section "Integration tests using the Avocado Framework".