vmx tests fail in kvm_unit_tests

Bug #1821394 reported by Sean Feole on 2019-03-22
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Unassigned
linux-aws (Ubuntu)
Undecided
Unassigned
linux-azure (Ubuntu)
Undecided
Unassigned
linux-kvm (Ubuntu)
Undecided
Unassigned
linux-oracle (Ubuntu)
Undecided
Unassigned

Bug Description

Reproducible: Yes, every time.
Series: cosmic
Kernel: "linux-aws 4.18.0-1012.14"
Steps:

1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib
2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
3.) cd kvm-unit-tests; ./configure; make
4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test"

PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
INFO: Processor supports accessed and dirty flag
PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 8192: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 16384: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 32768: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 65536: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 131072: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 262144: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 524288: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 1048576: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 2097152: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 4194304: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 8388608: vmlaunch fails
PASS: Enable-EPT disabled, unrestricted-guest disabled: vmlaunch succeeds
FAIL: Enable-EPT disabled, unrestricted-guest enabled: vmlaunch fails
PASS: Enable-EPT enabled, unrestricted-guest enabled: vmlaunch succeeds
PASS: Enable-EPT enabled, unrestricted-guest disabled: vmlaunch succeeds
PASS: enable-VMX-preemption-timer enabled, save-VMX-preemption-timer disabled: vmlaunch succeeds
PASS: enable-VMX-preemption-timer enabled, save-VMX-preemption-timer enabled: vmlaunch succeeds
FAIL: enable-VMX-preemption-timer disabled, save-VMX-preemption-timer enabled: vmlaunch fails
PASS: enable-VMX-preemption-timer disabled, save-VMX-preemption-timer disabled: vmlaunch succeeds
PASS: VM-exit MSR-store addr [4:0] 1: vmlaunch fails
PASS: VM-exit MSR-store addr [4:0] 1: VMX inst error is 7 (actual 7)
PASS: VM-exit MSR-store addr [4:0] 2: vmlaunch fails
PASS: VM-exit MSR-store addr [4:0] 2: VMX inst error is 7 (actual 7)
PASS: VM-exit MSR-store addr [4:0] 4: vmlaunch fails
PASS: VM-exit MSR-store addr [4:0] 4: VMX inst error is 7 (actual 7)
PASS: VM-exit MSR-store addr [4:0] 8: vmlaunch fails
PASS: VM-exit MSR-store addr [4:0] 8: VMX inst error is 7 (actual 7)
KVM: entry failed, hardware error 0x7
EAX=00000000 EBX=00000000 ECX=00000000 EDX=000406f1
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
EIP=0000fff0 EFL=00000000 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0000 00000000 0000ffff 00009300
CS =0000 00000000 00000000 00008000
SS =0000 00000000 0000ffff 00009300
DS =0000 00000000 0000ffff 00009300
FS =0000 00000000 0000ffff 00009300
GS =0000 00000000 0000ffff 00009300
LDT=0000 00000000 0000ffff 00008200
TR =0000 00000000 0000ffff 00008b00
GDT= 00000000 0000ffff
IDT= 00000000 0000ffff
CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

------------------------------------------

Test: ubuntu-kvm-unit-tests
Series: Disco
Kernel: 5.0.0-38.41-generic

The following is observed and reproducible in kvm_unit_tests, KVM subtest.

