ubuntu-kernel-tests

vmx_host_state_area failed in ubuntu_kvm_unit_tests on T-aws / X-aws / B-aws-5.0

Bug #1866585 reported by Po-Hsu Lin on 2020-03-09

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubuntu-kernel-tests	Confirmed	Undecided	Unassigned

Bug Description

Issue found on bare-metal node r5.metal, i3.metal, c5.metal

timeout -k 1s --foreground 30 /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.v18DYEVgce -smp 1 -cpu host,+vmx -append vmx_host_state_area_test # -initrd /tmp/tmp.9OvR6iG4dn
enabling apic
paging enabled
cr0 = 80010011
cr3 = 477000
cr4 = 20

Test suite: vmx_host_state_area_test
FAIL: HOST_CR0 80000021: x86/vmx_tests.c:3330: Assertion failed: exit_reason == (VMX_FAIL_STATE | VMX_ENTRY_FAILURE) || exit_reason == (VMX_FAIL_MSR | VMX_ENTRY_FAILURE)
STACK: 40476d 407442 407535 4076eb 401556 4039f1 400312
SUMMARY: 1 tests, 1 unexpected failures
FAIL vmx_host_state_area (1 tests, 1 unexpected failures)

See original description

Po-Hsu Lin (cypressyew) on 2020-03-09

tags:	added: sru-20200217
tags:	added: 4.4 amd64 trusty ubuntu-kvm-unit-tests

Po-Hsu Lin (cypressyew) on 2020-03-09

tags:

added: aws

Po-Hsu Lin (cypressyew) on 2020-03-09

description:

updated

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2020-03-09:

Looks like this is a new test.

tags:

added: kqa-blocker

Revision history for this message

Sean Feole (sfeole) wrote on 2020-03-10:

these failures are to be expected on 4.15 and older kernels. they were split from the large vmx test, this is not a blocker, removing the tag.

We will continue to run these tests on the 4.15 and older kernels, to ensure that the kernel does not crash or panic, etc. There is no plan to stop running them. We just know they will fail

Changed in ubuntu-kernel-tests:
status:	New → Triaged
tags:	removed: kqa-blocker
Changed in ubuntu-kernel-tests:
status:	Triaged → Confirmed

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2020-03-11:

Failed on B-aws-5.0 bare metal nodes as well (5.0.0-1027.30-aws)

tags:	added: 5.0 bionic
summary:	- vmx_host_state_area failed in ubuntu_kvm_unit_tests on T-aws + vmx_host_state_area failed in ubuntu_kvm_unit_tests on T-aws / B-aws-5.0

Po-Hsu Lin (cypressyew) on 2020-03-12

tags:

added: 4.15

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2020-03-19: Re: vmx_host_state_area failed in ubuntu_kvm_unit_tests on T-aws / B-aws-5.0

Download full text (3.9 KiB)

Failed on T-4.4 as well, with slightly different error message:
BUILD_HEAD=4671e4ba
timeout -k 1s --foreground 30 /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.WrAftaGs4I -smp 1 -cpu host,+vmx -append vmx_host_state_area_test # -initrd /tmp/tmp.3XdRJ8sRFg
enabling apic
paging enabled
cr0 = 80010011
cr3 = 477000
cr4 = 20

