kvm_unit_tests failed with multiple test cases on azure kernel

Bug #1719524 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-azure (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

We have the kvm_unit_test updated in our autotest-client-tests repo recently for the SRU regression-testing, before it gets updated, this test will be skipped for azure kernel (except the "setup.all").

Now we can see it has failed with 11 tests:
ioapic, vmexit_vmcall, access, hypercall, realmode, sieve, syscall, svm, kvmclock_test, pcid, hyperv_clock

Please refer to attachments for the log.

Kernel: 4.11.0-1012.12 - azure

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Marcelo Cerri (mhcerri) wrote :

Do those tests require a KVM enabled kernel to run?

Po-Hsu Lin (cypressyew)
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

According to this bug 1718740 "linux-azure: KVM nested virtualization is disabled", I think it's enabled on azure kernel?

This is the test result for 4.11.0-1012.12 - azure

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

BTW, compare to the previous test result (4.11.0-1009.9).

This test suite was skipped after the setup task[1], it might because that it is not supported.
But we have also updated the repo after that, it's hard to tell if it has anything to do with the repo update, or to the kernel config change.

[1] http://kernel.ubuntu.com/testing/4.11.0-1009.9-azure/azure--ubuntu-kvm-unit-tests--xenial__4.11.0-1009.9__2017-09-12_23-14-00/ubuntu_kvm_unit_tests-test-suite.html

Revision history for this message
Joshua R. Poulson (jrp) wrote :

Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3. I believe this has already been changed for testing, so this bug can probably be closed.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hello Joshua,

Yes we have added an extra kvm-ok check to our kvm-smoke-test test suite to make sure it supports the KVM feature.

Since these failures here were filed against an arbitrary node. I will close this with Invalid and open another that passed the kvm-smoke-test but failed with kvm-unit-test.

Thanks

Changed in linux-azure (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.