[Bug 120971] New: KVM: entry failed, hardware error 0x80000021 on Intel Host

* [Bug 120971] New: KVM: entry failed, hardware error 0x80000021 on Intel Host
@ 2016-06-24 18:33 bugzilla-daemon
  2016-06-25  7:22 ` [Bug 120971] " bugzilla-daemon
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: bugzilla-daemon @ 2016-06-24 18:33 UTC (permalink / raw)
  To: kvm

https://bugzilla.kernel.org/show_bug.cgi?id=120971

            Bug ID: 120971
           Summary: KVM: entry failed, hardware error 0x80000021 on Intel
                    Host
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.7.0-rc4-mainline
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: joseph.knockenhauer@gmail.com
        Regression: No

hardware is as follows:

Intel i5 6600K
32Gig DDR4 Memory 
GTX 980ti
2 SSD
2 HDD

Using qemu-kvm and ovmf the following error occurs erratically when booted into
a windows 10 host:

KVM: entry failed, hardware error 0x80000021

If you're running a guest on an Intel machine without unrestricted mode
support, the failure can be most likely due to the guest entering an invalid
state for Intel VT. For example, the guest maybe running in big real mode
which is not supported on less recent Intel processors.

RAX=ffffffffffd148c0 RBX=0000000000000000 RCX=0000000000000086
RDX=0000000000000                                 000
RSI=ffffda819a1e1180 RDI=ffff910d6ee037b0 RBP=0000000000000000
RSP=ffffda819a1f7                                 758
R8 =00000000ffffffff R9 =0000000000000000 R10=00000000ffffffff
R11=0000000000000                                 000
R12=00000000a71b10d9 R13=0000000000000046 R14=0000000000000000
R15=0000000000000                                 000
RIP=fffff8013c22615f RFL=00000282 [--S----] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA]
SS =0018 0000000000000000 00000000 00409300 DPL=0 DS   [-WA]
DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
FS =0053 00000000b300c000 0000fc00 0040f300 DPL=3 DS   [-WA]
GS =002b ffffda819a1e1000 ffffffff 00c0f300 DPL=3 DS   [-WA]
LDT=0000 0000000000000000 ffffffff 00000000
TR =0040 ffffda819a1e7b40 00000067 00008b00 DPL=0 TSS64-busy
GDT=     ffffda819a1eec00 0000006f
IDT=     ffffda819a1eec70 00000fff
CR0=80050033 CR2=0000000000000030 CR3=00000000001ab000 CR4=001506f8
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
DR3=0000000000000                                 000
DR6=00000000fffe0ff0 DR7=0000000000000400
EFER=0000000000000d01
Code=00 00 00 00 00 48 83 ec 28 e8 47 b3 ff ff 48 83 c4 28 fb f4 <c3> cc cc cc
c                                 c cc cc 66 66 0f 1f 84 00 00 00 00 00 0f 20
d0 0f 22 d0 c3 cc cc cc cc cc cc

The error occurs whether or not pci devices are passed through to the host or
not, and in every conceivable processor configuration that works for Windows
guests. 

The error occurs approximately 10 minutes into using the machine (give or take
a few minutes).

Occasionally the error occurs on boot of the guest. 

This has also happened on previous kernels. 

Currently I have the kvm_intel module loaded with
emulate_invalid_guest_state=0, although it also occurs in the same capacity if
the parameter is set to 1.

Please feel free to contact me for additional information.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 9+ messages in thread