Test suite: vmx_host_state_area_test
PASS: HOST_CR0 80000021: vmlaunch succeeds
PASS: HOST_CR0 80010030: vmlaunch fails
FAIL: HOST_CR0 80010030: VMX inst error is 8 (actual 4)
PASS: HOST_CR0 80010011: vmlaunch fails
FAIL: HOST_CR0 80010011: VMX inst error is 8 (actual 4)
PASS: HOST_CR0 10031: vmlaunch fails
FAIL: HOST_CR0 10031: VMX inst error is 8 (actual 4)
FAIL: HOST_CR4 2000: vmlaunch succeeds
PASS: HOST_CR4 20: vmlaunch fails
FAIL: HOST_CR4 20: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 10000477000: vmlaunch fails
FAIL: HOST_CR3 10000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 20000477000: vmlaunch fails
FAIL: HOST_CR3 20000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 40000477000: vmlaunch fails
FAIL: HOST_CR3 40000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 80000477000: vmlaunch fails
FAIL: HOST_CR3 80000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 100000477000: vmlaunch fails
FAIL: HOST_CR3 100000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 200000477000: vmlaunch fails
FAIL: HOST_CR3 200000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 400000477000: vmlaunch fails
FAIL: HOST_CR3 400000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 800000477000: vmlaunch fails
FAIL: HOST_CR3 800000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 1000000477000: vmlaunch fails
FAIL: HOST_CR3 1000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 2000000477000: vmlaunch fails
FAIL: HOST_CR3 2000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 4000000477000: vmlaunch fails
FAIL: HOST_CR3 4000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 8000000477000: vmlaunch fails
FAIL: HOST_CR3 8000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 10000000477000: vmlaunch fails
FAIL: HOST_CR3 10000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 20000000477000: vmlaunch fails
FAIL: HOST_CR3 20000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 40000000477000: vmlaunch fails
FAIL: HOST_CR3 40000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 80000000477000: vmlaunch fails
FAIL: HOST_CR3 80000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 100000000477000: vmlaunch fails
FAIL: HOST_CR3 100000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 200000000477000: vmlaunch fails
FAIL: HOST_CR3 200000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 400000000477000: vmlaunch fails
FAIL: HOST_CR3 400000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 800000000477000: vmlaunch fails
FAIL: HOST_CR3 800000000477000: VMX inst error is 8 (actual 4)
PASS: HOST_CR3 1000000000477000: vmlaunch fails
FAIL: HOST_CR3 1000000000...

Failed on T-4.4 as well, with slightly different error message:
 BUILD_HEAD=4671e4ba
 timeout -k 1s --foreground 30 /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.WrAftaGs4I -smp 1 -cpu host,+vmx -append vmx_host_state_area_test # -initrd /tmp/tmp.3XdRJ8sRFg
 enabling apic
 paging enabled
 cr0 = 80010011
 cr3 = 477000
 cr4 = 20

Test suite: vmx_host_state_area_test
 PASS: HOST_CR0 80000021: vmlaunch succeeds
 PASS: HOST_CR0 80010030: vmlaunch fails
 FAIL: HOST_CR0 80010030: VMX inst error is 8 (actual 4)
 PASS: HOST_CR0 80010011: vmlaunch fails
 FAIL: HOST_CR0 80010011: VMX inst error is 8 (actual 4)
 PASS: HOST_CR0 10031: vmlaunch fails
 FAIL: HOST_CR0 10031: VMX inst error is 8 (actual 4)
 FAIL: HOST_CR4 2000: vmlaunch succeeds
 PASS: HOST_CR4 20: vmlaunch fails
 FAIL: HOST_CR4 20: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 10000477000: vmlaunch fails
 FAIL: HOST_CR3 10000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 20000477000: vmlaunch fails
 FAIL: HOST_CR3 20000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 40000477000: vmlaunch fails
 FAIL: HOST_CR3 40000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 80000477000: vmlaunch fails
 FAIL: HOST_CR3 80000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 100000477000: vmlaunch fails
 FAIL: HOST_CR3 100000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 200000477000: vmlaunch fails
 FAIL: HOST_CR3 200000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 400000477000: vmlaunch fails
 FAIL: HOST_CR3 400000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 800000477000: vmlaunch fails
 FAIL: HOST_CR3 800000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 1000000477000: vmlaunch fails
 FAIL: HOST_CR3 1000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 2000000477000: vmlaunch fails
 FAIL: HOST_CR3 2000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 4000000477000: vmlaunch fails
 FAIL: HOST_CR3 4000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 8000000477000: vmlaunch fails
 FAIL: HOST_CR3 8000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 10000000477000: vmlaunch fails
 FAIL: HOST_CR3 10000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 20000000477000: vmlaunch fails
 FAIL: HOST_CR3 20000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 40000000477000: vmlaunch fails
 FAIL: HOST_CR3 40000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 80000000477000: vmlaunch fails
 FAIL: HOST_CR3 80000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 100000000477000: vmlaunch fails
 FAIL: HOST_CR3 100000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 200000000477000: vmlaunch fails
 FAIL: HOST_CR3 200000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 400000000477000: vmlaunch fails
 FAIL: HOST_CR3 400000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 800000000477000: vmlaunch fails
 FAIL: HOST_CR3 800000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 1000000000477000: vmlaunch fails
 FAIL: HOST_CR3 1000000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 2000000000477000: vmlaunch fails
 FAIL: HOST_CR3 2000000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 4000000000477000: vmlaunch fails
 FAIL: HOST_CR3 4000000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_CR3 8000000000477000: vmlaunch fails
 FAIL: HOST_CR3 8000000000477000: VMX inst error is 8 (actual 4)
 PASS: HOST_SYSENTER_ESP non-canonical: vmlaunch fails
 FAIL: HOST_SYSENTER_ESP non-canonical: VMX inst error is 8 (actual 4)
 FAIL: HOST_SYSENTER_ESP canonical: vmlaunch succeeds
 PASS: HOST_SYSENTER_EIP non-canonical: vmlaunch fails
 FAIL: HOST_SYSENTER_EIP non-canonical: VMX inst error is 8 (actual 4)
 FAIL: HOST_SYSENTER_EIP canonical: vmlaunch succeeds
 SUMMARY: 65 tests, 33 unexpected failures
 FAIL vmx_host_state_area (65 tests, 33 unexpected failures)

