topic Re:Issue of "KVM: entry failed, hardware error 0x80000021" on Intel Xeon Gold 6248R in Mobile and Desktop Processors

Issue of "KVM: entry failed, hardware error 0x80000021" on Intel Xeon Gold 6248R

GuangyaoJiang — Sat, 09 Sep 2023 02:24:09 GMT

Hi,

The VMs running on several servers will be stopped after running for a period of time. i want to how to fix it, it's a kernel issuse or an FW bug? Thaks.

The qemu log reports the following error:

=========================================================

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.

EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000000

ESI=c41fbc50 EDI=00000033 EBP=c41fbd00 ESP=fffffee8

EIP=00000000 EFL=00000282 [--S----] CPL=3 II=0 A20=1 SMM=0 HLT=0

ES =002b 00000000 ffffffff 00c0f300 DPL=3 DS [-WA]

CS =0023 00000000 ffffffff 00c0fb00 DPL=3 CS32 [-RA]

SS =002b 00000000 ffffffff 00c0f300 DPL=3 DS [-WA]

DS =002b 00000000 ffffffff 00c0f300 DPL=3 DS [-WA]

FS =0053 00000000 0000bc00 0040f300 DPL=3 DS [-WA]

GS =002b c3f30000 ffffffff 00c0f300 DPL=3 DS [-WA]

LDT=0000 00000000 00000000 00000000

TR =0040 3b55d000 00000067 00008b00 DPL=0 TSS64-busy

GDT= ffffbf813b55efb0 00000057

IDT= ffffbf813b55c000 00000fff

CR0=80050031 CR2=00007ffcf9380000 CR3=00000000203b7000 CR4=00350ef8

DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000

DR6=00000000fffe0ff0 DR7=0000000000000400

EFER=0000000000000d01

Code=00 00 00 00 fe ff ff ff 23 00 00 00 00 00 00 00 00 00 0f a2 <??> ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??

==========================================================

at the same time, some kernel message like belowing.

========================================

2023-09-04T15:13:28.481952+02:00|err|kernel[-]|[9069029.416846] *** Guest State ***

2023-09-04T15:13:28.481991+02:00|err|kernel[-]|[9069029.416849] CR0: actual=0x0000000080050031, shadow=0x0000000080050031, gh_mask=fffffffffffffff7

2023-09-04T15:13:28.482001+02:00|err|kernel[-]|[9069029.416849] CR4: actual=0x00000000003526f8, shadow=0x0000000000350ef8, gh_mask=fffffffffffff871

2023-09-04T15:13:28.482008+02:00|err|kernel[-]|[9069029.416850] CR3 = 0x00000000203b7000

2023-09-04T15:13:28.482015+02:00|err|kernel[-]|[9069029.416851] PDPTR0 = 0x0000000000000000 PDPTR1 = 0x0000022000000000

2023-09-04T15:13:28.482025+02:00|err|kernel[-]|[9069029.416852] PDPTR2 = 0x0000000100000001 PDPTR3 = 0x0000022000000000

2023-09-04T15:13:28.482033+02:00|err|kernel[-]|[9069029.416852] RSP = 0x00000000fffffee8 RIP = 0x0000000100000000

2023-09-04T15:13:28.482040+02:00|err|kernel[-]|[9069029.416853] RFLAGS=0x00000282 DR7 = 0x0000000000000400

2023-09-04T15:13:28.482048+02:00|err|kernel[-]|[9069029.416854] Sysenter RSP=0000000000000000 CS:RIP=0000:0000000000000000

2023-09-04T15:13:28.482055+02:00|err|kernel[-]|[9069029.416855] CS: sel=0x0023, attr=0x0c0fb, limit=0xffffffff, base=0x0000000000000000

2023-09-04T15:13:28.482063+02:00|err|kernel[-]|[9069029.416856] DS: sel=0x002b, attr=0x0c0f3, limit=0xffffffff, base=0x0000000000000000

2023-09-04T15:13:28.482070+02:00|err|kernel[-]|[9069029.416856] SS: sel=0x002b, attr=0x0c0f3, limit=0xffffffff, base=0x0000000000000000

2023-09-04T15:13:28.482079+02:00|err|kernel[-]|[9069029.416857] ES: sel=0x002b, attr=0x0c0f3, limit=0xffffffff, base=0x0000000000000000

2023-09-04T15:13:28.482087+02:00|err|kernel[-]|[9069029.416858] FS: sel=0x0053, attr=0x040f3, limit=0x0000bc00, base=0x0000000000000000