12/12 18:24:56 DEBUG| utils:0153| [stdout] PASS: HOST_CR3 8000000000477000: vmlaunch fails
12/12 18:24:56 DEBUG| utils:0153| [stdout] PASS: HOST_CR3 8000000000477000: VMX inst error is 8 (actual 8)
12/12 18:24:56 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x80000021
12/12 18:24:56 DEBUG| utils:0153| [stderr]
12/12 18:24:56 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode
12/12 18:24:56 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid
12/12 18:24:56 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode
12/12 18:24:56 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors.
12/12 18:24:56 DEBUG| utils:0153| [stderr]
12/12 18:24:56 DEBUG| utils:0153| [stderr] RAX=0000000000006c14 RBX=0000000000006c10 RCX=000000000046e290 RDX=0000000000006c16
12/12 18:24:56 DEBUG| utils:0153| [stderr] RSI=0000000000000000 RDI=0000000000000008 RBP=000000000046e3a0 RSP=000000000046e378
12/12 18:24:56 DEBUG| utils:0153| [stderr] R8 =0000000000000000 R9 =0000000000000020 R10=000000000000000d R11=0000000000000010
12/12 18:24:56 DEBUG| utils:0153| [stderr] R12=0000000000000000 R13=0000000000000008 R14=0000000000000001 R15=0000000000415078
12/12 18:24:56 DEBUG| utils:0153| [stderr] RIP=0000000000404693 RFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
12/12 18:24:56 DEBUG| utils:0153| [stderr] ES =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
12/12 18:24:56 DEBUG| utils:0153| [stderr] CS =0008 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
12/12 18:24:56 DEBUG| utils:0153| [stderr] SS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
12/12 18:24:56 DEBUG| utils:0153| [stderr] DS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
12/12 18:24:56 DEBUG| utils:0153| [stderr] FS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
12/12 18:24:56 DEBUG| utils:0153| [stderr] GS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
12/12 18:24:56 DEBUG| utils:0153| [stderr] LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT
12/12 18:24:56 DEBUG| utils:0153| [stderr] TR =0080 000000008b41d48a 00000067 00008b00 DPL=0 TSS64-busy
12/12 18:24:56 DEBUG| utils:0153| [stderr] GDT= 000000000041d00a 0000ffff
12/12 18:24:56 DEBUG| utils:0153| [stderr] IDT= 0000000000000000 0000ffff
12/12 18:24:56 DEBUG| utils:0153| [stderr] CR0=80010031 CR2=ffffffffffffe000 CR3=0000000000477000 CR4=00002020
12/12 18:24:56 DEBUG| utils:0153| [stderr] DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
12/12 18:24:56 DEBUG| utils:0153| [stderr] DR6=00000000ffff0ff0 DR7=0000000000000400
12/12 18:24:56 DEBUG| utils:0153| [stderr] EFER=0000000000000d00
12/12 18:24:56 DEBUG| utils:0153| [stderr] Code=00 0f 79 d0 0f 96 c0 b8 14 6c 00 00 0f 79 c4 0f 01 c2 eb 52 <55> 48 89 e5 b8 02 44 00 00 0f 78 c0 05 df ff ff 7f 83 f8 01 77 0c e8 4a cf 00 00 b8 01 00
12/12 18:26:20 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 22853 (timeout)
12/12 18:26:21 DEBUG| utils:0153| [stdout] FAIL vmx (timeout; duration=90s)
12/12 18:26:21 ERROR| test:0414| Exception escaping from test:

Sean Feole (sfeole) on 2019-03-22
tags: added: aws i3.metal
Sean Feole (sfeole) wrote :

Also affects Bionic linux-aws 4.15.1035.37

tags: added: 4.15 4.18 bionic cosmic
Sean Feole (sfeole) wrote :

Also affects Xenial linux-aws 4.4.0-1078.88

tags: added: 4.4 xenial
Po-Hsu Lin (cypressyew) on 2019-03-27
no longer affects: linux (Ubuntu)
Sean Feole (sfeole) on 2019-03-28
summary: - vmx tests fail in kvm_unit_tests on aws i3.metal
+ vmx tests fail in kvm_unit_tests

The vmx tests have been failing for me as well. There were some bugs that required me to revert some patches or apply some others, that ended up being fixed on kvm_unit_tests master regarding EPT. The disco branch of our own repo of kvm_unit_tests should work fine with our 5.0 kernel, but we still need to see that running on our test systems. So far, I only tested on a very old Intel Core 2 Duo processor.

One of the other vmx test (vmx_controls_test) has been failing on said processor, and has been disabled on that same branch. That is the more complete part of that test, so at least we should not see that much failures from that one on our systems, until I get to enable it again, after some investigation.

Po-Hsu Lin (cypressyew) wrote :

Found on X KVM as well.

Sean Feole (sfeole) wrote :

affects 4.18.0-1013.15 linux-aws

Sean Feole (sfeole) wrote :

I have seen this fail in Disco on linux-aws but only on i3.metal.

TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test -vmx_controls_test"
04/30 02:54:41 DEBUG| utils:0153| [stdout] FAIL vmx (timeout; duration=90s)

tags: added: disco
Sean Feole (sfeole) wrote :

also affecting linux-azure Disco, 5.0.0-1005.5
Instances: Standard_D16s_v3 , Standard_D2_v3 , Standard_D2s_v3, Standard_E2s_v3, Standard_F2s_v2, Standard_F32s_v2

Sean Feole (sfeole) wrote :

affects 5.0.0-1007.7-aws

Changed in ubuntu-kernel-tests:
status: New → Confirmed
Changed in linux-aws (Ubuntu):
status: New → Confirmed
Sean Feole (sfeole) wrote :

affects , linux-aws-4.18.0 amd64, i3.metal

Sean Feole (sfeole) wrote :

affects , linux-azure 5.0.0-1007.7