tags:

added: sru-20200316

Po-Hsu Lin (cypressyew) on 2020-05-21

tags:

added: sru-20200518

Kelsey Steele (kelsey-steele) on 2020-10-02

tags:

added: sru-20200921

Kelsey Steele (kelsey-steele) on 2020-10-09

tags:

added: azure

Revision history for this message

Kelsey Steele (kelsey-steele) wrote on 2020-10-09:

failed on Bionic/azure-4.15 : 4.15.0-1097.107 : amd64

[stdout] FAIL vmx_host_state_area (timeout; duration=30)

Revision history for this message

Kelsey Steele (kelsey-steele) wrote on 2020-10-09:

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

09/24 08:16:06 DEBUG| utils:0153| [stdout] FAIL: HOST_CR4 2000: vmlaunch succeeds

...

232. 09/24 08:16:07 DEBUG| utils:0153| [stdout] FAIL: HOST_SYSENTER_ESP canonical: vmlaunch succeeds
233. 09/24 08:16:07 DEBUG| utils:0153| [stdout] PASS: HOST_SYSENTER_EIP non-canonical: vmlaunch fails
234. 09/24 08:16:07 DEBUG| utils:0153| [stdout] PASS: HOST_SYSENTER_EIP non-canonical: VMX inst error is 8 (actual 8)
235. 09/24 08:16:07 DEBUG| utils:0153| [stdout] FAIL: HOST_SYSENTER_EIP canonical: vmlaunch succeeds
236. 09/24 08:16:08 DEBUG| utils:0153| [stdout] SUMMARY: 223 tests, 3 unexpected failures
237. 09/24 08:16:08 DEBUG| utils:0153| [stdout] FAIL vmx_host_state_area (223 tests, 3 unexpected failures)

tags:

added: 5.4 oracle

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2020-11-17:

Still visible in Xenial 4.4.0-1118.132 AWS c5.metal

tags:	added: sru-20201109
summary:	- vmx_host_state_area failed in ubuntu_kvm_unit_tests on T-aws / B-aws-5.0 + vmx_host_state_area failed in ubuntu_kvm_unit_tests on T-aws / X-aws / + B-aws-5.0

Kelsey Steele (kelsey-steele) on 2020-12-18

tags:

added: sru-20201130 xenial

Revision history for this message

Francis Ginther (fginther) wrote on 2021-02-16:

linux-oracle 4.15.0-1065.73

tags:

added: sru-20210125

Revision history for this message

Kleber Sacilotto de Souza (kleber-souza) wrote on 2021-04-12:

Download full text (3.3 KiB)

Failed with timeout on xenial/linux-oracle: 4.15.0-1069.77~16.04.1 for sru-20210315

