RemoM
Contributor
Contributor

server (vsphere 7.0) crashes after few days

I ve installed vspehere 7.0 with the following specs (Gigabyte Aorus Elite x570 Motherboard, AMD Rizen x3700 CPU and Samsung 970 EVO Plus 2 NVMe 2TB (storage)

After few days the server crashed each time.

Please adivse to how solve this issue?

Regards,

Ram

/var/log/LogEFI.log shows

2020-06-13T15:12:15.682Z cpu1:1061755)VMware ESXi 7.0.0 [Releasebuild-15843807 x86_64]

#GP Exception 13 in world 1061755:vmm0:Win_Ext @ 0x4200360ded93

2020-06-13T15:12:15.684Z cpu1:1061755)cr0=0x80050033 cr2=0x0 cr3=0x1ea9f2000 cr4=0x150668

2020-06-13T15:12:15.685Z cpu1:1061755)FMS=17/71/0 uCode=0x8701013

2020-06-13T15:12:15.686Z cpu1:1061755)frame=0x451a1671b970 ip=0x4200360ded93 err=0 rflags=0x10016

2020-06-13T15:12:15.687Z cpu1:1061755)rax=0x6ac84800003bc rbx=0x451a19aa1100 rcx=0x1000

2020-06-13T15:12:15.687Z cpu1:1061755)rdx=0xef rbp=0xef rsi=0x1

2020-06-13T15:12:15.688Z cpu1:1061755)rdi=0x4519c00f0000 r8=0x430076aeb770 r9=0x430076aebb90

2020-06-13T15:12:15.689Z cpu1:1061755)r10=0xe036a0 r11=0x0 r12=0xef

2020-06-13T15:12:15.689Z cpu1:1061755)r13=0x0 r14=0x0 r15=0x42003613e378

*PCPU1:1061755/vmm0:Win_Ext

PCPU  0: SVVSVSVUSVVIVIVS

2020-06-13T15:12:15.691Z cpu1:1061755)Code start: 0x420036000000 VMK uptime: 9:06:30:50.522

2020-06-13T15:12:15.693Z cpu1:1061755)0x451a1671ba30:[0x4200360ded93]IntrCookie_DoInterrupt@vmkernel#nover+0x53 stack: 0x0

2020-06-13T15:12:15.695Z cpu1:1061755)0x451a1671bae0:[0x4200360df3b9]IntrCookie_VmkernelInterrupt@vmkernel#nover+0x3a stack: 0xffffffffffffffef

2020-06-13T15:12:15.696Z cpu1:1061755)0x451a1671bb00:[0x42003613e414]IDT_IntrHandler@vmkernel#nover+0x9d stack: 0x0

2020-06-13T15:12:15.697Z cpu1:1061755)0x451a1671bb20:[0x420036154067]gate_entry@vmkernel#nover+0x68 stack: 0x0

2020-06-13T15:12:15.699Z cpu1:1061755)0x451a1671bbe8:[0x420036086ab7]Power_ArchPerformWait@vmkernel#nover+0xc3 stack: 0x420040400880

2020-06-13T15:12:15.701Z cpu1:1061755)0x451a1671bbf0:[0x420036086bd2]Power_ArchSetCState@vmkernel#nover+0x8f stack: 0x800000000

2020-06-13T15:12:15.702Z cpu1:1061755)0x451a1671bc40:[0x42003635a304]CpuSchedIdleLoopInt@vmkernel#nover+0x23d stack: 0x420040400108

2020-06-13T15:12:15.704Z cpu1:1061755)0x451a1671bcb0:[0x42003635d19e]CpuSchedDispatch@vmkernel#nover+0x14d3 stack: 0x420040400120

2020-06-13T15:12:15.705Z cpu1:1061755)0x451a1671bee0:[0x42003635e1d8]CpuSchedWait@vmkernel#nover+0x275 stack: 0x1

2020-06-13T15:12:15.707Z cpu1:1061755)0x451a1671bf50:[0x42003635e9a3]CpuSched_VcpuHalt@vmkernel#nover+0x13c stack: 0x1e

2020-06-13T15:12:15.708Z cpu1:1061755)0x451a1671bfa0:[0x42003612a2b6]VMMVMKCall_Call@vmkernel#nover+0xf7 stack: 0x0

2020-06-13T15:12:15.710Z cpu1:1061755)0x451a1671bfe0:[0x42003614e0c5]VMKVMM_ArchEnterVMKernel@vmkernel#nover+0xe stack: 0x42003614e0b8

