Skip to main content

vSphere ESXi 6.7, 6.5, 6.0, 5.5 PSOD due to an invalid pointer value being detected.


 

 

  Symptoms

  • ESXi may encounter the following system alert:

2019-05-02T19:44:08.966Z cpu55:66539)CpuSched: 4838: Unexpected runqueue state encountered!

  • ESXi may encounter a PSOD when operating on a linked-list data structure inside the vmkernel. The PSOD backtrace will be similar to the following:

[0x418007b0688f]CpuSchedQueueAdd@vmkernel#nover+0xcf stack: 0x7388e490eaa7f
[0x418007b06ad4]CpuSchedVcpuMakeReady@vmkernel#nover+0xad stack: 0x4529eac23780
[0x418007b06cb2]CpuSchedWorldWakeup@vmkernel#nover+0x8b stack: 0x4529ead23100
[0x418007b07150]CpuSchedForceWakeupInt@vmkernel#nover+0x10d stack: 0x4529f20a3000  
0x418007b12d97]CpuSchedActionNotifyTraditional@vmkernel#nover+0x9c stack: 0x0
[0x418007b12e25]CpuSched_ActionNotifyHierarchical@vmkernel#nover+0x7e stack: 0x0
[0x418007b12f89]CpuSched_ActionNotifyVCPUs@vmkernel#nover+0x22 stack: 0x1c
[0x41800793659e]VMMVMKCall_Call@vmkernel#nover+0xf7 stack: 0x0

Or

[0x41803b2c215d]CpuSchedPcpuVcpuChooseInt@vmkernel#nover+0x19 stack: 0x418040000080, 0x10b, 0x0, 0x1, 0x418040000080
[0x41803b2c3f46]CpuSched_PcpuChoose@vmkernel#nover+0xfe stack: 0x3ff, 0xfffffffffffe, 0x0, 0x418040000000, 0x0
[0x41803b2d8359]CpuSchedRebalance_PcpuMigrateIdle@vmkernel#nover+0x17d stack: 0xc64ff6b3c8815, 0x4310080086e8, 0x4310080086d8, 0x43a3e6b9bc90, 0x400000000
[0x41803b2c9931]CpuSchedDispatch@vmkernel#nover+0x1331 stack: 0x410000000001, 0x418045400000,

 Or

[0x41800fb1299a]CpuSched_Charge@vmkernel#nover+0x1ea stack: 0x418040400080
[0x41800fb0c483]CpuSchedDispatch@vmkernel#nover+0xac stack: 0x418040000108
[0x41800f9365e3]VMMVMKCall_Call@vmkernel#nover+0x13c stack: 0x0
[0x41800f95c7ed]VMKVMM_ArchEnterVMKernel@vmkernel#nover+0xe stack: 0x41800f95c7e0

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

ESXi panics when an invalid pointer value is detected while operating on a linked list protected by a spinlock. While the spinlock is being held, the values in the linked list are assured by hardware not to change during these operations, but unexpectedly a transient invalid value is seen. The invalid value is frequently null (0), but is sometimes some other incorrect value, such as a non-canonical address.

The root cause of this issue is not known at this time and is being investigated by our hardware partners.

Resolution

There is no known resolution at this time.

 

Comments

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...
Post a Comment
Read more

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...
Post a Comment
Read more

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...
Post a Comment
Read more