2023-09-04T15:13:28.482095+02:00|err|kernel[-]|[9069029.416858] GS: sel=0x002b, attr=0x0c0f3, limit=0xffffffff, base=0x00000014c3f30000

2023-09-04T15:13:28.482101+02:00|err|kernel[-]|[9069029.416859] GDTR: limit=0x00000057, base=0xffffbf813b55efb0

2023-09-04T15:13:28.482109+02:00|err|kernel[-]|[9069029.416860] LDTR: sel=0x0000, attr=0x10000, limit=0x00000000, base=0x0000000000000000

2023-09-04T15:13:28.482116+02:00|err|kernel[-]|[9069029.416861] IDTR: limit=0x00000fff, base=0xffffbf813b55c000

2023-09-04T15:13:28.482124+02:00|err|kernel[-]|[9069029.416861] TR: sel=0x0040, attr=0x0008b, limit=0x00000067, base=0xffffbf813b55d000

2023-09-04T15:13:28.482131+02:00|err|kernel[-]|[9069029.416862] EFER = 0x0000000000000801 PAT = 0x0007010600070106

2023-09-04T15:13:28.482143+02:00|err|kernel[-]|[9069029.416863] DebugCtl = 0x0000000000000000 DebugExceptions = 0x0000000000000000

2023-09-04T15:13:28.482151+02:00|err|kernel[-]|[9069029.416863] BndCfgS = 0x0000000000000000

2023-09-04T15:13:28.482157+02:00|err|kernel[-]|[9069029.416864] Interruptibility = 00000000 ActivityState = 00000000

2023-09-04T15:13:28.482165+02:00|err|kernel[-]|[9069029.416865] InterruptStatus = 0000

2023-09-04T15:13:28.482172+02:00|err|kernel[-]|[9069029.416865] *** Host State ***

2023-09-04T15:13:28.482180+02:00|err|kernel[-]|[9069029.416866] RIP = 0xffffffffc1f488b0 RSP = 0xffffbb2aaf4a3c68

2023-09-04T15:13:28.482187+02:00|err|kernel[-]|[9069029.416867] CS=0010 SS=0018 DS=0000 ES=0000 FS=0000 GS=0000 TR=0040

2023-09-04T15:13:28.482194+02:00|err|kernel[-]|[9069029.416868] FSBase=00007f3a9dffb700 GSBase=ffff94c13fb80000 TRBase=fffffe0000e75000

2023-09-04T15:13:28.482202+02:00|err|kernel[-]|[9069029.416869] GDTBase=fffffe0000e73000 IDTBase=fffffe0000000000

2023-09-04T15:13:28.482212+02:00|err|kernel[-]|[9069029.416869] CR0=0000000080050033 CR3=00000007d14b2001 CR4=00000000003626e0

2023-09-04T15:13:28.482219+02:00|err|kernel[-]|[9069029.416870] Sysenter RSP=fffffe0000e74200 CS:RIP=0010:ffffffffa8a01790

2023-09-04T15:13:28.482226+02:00|err|kernel[-]|[9069029.416871] EFER = 0x0000000000000d01 PAT = 0x0407050600070106

2023-09-04T15:13:28.482233+02:00|err|kernel[-]|[9069029.416872] *** Control State ***

2023-09-04T15:13:28.482241+02:00|err|kernel[-]|[9069029.416872] PinBased=000000bf CPUBased=b5a06dfa SecondaryExec=021237ef

2023-09-04T15:13:28.482248+02:00|err|kernel[-]|[9069029.416873] EntryControls=000153ff ExitControls=008fefff

2023-09-04T15:13:28.482256+02:00|err|kernel[-]|[9069029.416874] ExceptionBitmap=00060042 PFECmask=00000000 PFECmatch=00000000

2023-09-04T15:13:28.482263+02:00|err|kernel[-]|[9069029.416874] VMEntry: intr_info=00000000 errcode=00000004 ilen=00000000

2023-09-04T15:13:28.482275+02:00|err|kernel[-]|[9069029.416875] VMExit: intr_info=00000000 errcode=00000000 ilen=00000002

2023-09-04T15:13:28.482284+02:00|err|kernel[-]|[9069029.416875] reason=80000021 qualification=0000000000000000

2023-09-04T15:13:28.482291+02:00|err|kernel[-]|[9069029.416876] IDTVectoring: info=00000000 errcode=00000000

2023-09-04T15:13:28.482299+02:00|err|kernel[-]|[9069029.416876] TSC Offset = 0xff93449c1d1f3016

2023-09-04T15:13:28.482306+02:00|err|kernel[-]|[9069029.416877] TSC Multiplier = 0x0001000000000000

2023-09-04T15:13:28.482314+02:00|err|kernel[-]|[9069029.416877] TPR Threshold = 0x00

2023-09-04T15:13:28.482321+02:00|err|kernel[-]|[9069029.416878] PostedIntrVec = 0xf2

2023-09-04T15:13:28.482330+02:00|err|kernel[-]|[9069029.416878] EPT pointer = 0x000000731a12c05e

2023-09-04T15:13:28.482337+02:00|err|kernel[-]|[9069029.416879] PLE Gap=00000001 Window=00000080

2023-09-04T15:13:28.482345+02:00|err|kernel[-]|[9069029.416879] Virtual processor ID = 0x002f

========================================

Re:Issue of "KVM: entry failed, hardware error 0x80000021" on Intel Xeon Gold 6248R

Allan_A_Intel — Tue, 12 Sep 2023 19:12:26 GMT

Hello GuangyaoJiang,

Thank you for reaching out to us regarding the issue you've encountered with the error message "KVM: entry failed, hardware error 0x80000021" on your server with Intel® Xeon® Gold 6248R Processor. I understand that this issue is causing disruptions to the VMs running on several servers, and you're seeking assistance in resolving it.

This error message typically points to a virtualization-related problem, which can be attributed to either hardware virtualization support or guest configuration. To address this issue, please consider the following steps:

QEMU Support Options: Review the QEMU documentation and support options, which can be found on their official website at https://www.qemu.org/support/. Here, you may find specific guidance on troubleshooting and resolving issues related to KVM virtualization.

Firmware and BIOS Updates: It's essential to keep your server's firmware and BIOS up to date. Sometimes, compatibility issues can be resolved through firmware updates. If you are using an Intel Server Board, kindly provide us with the model number and the current BIOS version. Additionally, let us know the host operating system you are using.

By following these steps, you can diagnose and potentially resolve the "KVM: entry failed, hardware error 0x80000021" issue. If you have any specific details about your server's configuration or if you encounter any challenges during these steps, please don't hesitate to reach out for further assistance.

We are committed to helping you resolve this matter promptly, and your feedback on the progress will be highly appreciated.

Best Regards,

Allan A.

Intel Customer Support

Re:Issue of "KVM: entry failed, hardware error 0x80000021" on Intel Xeon Gold 6248R

Allan_A_Intel — Fri, 15 Sep 2023 20:41:14 GMT

Hello GuangyaoJiang,

I hope this message finds you well. I wanted to follow up on our previous conversation regarding the "KVM: entry failed, hardware error 0x80000021" issue you're experiencing with your server equipped with the Intel® Xeon® Gold 6248R Processor.

In my last message, I provided some steps and recommendations to help resolve this issue. If you have had the chance to review them, please let me know if you require any further assistance or clarification. Your feedback is essential in assisting us in finding a solution that meets your needs.

If you haven't had a chance to look into the suggestions yet, that's perfectly fine too. I understand that technical issues can take time to troubleshoot. I want to assure you that we're here to support you throughout the process.

In case you need more assistance or have any questions, please don't hesitate to reach out. I'll be checking back in with you in 3 business days to ensure that everything is progressing smoothly.

Thank you for choosing Intel for your server needs, and we appreciate your patience as we work to resolve this issue.

Best regards,

Allan A.

Intel Customer Support

Re:Issue of "KVM: entry failed, hardware error 0x80000021" on Intel Xeon Gold 6248R

Allan_A_Intel — Wed, 20 Sep 2023 21:22:14 GMT

Hello GuangyaoJiang,

I hope you're well. I'm following up on our previous conversation about the "KVM: entry failed, hardware error 0x80000021" issue you're encountering with your server featuring the Intel® Xeon® Gold 6248R Processor.

It seems we haven't received further communication from you since my last message. We value your time and input, and we're here to assist you effectively.

Given the lack of recent updates, we'll be closing this case. If you encounter any further issues or have questions in the future, please feel free to start a new conversation, and we'll be glad to help.

Thank you for choosing Intel. We wish you the best with your server and any future endeavors.

Best regards,

Allan A.

Intel Customer Support