It's not easy to distinguish successful unit-test from failed QEMU, so we check for presence of the needed feature before hand. x86/hyperv_synic is "skip" instead of "PASS", without KVM/QEMU support. Signed-off-by: Radim Krčmář <rkrcmar@xxxxxxxxxx> --- Probably not the nicest solution around ... "dry_run_qemu_and_skip_if_it_fails=true" parameter in unittest.cfg might be better. x86/unittests.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/x86/unittests.cfg b/x86/unittests.cfg index 6b94ad93dcf0..32fc5f7037e1 100644 --- a/x86/unittests.cfg +++ b/x86/unittests.cfg @@ -182,3 +182,4 @@ arch = x86_64 file = hyperv_synic.flat smp = 2 extra_params = -cpu kvm64,hv_synic -device hyperv-testdev +check = echo quit | $qemu -enable-kvm -cpu kvm64,hv_synic -device hyperv-testdev -monitor stdio > /dev/null -- 2.6.4 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