tags: added: 5.0.0
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-azure (Ubuntu):
status: New → Confirmed
Changed in linux-kvm (Ubuntu):
status: New → Confirmed
Po-Hsu Lin (cypressyew) on 2019-06-17
tags: added: 5.0 ubuntu-kvm-unit-tests
removed: 5.0.0
Po-Hsu Lin (cypressyew) on 2019-06-24
tags: added: linux-kvm sru-20190603
Sean Feole (sfeole) on 2019-07-22
tags: added: sru-20190701
tags: added: azure
Sean Feole (sfeole) wrote :

latest results from sru-20190812 differ a bit, but still crash linux-azure , disco

8/21 14:39:49 DEBUG| utils:0153| [stdout] Test suite: instruction intercept
08/21 14:39:49 DEBUG| utils:0153| [stdout] PASS: execute HLT
08/21 14:39:49 DEBUG| utils:0153| [stdout] PASS: intercept HLT
08/21 14:39:49 DEBUG| utils:0153| [stdout] PASS: execute INVLPG
08/21 14:39:49 DEBUG| utils:0153| [stdout] PASS: intercept INVLPG
08/21 14:39:49 DEBUG| utils:0153| [stdout] PASS: execute MWAIT
08/21 14:39:49 DEBUG| utils:0153| [stdout] PASS: intercept MWAIT
08/21 14:39:49 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP at ip 0000000000403a95
08/21 14:39:49 DEBUG| utils:0153| [stdout] error_code=0000 rflags=00010046 cs=00000008
08/21 14:39:49 DEBUG| utils:0153| [stdout] rax=0000000000403a93 rcx=0000000000000000 rdx=0000000000000090 rbx=0000000000475c80
08/21 14:39:49 DEBUG| utils:0153| [stdout] rbp=000000000047efdf rsi=0000000000000000 rdi=0000000000000006
08/21 14:39:49 DEBUG| utils:0153| [stdout] r8=00000000000003fd r9=00000000000003f8 r10=000000000000000d r11=0000000000000000
08/21 14:39:49 DEBUG| utils:0153| [stdout] r12=0000000000423c62 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000
08/21 14:39:49 DEBUG| utils:0153| [stdout] cr0=0000000080010031 cr2=0000000000000000 cr3=0000000000477000 cr4=0000000000002020
08/21 14:39:49 DEBUG| utils:0153| [stdout] cr8=0000000000000000
08/21 14:39:49 DEBUG| utils:0153| [stdout] STACK: @403a95 4016d0 4004dd
08/21 14:39:49 DEBUG| utils:0153| [stdout] FAIL vmx

tags: added: sru-20190812
Sean Feole (sfeole) wrote :
Download full text (23.8 KiB)

Oracle is also affected by this. VM.Dense and VM.Standard instance types

09/20 05:24:53 DEBUG| utils:0153| [stdout] Test suite: vmx_host_state_area_test
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 80000021: vmlaunch succeeds
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 80010030: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 80010030: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 80010011: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 80010011: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 10031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 10031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 180010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 180010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 280010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 280010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 480010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 480010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 880010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 880010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 1080010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 1080010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 2080010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 2080010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 4080010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 4080010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 8080010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 8080010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 10080010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 10080010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 20080010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 20080010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 40080010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 40080010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 80080010031: vmlaunch fails
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_CR0 80080010031: VMX inst error is 8 (actual 8)
09/20 05:24:53 DEBUG| utils:0153| [stdout] PASS: HOST_...

Sean Feole (sfeole) wrote :

linux-oracle / disco / 5.0.0-1003.4

tags: added: sru-20190902
tags: added: oracle
Sean Feole (sfeole) wrote :

Failing on the 5.3 kernel Eoan / Azure

