Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ESXi host crashes with a PSOD if seSparse snapshot created on base vmdk of size that is not 4K aligned (67765)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 12199Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

ESXi host crashes with a PSOD  - @BlueScreen: PCPU 11: no heartbeat (3/3 IPIs received)

You will see similar messages as below

@BlueScreen: PCPU 11: no heartbeat (3/3 IPIs received)

YYYY-MM-DDTHH:MM:SS.609Z cpu12:68535)@BlueScreen: PCPU 11: no heartbeat (3/3 IPIs received)

YYYY-MM-DDTHH:MM:SS.609Z cpu12:68535)Code start: 0x418037800000 VMK uptime: 115:12:44:05.065
YYYY-MM-DDTHH:MM:SS.609Z cpu12:68535)Saved backtrace from: pcpu 11 Heartbeat NMI
YYYY-MM-DDTHH:MM:SS.610Z cpu12:68535)0x43932041b770:[0x4180378698aa]DevFSIoctl@vmkernel#nover+0x1f6 stack: 0x43932041b7d0
YYYY-MM-DDTHH:MM:SS.610Z cpu12:68535)0x43932041b810:[0x41803783e344]FSSVec_Ioctl@vmkernel#nover+0x6c stack: 0x514c7428
YYYY-MM-DDTHH:MM:SS.610Z cpu12:68535)0x43932041b860:[0x41803783acaa]FSS_IoctlByFH@vmkernel#nover+0x9a stack: 0x19
YYYY-MM-DDTHH:MM:SS.611Z cpu12:68535)0x43932041b8a0:[0x418038a6bff9]CBT_Ioctl@(cbt)#<None>+0x201 stack: 0x0
YYYY-MM-DDTHH:MM:SS.611Z cpu12:68535)0x43932041b940:[0x418037869897]DevFSIoctl@vmkernel#nover+0x1e3 stack: 0x500735f55bb24bda
YYYY-MM-DDTHH:MM:SS.611Z cpu12:68535)0x43932041b9e0:[0x41803783e344]FSSVec_Ioctl@vmkernel#nover+0x6c stack: 0x416c742b
YYYY-MM-DDTHH:MM:SS.611Z cpu12:68535)0x43932041ba30:[0x41803783acaa]FSS_IoctlByFH@vmkernel#nover+0x9a stack: 0x43054028b940
YYYY-MM-DDTHH:MM:SS.612Z cpu12:68535)0x43932041ba70:[0x418037b66e09]VSCSIFsEmulateCommand@vmkernel#nover+0x15dd stack: 0x430013cb6bc0
YYYY-MM-DDTHH:MM:SS.612Z cpu12:68535)0x43932041bc70:[0x418037b680ec]VSCSI_FSCommand@vmkernel#nover+0xe4 stack: 0xffff8103c700dff0
YYYY-MM-DDTHH:MM:SS.612Z cpu12:68535)0x43932041bd40:[0x418037b5d5c5]VSCSI_IssueCommandBE@vmkernel#nover+0x31 stack: 0x43054028b940
YYYY-MM-DDTHH:MM:SS.613Z cpu12:68535)0x43932041bd80:[0x418037b5ea6c]VSCSIExecuteCommandInt@vmkernel#nover+0x3b4 stack: 0x823ac9000
YYYY-MM-DDTHH:MM:SS.613Z cpu12:68535)0x43932041be10:[0x418037b70d0b]LSIProcessReqInt@vmkernel#nover+0x6fb stack: 0x43932041beab
YYYY-MM-DDTHH:MM:SS.613Z cpu12:68535)0x43932041bf50:[0x418037b7142e]LSI_ProcessReq@vmkernel#nover+0x66 stack: 0x439334d27100
YYYY-MM-DDTHH:MM:SS.614Z cpu12:68535)0x43932041bf80:[0x4180379197d7]VMMVMKCall_Call@vmkernel#nover+0x157 stack: 0x43932041bfec
YYYY-MM-DDTHH:MM:SS.614Z cpu12:68535)0x43932041bfe0:[0x41803794b8a2]VMKVMM_ArchEnterVMKernel@vmkernel#nover+0xe stack: 0x0
YYYY-MM-DDTHH:MM:SS.618Z cpu12:68535)base fs=0x0 gs=0x418043000000 Kgs=0x0

In the vmkernel.log you will see message as below related to seSparse snapshot created on base vmdk of size that is not 4K aligned -  numBlocks=4080218930

YYYY-MM-DDTHH:MM:SS.582Z cpu18:2319716)VSCSI: 3801: handle 22158(vscsi0:1):Creating Virtual Device for world 2319506 (FSS handle 6974411622) numBlocks=4080218930 (bs=512)
YYYY-MM-DDTHH:MM:SS582Z cpu18:2319716)VSCSI: 273: handle 22158(vscsi0:1):Input values: res=0 limit=-2 bw=-1 Shares=1000
YYYY-MM-DDTHH:MM:SS cpu18:2319716)FDS: 586: Enabling IO coalescing on driver 'deltadisks' device '148851367-vmname-000001-sesparse.vmdk'
YYYY-MM-DDTHH:MM:SS.589Z cpu18:2319716)CBT: 1310: Created device 106c11369-cbt for cbt driver with filehandle 4408284009

Solution

This issue is resolved in VMware ESXi 6.5 Update 3 and VMware ESXi 6.7 Update 3 available at VMware Downloads.

To work around this issue if you do not want to upgrade, specify the size of disk in GB or TB it would be 4K aligned (in other words, size is completely divisible by 4096)

In this example above here size of the base vmdk "vmname.vmdk" was 4080218930 sectors for 512 bytes each. If this size is rounded up to 4080218936 sectors it will be 4K aligned. By extending size of this vmdk to 4080218936 sectors this issue can be avoided.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Windows 静默快照创建失败，并显示错误 0x80042413 (67869)

KB
•
vCenter Server Appliance REST-API 调用失败：授权用户无法调用 (67483)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant