ubuntu-kernel-tests

ubuntu_kvm_unit_tests: vmx_cr_load_test: VM-Fail on vmresume: error number is 8

Bug #1941753 reported by Stefan Bader
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned

Bug Description

On host spitfire running focal:linux (5.4) lowlatency for sru-20210816:

DEBUG| [stdout] Test suite: vmx_cr_load_test
DEBUG| [stdout] VM-Fail on vmresume: error number is 8. See Intel 30.4.
DEBUG| [stdout] FAIL vmx

Might not be limited to the lowlatency flavour as spitfire was not selected for generic. This host is also the only one to show this failure.

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

Interesting, I found this bug https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1936380 you filed last month, before the recent test case change. I think this is something that I need to pull out from vmx again.

I wonder what Intel 30.4 is.

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

Tested with Intel node spitfire and vought, it seems that only spitfire is affected. Pull this test out can make vmx test finish properly. This test case change will be handled in bug 1941830)

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

kvm-unit-tests source tree updated https://kernel.ubuntu.com/git/ubuntu/kvm-unit-tests/commit/?h=hirsute&id=1593e88af6f925f44df5089ebdfb7549e1cba722

Test retriggered on spitfire, will update the bug title later.

Po-Hsu Lin (cypressyew)
summary: - ubuntu_kvm_unit_tests:vmx:vmx_cr_load_test: VM-Fail on vmresume: error
+ ubuntu_kvm_unit_tests: vmx_cr_load_test: VM-Fail on vmresume: error
number is 8
Revision history for this message
Kleber Sacilotto de Souza (kleber-souza) wrote :

Found with focal/linux-hwe 5.4.0-89.100~18.04.1 lowlatency on spitfire.

tags: added: sru-20210927
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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