diff options
| author | Thomas Huth <thuth@redhat.com> | 2022-08-01 13:17:46 +0200 |
|---|---|---|
| committer | Thomas Huth <thuth@redhat.com> | 2022-08-01 16:30:18 +0200 |
| commit | 1bca64a3f0490861c03ceb849821ebf42c926f82 (patch) | |
| tree | ef853e9f80a9b4cdb3f101466a24c8b89b371817 /tests/tcg | |
| parent | a07d9df0fd9d449c0271e2fe358e472bc7efefc2 (diff) | |
| download | qemu-1bca64a3f0490861c03ceb849821ebf42c926f82.zip qemu-1bca64a3f0490861c03ceb849821ebf42c926f82.tar.gz qemu-1bca64a3f0490861c03ceb849821ebf42c926f82.tar.bz2 | |
tests/qtest/migration-test: Run the dirty ring tests only with the x86 target
kvm_dirty_ring_supported() only checks whether the dirty ring support
is available on the x86 host, but it ignores whether the target QEMU
architecture is x86 or not. Thus the test_vcpu_dirty_limit() test
currently fails with the assert((strcmp(arch, "x86_64") == 0)) statement
in dirtylimit_start_vm() if the users run e.g. "make check-qtest-aarch64"
on their x86 host. Fix it by only executing the tests when we're running
with a x86_64 target QEMU binary with KVM.
Message-Id: <20220801114644.208197-1-thuth@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'tests/tcg')
0 files changed, 0 insertions, 0 deletions