2020-06-13T15:12:15.712Z cpu1:1061755)base fs=0x0 gs=0x420040400000 Kgs=0x0

2020-06-19T11:01:10.694Z cpu0:1049326)VMware ESXi 7.0.0 [Releasebuild-15843807 x86_64]

VERIFY bora/vmkernel/sched/cpusched.c:10893

2020-06-19T11:01:10.696Z cpu0:1049326)cr0=0x8001003d cr2=0x430000ede000 cr3=0xdcc7e000 cr4=0x10016c

2020-06-19T11:01:10.697Z cpu0:1049326)FMS=17/71/0 uCode=0x8701013

*PCPU0:1049326/tq:tcpip4

PCPU  0: SSSSUUSVIISVIISV

2020-06-19T11:01:10.698Z cpu0:1049326)Code start: 0x420021000000 VMK uptime: 5:18:44:21.568

2020-06-19T11:01:10.700Z cpu0:1049326)0x451a10b9bc50:[0x4200210fc6ce]PanicvPanicInt@vmkernel#nover+0x2c6 stack: 0x4200210fc6ce

2020-06-19T11:01:10.701Z cpu0:1049326)0x451a10b9bd00:[0x4200210fcbac]Panic_NoSave@vmkernel#nover+0x4d stack: 0x451a10b9bd60

2020-06-19T11:01:10.703Z cpu0:1049326)0x451a10b9bd60:[0x4200210fd155]Panic_OnAssertAt@vmkernel#nover+0xd2 stack: 0x2a8d00000000

2020-06-19T11:01:10.704Z cpu0:1049326)0x451a10b9bdf0:[0x42002113e0eb]Int6_UD2Assert@vmkernel#nover+0x1f8 stack: 0x0

2020-06-19T11:01:10.706Z cpu0:1049326)0x451a10b9be10:[0x420021154067]gate_entry@vmkernel#nover+0x68 stack: 0x0

2020-06-19T11:01:10.707Z cpu0:1049326)0x451a10b9bed0:[0x42002135e1b8]CpuSchedWait@vmkernel#nover+0x254 stack: 0x4abd4317deed2704

2020-06-19T11:01:10.709Z cpu0:1049326)0x451a10b9bf40:[0x42002135e2b8]CpuSched_NoEvqWait@vmkernel#nover+0x19 stack: 0x0

2020-06-19T11:01:10.711Z cpu0:1049326)0x451a10b9bf50:[0x42002102eb80]VmkTimerQueueWorldFunc@vmkernel#nover+0x319 stack: 0x4abd4317deed2704

2020-06-19T11:01:10.712Z cpu0:1049326)0x451a10b9bfe0:[0x42002135ef79]CpuSched_StartWorld@vmkernel#nover+0x82 stack: 0x0

2020-06-19T11:01:10.713Z cpu0:1049326)0x451a10b9c000:[0x4200210c5303]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0

2020-06-19T11:01:10.716Z cpu0:1049326)base fs=0x0 gs=0x420040000000 Kgs=0x0

2020-06-19T22:15:58.953Z cpu0:1048841)VMware ESXi 7.0.0 [Releasebuild-15843807 x86_64]

CPU 0 / World 1048841 tried to re-acquire lock

2020-06-19T22:15:58.955Z cpu0:1048841)cr0=0x8001003d cr2=0xf cr3=0xdcc7e000 cr4=0x10016c

2020-06-19T22:15:58.956Z cpu0:1048841)FMS=17/71/0 uCode=0x8701013

*PCPU0:1048841/VSCSIPoll

PCPU  0: SSVSVSVUVVVVVVVS

2020-06-19T22:15:58.957Z cpu0:1048841)Code start: 0x42000f000000 VMK uptime: 0:09:24:18.812

2020-06-19T22:15:58.959Z cpu0:1048841)0x451a0849b830:[0x42000f0fc6ce]PanicvPanicInt@vmkernel#nover+0x2c6 stack: 0x42000f0fc6ce

2020-06-19T22:15:58.961Z cpu0:1048841)0x451a0849b8e0:[0x42000f0fcbac]Panic_NoSave@vmkernel#nover+0x4d stack: 0x451a0849b940

2020-06-19T22:15:58.962Z cpu0:1048841)0x451a0849b940:[0x42000f01eaac]LockCheckSelfDeadlockInt@vmkernel#nover+0x95 stack: 0x52f6be00000000

2020-06-19T22:15:58.964Z cpu0:1048841)0x451a0849b950:[0x42000f1063e7]SP_WaitLockIRQ@vmkernel#nover+0x190 stack: 0x451a084a1000