229. 04/06 21:46:56 DEBUG| utils:0153| [stdout] PASS: HOST_CR3 8000000000477000: VMX inst error is 8 (actual 8)
230. 04/06 21:46:59 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x80000021
231. 04/06 21:46:59 DEBUG| utils:0153| [stderr]
232. 04/06 21:46:59 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode
233. 04/06 21:46:59 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid
234. 04/06 21:46:59 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode
235. 04/06 21:46:59 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors.
236. 04/06 21:46:59 DEBUG| utils:0153| [stderr]
237. 04/06 21:46:59 DEBUG| utils:0153| [stderr] RAX=0000000000006c14 RBX=0000000000000000 RCX=000000000046e680 RDX=0000000000006c16
238. 04/06 21:46:59 DEBUG| utils:0153| [stderr] RSI=0000000000000000 RDI=0000000000000008 RBP=000000000046e790 RSP=000000000046e768
239. 04/06 21:46:59 DEBUG| utils:0153| [stderr] R8 =0000000000000021 R9 =0000000000000001 R10=000000000000000d R11=0000000000000000
240. 04/06 21:46:59 DEBUG| utils:0153| [stderr] R12=0000000000000000 R13=0000000000000008 R14=0000000000000001 R15=0000000000000000
241. 04/06 21:46:59 DEBUG| utils:0153| [stderr] RIP=0000000000404767 RFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
242. 04/06 21:46:59 DEBUG| utils:0153| [stderr] ES =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
243. 04/06 21:46:59 DEBUG| utils:0153| [stderr] CS =0008 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
244. 04/06 21:46:59 DEBUG| utils:0153| [stderr] SS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
245. 04/06 21:46:59 DEBUG| utils:0153| [stderr] DS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
246. 04/06 21:46:59 DEBUG| utils:0153| [stderr] FS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
247. 04/06 21:46:59 DEBUG| utils:0153| [stderr] GS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
248. 04/06 21:46:59 DEBUG| utils:0153| [stderr] LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT
249. 04/06 21:46:59 DEBUG| utils:0153| [stderr] TR =0080 000000008b41d48a 00000067 00008b00 DPL=0 TSS64-busy
250. 04/06 21:46:59 DEBUG| utils:0153| [stderr] GDT= 000000000041d00a 0000ffff
251. 04/06 21:46:59 DEBUG| utils:0153| [stderr] IDT= 0000000000000000 0000ffff
252. 04/06 21:46:59 DEBUG| utils:0153| [stderr] CR0=80010031 CR2=0000000000000000 CR3=0000000000477000 CR4=00002020
253. 04/06 21:46:59 DEBUG| utils:0153| [stderr] DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
254. 04/06 21:46:59 DEBUG| utils:0153| [stderr] DR6=00000000ffff0ff0 DR7=0000000000000400
255. 04/06 21:46:59 DEBUG| utils:0153| [stderr] EFER=0000000000000500
256. 04/06 21:46:59 DEBUG| utils:0153| [stderr] Code=00 0f 79 d0 0f 96 c0 b8 14 6c 00 00 0f 79 c4 0f 01 c2 eb 50 <55> 48 89 e5 b8 02 44 00 00 0f 78 c0 05 df ff ff 7f 83 f8 01 76 2e 41 b8 b8 62 42 00 b9 02
257. 04/06 21:47:25 DEBUG| utils:0153| ...

Failed with timeout on xenial/linux-oracle: 4.15.0-1069.77~16.04.1 for sru-20210315

229. 	04/06 21:46:56 DEBUG| utils:0153| [stdout] PASS: HOST_CR3 8000000000477000: VMX inst error is 8 (actual 8)
230. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware error 0x80000021
231. 	04/06 21:46:59 DEBUG| utils:0153| [stderr]
232. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] If you're running a guest on an Intel machine without unrestricted mode
233. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] support, the failure can be most likely due to the guest entering an invalid
234. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] state for Intel VT. For example, the guest maybe running in big real mode
235. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] which is not supported on less recent Intel processors.
236. 	04/06 21:46:59 DEBUG| utils:0153| [stderr]
237. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] RAX=0000000000006c14 RBX=0000000000000000 RCX=000000000046e680 RDX=0000000000006c16
238. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] RSI=0000000000000000 RDI=0000000000000008 RBP=000000000046e790 RSP=000000000046e768
239. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] R8 =0000000000000021 R9 =0000000000000001 R10=000000000000000d R11=0000000000000000
240. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] R12=0000000000000000 R13=0000000000000008 R14=0000000000000001 R15=0000000000000000
241. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] RIP=0000000000404767 RFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
242. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] ES =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
243. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] CS =0008 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA]
244. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] SS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
245. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] DS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
246. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] FS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
247. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] GS =0010 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA]
248. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT
249. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] TR =0080 000000008b41d48a 00000067 00008b00 DPL=0 TSS64-busy
250. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] GDT= 000000000041d00a 0000ffff
251. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] IDT= 0000000000000000 0000ffff
252. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] CR0=80010031 CR2=0000000000000000 CR3=0000000000477000 CR4=00002020
253. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
254. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] DR6=00000000ffff0ff0 DR7=0000000000000400
255. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] EFER=0000000000000500
256. 	04/06 21:46:59 DEBUG| utils:0153| [stderr] Code=00 0f 79 d0 0f 96 c0 b8 14 6c 00 00 0f 79 c4 0f 01 c2 eb 50 <55> 48 89 e5 b8 02 44 00 00 0f 78 c0 05 df ff ff 7f 83 f8 01 76 2e 41 b8 b8 62 42 00 b9 02
257. 	04/06 21:47:25 DEBUG| utils:0153| [stderr] qemu-system-x86_64: terminating on signal 15 from pid 27452
258. 	04/06 21:47:25 DEBUG| utils:0153| [stdout] FAIL vmx_host_state_area (timeout; duration=30)