10/25 17:59:05 DEBUG| utils:0153| [stdout] Test suite: instruction intercept
10/25 17:59:05 DEBUG| utils:0153| [stdout] PASS: execute HLT
10/25 17:59:05 DEBUG| utils:0153| [stdout] PASS: intercept HLT
10/25 17:59:05 DEBUG| utils:0153| [stdout] PASS: execute INVLPG
10/25 17:59:05 DEBUG| utils:0153| [stdout] PASS: intercept INVLPG
10/25 17:59:05 DEBUG| utils:0153| [stdout] PASS: execute MWAIT
10/25 17:59:05 DEBUG| utils:0153| [stdout] PASS: intercept MWAIT
10/25 17:59:05 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP at ip 0000000000403b55
10/25 17:59:05 DEBUG| utils:0153| [stdout] error_code=0000 rflags=00010046 cs=00000008
10/25 17:59:05 DEBUG| utils:0153| [stdout] rax=0000000000403b53 rcx=0000000000000000 rdx=0000000000000090 rbx=0000000000475c80
10/25 17:59:05 DEBUG| utils:0153| [stdout] rbp=000000000047efdf rsi=0000000000000000 rdi=0000000000000006
10/25 17:59:05 DEBUG| utils:0153| [stdout] r8=000000000042568d r9=00000000000003f8 r10=000000000000000d r11=0000000000000000
10/25 17:59:05 DEBUG| utils:0153| [stdout] r12=0000000000423c62 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000
10/25 17:59:05 DEBUG| utils:0153| [stdout] cr0=0000000080010031 cr2=0000000000000000 cr3=0000000000477000 cr4=0000000000002020
10/25 17:59:05 DEBUG| utils:0153| [stdout] cr8=0000000000000000
10/25 17:59:05 DEBUG| utils:0153| [stdout] STACK: @403b55 401742 4004dd
10/25 17:59:05 DEBUG| utils:0153| [stdout] FAIL vmx

tags: added: sru-20191021
tags: added: eoan
tags: removed: cosmic
Po-Hsu Lin (cypressyew) on 2019-11-25
tags: added: sru-20191111
tags: added: 5.3
Sean Feole (sfeole) on 2019-12-16
description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-oracle (Ubuntu):
status: New → Confirmed
Sean Feole (sfeole) on 2019-12-16
tags: added: sru-20191202
Sean Feole (sfeole) on 2020-01-23
tags: added: sru-20200106
Sean Feole (sfeole) on 2020-02-03
tags: added: sru-20200127
Po-Hsu Lin (cypressyew) wrote :
Download full text (11.8 KiB)

Time out on T-4.4, with a slightly different error:
 BUILD_HEAD=4671e4ba
 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -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.1jzuZsx4Jy -smp 1 -cpu host,+vmx -append -exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test -vmx_controls_test -vmx_host_state_area_test -vmx_nm_test -vmx_nmi_window_test -vmx_intr_window_test -vmx_pending_event_test # -initrd /tmp/tmp.1FbpAwN033
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 477000
 cr4 = 20
 PASS: test vmxon with FEATURE_CONTROL cleared
 PASS: test vmxon without FEATURE_CONTROL lock
 PASS: test enable VMX in FEATURE_CONTROL
 PASS: test FEATURE_CONTROL lock bit
 PASS: test vmxon with unaligned vmxon region
 PASS: test vmxon with bits set beyond physical address width
 PASS: test vmxon with invalid revision identifier
 PASS: test vmxon with valid vmxon region
 PASS: test vmptrld with unaligned vmcs
 PASS: test vmptrld with vmcs address bits set beyond physical address width
 PASS: test vmptrld with vmxon region
 FAIL: test vmptrld with vmxon region vm-instruction error
 PASS: test vmptrld with valid vmcs region
 PASS: test vmclear with unaligned vmcs
 PASS: test vmclear with vmcs address bits set beyond physical address width
 PASS: test vmclear with vmxon region
 PASS: test vmclear with valid vmcs region
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: test vmclear flush (current VMCS)
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: test vmclear flush (!current VMCS)
 PASS: test vmptrst
 Skipping read-only field 2400
 Skipping volatile field 4400
 Skipping read-only field 4402
 Skipping read-only field 4404
 Skipping read-only field 4406
 Skipping read-only field 4408
 Skipping read-only field 440a
 Skipping read-only field 440c
 Skipping read-only field 440e
 Skipping read-only field 6400
 Skipping read-only field 6402
 Skipping read-only field 6404
 Skipping read-only field 6406
 Skipping read-only field 6408
 Skipping read-only field 640a
 PASS: VMWRITE/VMREAD
 PASS: VMREAD TSC_OFFSET after VMWRITE TSC_OFFSET
 PASS: VMREAD TSC_OFFSET_HI after VMWRITE TSC_OFFSET
 PASS: VMREAD TSC_OFFSET_HI after VMWRITE TSC_OFFSET_HI
 PASS: VMREAD TSC_OFFSET after VMWRITE TSC_OFFSET_HI
 VMCLEAR VMCS...

tags: added: sru-20200316
Po-Hsu Lin (cypressyew) wrote :

Failed on T-4.4 / X-4.4 AMD64
Passed on X-4.15 / B-4.15 AMD64

tags: added: sru-20200921

Failed on Bionic/oracle : 5.4.0-1026.26~18.04.1 : amd64

tags: added: 5.4
Po-Hsu Lin (cypressyew) wrote :

Still visible in Xenial 4.4.0-1118.132 AWS c5.metal

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

Other bug subscribers