2020-06-19T22:15:58.965Z cpu0:1048841)0x451a0849b9a0:[0x42000f106455]SPLockIRQWork@vmkernel#nover+0x3e stack: 0x420040000000

2020-06-19T22:15:58.967Z cpu0:1048841)0x451a0849b9c0:[0x42000f359b02]CpuSched_IdleHaltEnd@vmkernel#nover+0x3b stack: 0xef

2020-06-19T22:15:58.968Z cpu0:1048841)0x451a0849ba00:[0x42000f0df201]IntrCookie_DoInterrupt@vmkernel#nover+0x4c2 stack: 0x0

2020-06-19T22:15:58.970Z cpu0:1048841)0x451a0849bab0:[0x42000f0df3b9]IntrCookie_VmkernelInterrupt@vmkernel#nover+0x3a stack: 0xffffffffffffffef

2020-06-19T22:15:58.972Z cpu0:1048841)0x451a0849bad0:[0x42000f13e414]IDT_IntrHandler@vmkernel#nover+0x9d stack: 0x0

2020-06-19T22:15:58.973Z cpu0:1048841)0x451a0849baf0:[0x42000f154067]gate_entry@vmkernel#nover+0x68 stack: 0x0

2020-06-19T22:15:58.975Z cpu0:1048841)0x451a0849bbb8:[0x42000f086ab7]Power_ArchPerformWait@vmkernel#nover+0xc3 stack: 0x420040000880

2020-06-19T22:15:58.976Z cpu0:1048841)0x451a0849bbc0:[0x42000f086bd2]Power_ArchSetCState@vmkernel#nover+0x8f stack: 0x800000000

2020-06-19T22:15:58.978Z cpu0:1048841)0x451a0849bc10:[0x42000f35a304]CpuSchedIdleLoopInt@vmkernel#nover+0x23d stack: 0x420040000108

2020-06-19T22:15:58.980Z cpu0:1048841)0x451a0849bc80:[0x42000f35d19e]CpuSchedDispatch@vmkernel#nover+0x14d3 stack: 0x420040000120

2020-06-19T22:15:58.981Z cpu0:1048841)0x451a0849beb0:[0x42000f35e1d8]CpuSchedWait@vmkernel#nover+0x275 stack: 0x1

2020-06-19T22:15:58.983Z cpu0:1048841)0x451a0849bf20:[0x42000f35e37d]CpuSchedSleepUntilTC@vmkernel#nover+0xbe stack: 0x4519c0000430

2020-06-19T22:15:58.984Z cpu0:1048841)0x451a0849bfb0:[0x42000f4b2382]VSCSIPollCallback@vmkernel#nover+0x123 stack: 0x451a084a1100

2020-06-19T22:15:58.986Z cpu0:1048841)0x451a0849bfe0:[0x42000f35ef79]CpuSched_StartWorld@vmkernel#nover+0x82 stack: 0x0

2020-06-19T22:15:58.987Z cpu0:1048841)0x451a0849c000:[0x42000f0c5303]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0

2020-06-19T22:15:58.989Z cpu0:1048841)base fs=0x0 gs=0x420040000000 Kgs=0x0

0 Kudos
7 Replies
scott28tt
VMware Employee
VMware Employee

You can use the various options on this page to check that your hardware is supported for ESXi 7.0:

VMware Compatibility Guide - System Search

0 Kudos
RemoM
Contributor
Contributor

It looks like that my hardware is not supported.

AMD Rizen CPU, Gigabyte motherboard, Samsung 970 Evo plus 2.

0 Kudos
dariusd
Leadership
Leadership

Even though your hardware is not officially supported, it might be worth checking whether you have the latest firmware (BIOS/EFI) installed for your Gigabyte Aorus Elite x570 Motherboard and updating it if a newer firmware version is available.

Thanks,

--

Darius

0 Kudos
RemoM
Contributor
Contributor

I already updated the motherboard with the latest firmware version.

Regards,

Ram

0 Kudos
dariusd
Leadership
Leadership

Have you tried running hardware diagnostic tests (e.g. MemTest86+ or similar)?  That's about the only other thing I can think of trying, just in case it manages to find something.

--

Darius

0 Kudos
RemoM
Contributor
Contributor

No i didnot try any hardware diagnostic tests.

I check MemTest86.

Thanks,

Ram

0 Kudos
RemoM
Contributor
Contributor

I checked my hardware and it works ok. I decided to switch to Proxmox and this works ok with my hardware.

Regards,

Ram

0 Kudos