tags:

added: sru-20210315

Kleber Sacilotto de Souza (kleber-souza) on 2021-05-03

tags:

added: sru-20210412

Revision history for this message

Kleber Sacilotto de Souza (kleber-souza) wrote on 2021-05-07:

#10

Found with trusty/linux-azure 4.15.0-1114.127~14.04.1.

Revision history for this message

Ian May (ian-may) wrote on 2021-05-26:

#11

bionic/linux-aws: 4.15.0-1103.110

tags:

added: sru-20210510

Revision history for this message

Ian May (ian-may) wrote on 2021-05-27:

#12

Found on bionic/linux-aws-fips: 4.15.0-2045.47

Revision history for this message

Ian May (ian-may) wrote on 2021-05-27:

#13

Found on bionic/linux-azure-4.15: 4.15.0-1115.128

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2021-06-15:

#14

Found on 5.11.0-1009.9+21.10.1-kvm

FAIL: "CR4.PCIDE" set: vmlaunch succeeds
FAIL: HOST_RIP 10040523c: vmlaunch succeeds
FAIL: HOST_RIP 100040523c: vmlaunch succeeds
FAIL: HOST_RIP 1000040523c: vmlaunch succeeds
FAIL: HOST_RIP 10000040523c: vmlaunch succeeds
FAIL: HOST_RIP 100000040523c: vmlaunch succeeds
FAIL: HOST_RIP 1000000040523c: vmlaunch succeeds
FAIL: HOST_RIP 10000000040523c: vmlaunch succeeds
FAIL: HOST_RIP 100000000040523c: vmlaunch succeeds

FAIL vmx_host_state_area (1009 tests, 9 unexpected failures)

tags:

added: sru-20210531

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2021-06-17:

#15

Observed in H/KVM, cycle sru-20210531.

tags:

added: 5.11 hirsute kvm

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2021-06-18:

#16

Observed in G/KVM, cycle sru-20210531.

tags:

added: 5.8 groovy linux-kvm

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2021-06-18:

#17

Observed in F/KVM, cycle sru-20210531.

tags:

added: focal

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2021-06-18:

#18

The test failed with timeout on B/KVM, cycle sru-20210531.

Revision history for this message

Guilherme G. Piccoli (gpiccoli) wrote on 2021-06-21:

#19

Also in T-4.15/Azure, cycle sru-20210531.

Revision history for this message

Kelsey Steele (kelsey-steele) wrote on 2021-06-21:

#20

Failing on F/fips 5.4.0-1027.31 host rizzo with

805. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: "CR4.PCIDE" set: vmlaunch succeeds
806. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: HOST_RIP 100405602: vmlaunch succeeds
807. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: HOST_RIP 1000405602: vmlaunch succeeds
808. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: HOST_RIP 10000405602: vmlaunch succeeds
809. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: HOST_RIP 100000405602: vmlaunch succeeds
810. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: HOST_RIP 1000000405602: vmlaunch succeeds
811. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: HOST_RIP 10000000405602: vmlaunch succeeds
812. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: HOST_RIP 100000000405602: vmlaunch succeeds
813. 06/11 15:21:36 DEBUG| utils:0153| [stdout] FAIL: HOST_RIP 1000000000405602: vmlaunch succeeds

Krzysztof Kozlowski (krzk) on 2021-07-01

tags:

added: sru-20210621

Revision history for this message

Krzysztof Kozlowski (krzk) wrote on 2021-07-14:

#21

For the actual failure like "FAIL: "CR4.PCIDE" set: vmlaunch succeeds" please go to lp:1936224

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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