Make the painfully slow VPID-focused nested VMX access tests manual-only, as they add marginal value (have never found a bug that wasn't found by the base access test or non-VPID vmx_pf_exception_test), and are all but guarantee to timeout when run in a VM despite their 240s limit. Signed-off-by: Sean Christopherson <seanjc@xxxxxxxxxx> --- x86/unittests.cfg | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/x86/unittests.cfg b/x86/unittests.cfg index e325667b..c878363e 100644 --- a/x86/unittests.cfg +++ b/x86/unittests.cfg @@ -413,21 +413,21 @@ groups = vmx nested_exception file = vmx.flat extra_params = -cpu max,+vmx -append "vmx_pf_vpid_test" arch = x86_64 -groups = vmx nested_exception +groups = vmx nested_exception nodefault timeout = 240 [vmx_pf_invvpid_test] file = vmx.flat extra_params = -cpu max,+vmx -append "vmx_pf_invvpid_test" arch = x86_64 -groups = vmx nested_exception +groups = vmx nested_exception nodefault timeout = 240 [vmx_pf_no_vpid_test] file = vmx.flat extra_params = -cpu max,+vmx -append "vmx_pf_no_vpid_test" arch = x86_64 -groups = vmx nested_exception +groups = vmx nested_exception nodefault timeout = 240 [vmx_pf_exception_test_reduced_maxphyaddr] -- 2.40.0.348.gf938b09366-goog
