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
Revision history for this message
Mehmet Basaran (mehmetbasaran) wrote (last edit ):
Download full text (5.6 KiB)

Found with bionic/linux-oracle-5.4 5.4.0-1129.138~18.04.1 on BM.Optimized3.36 (x86_64) cycle=2024.07.08

16:48:51 INFO | START ubuntu_kvm_unit_tests.vmx_cr_load_test ubuntu_kvm_unit_tests.vmx_cr_load_test timestamp=1722703731 timeout=1800 localtime=Aug 03 16:48:51
16:48:51 DEBUG| Persistent state client._record_indent now set to 2
16:48:51 DEBUG| Persistent state client.unexpected_reboot now set to ('ubuntu_kvm_unit_tests.vmx_cr_load_test', 'ubuntu_kvm_unit_tests.vmx_cr_load_test')
16:48:51 DEBUG| Waiting for pid 30335 for 1800 seconds
16:48:51 DEBUG| Running 'kvm-ok'
16:48:51 DEBUG| [stdout] INFO: /dev/kvm exists
16:48:51 DEBUG| [stdout] KVM acceleration can be used
16:48:51 DEBUG| Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_cr_load_test'
16:48:51 DEBUG| [stdout] BUILD_HEAD=b04954c9
16:48:52 DEBUG| [stdout] timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Q1lQmAAWMi -smp 1 -cpu max,+vmx -append vmx_cr_load_test # -initrd /tmp/tmp.VQhH0gePjE
16:48:52 DEBUG| [stdout] enabling apic
16:48:52 DEBUG| [stdout] smp: waiting for 0 APs
16:48:52 DEBUG| [stdout] paging enabled
16:48:52 DEBUG| [stdout] cr0 = 80010011
16:48:52 DEBUG| [stdout] cr3 = 1007000
16:48:52 DEBUG| [stdout] cr4 = 20
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmx_feature_control
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmxon
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmptrld
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmclear
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmptrst
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmwrite_vmread
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmcs_high
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmcs_lifecycle
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmx_caps
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmread_flags_touch
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = test_vmwrite_flags_touch
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = null
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = vmenter
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = preemption timer
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = control field PAT
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = control field EFER
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = CR shadowing
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = I/O bitmap
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = instruction intercept
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = EPT A/D disabled
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = EPT A/D enabled
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = PML
16:48:52 DEBUG| [stdout] filter = vmx_cr_load_test, test = interrupt
16:48:52 DEBUG| [stdout] filter = vmx_cr_lo...

Read more...

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.