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

Upgrading host to ESXi 6.5.0 build-7388607 fails with PSOD (52617)

Last Updated: 7/23/2023Categories: TroubleshootingTotal Views: 6940Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Upgrading a host to ESXi 6.5.0 build-7388607 fails with the purple diagnostic screen.

2018-02-03T22:43:50.421Z cpu8:66965)@BlueScreen: Failed at bora/modules/vmkernel/vsan/dom/domOwner.c:2974 -- NOT REACHED
2018-02-03T22:43:50.422Z cpu8:66965)Code start: 0x41800f200000 VMK uptime: 0:00:02:13.357
2018-02-03T22:43:50.422Z cpu8:66965)0x43916ca9b990:[0x41800f2ed531]PanicvPanicInt@vmkernel#nover+0x545 stack: 0x41800f2ed531
2018-02-03T22:43:50.422Z cpu8:66965)0x43916ca9ba30:[0x41800f2ed8c7]Panic_vPanic@vmkernel#nover+0x23 stack: 0x0
2018-02-03T22:43:50.423Z cpu8:66965)0x43916ca9ba50:[0x41800f301501]vmk_PanicWithModuleID@vmkernel#nover+0x41 stack: 0x43916ca9bab0
2018-02-03T22:43:50.423Z cpu8:66965)0x43916ca9bab0:[0x418010667e29][email-masked]#0.0.0.1+0x1fd stack: 0x49e580
2018-02-03T22:43:50.423Z cpu8:66965)0x43916ca9bb00:[0x41801068908a][email-masked]#0.0.0.1+0x416 stack: 0xd
2018-02-03T22:43:50.424Z cpu8:66965)0x43916ca9bdf0:[0x418010689ab1][email-masked]#0.0.0.1+0x715 stack: 0x200000000
2018-02-03T22:43:50.424Z cpu8:66965)0x43916ca9bed0:[0x41801025def2][email-masked]#0.0.0.1+0x51a stack: 0x430c0e96f4e8
2018-02-03T22:43:50.424Z cpu8:66965)0x43916ca9bf90:[0x41800f308bbf]vmkWorldFunc@vmkernel#nover+0x4f stack: 0x41800f308bba
2018-02-03T22:43:50.425Z cpu8:66965)0x43916ca9bfe0:[0x41800f4c93c5]CpuSched_StartWorld@vmkernel#nover+0x99 stack: 0x0
2018-02-03T22:43:50.427Z cpu8:66965)base fs=0x0 gs=0x418042000000 Kgs=0x0
2018-02-03T22:43:50.427Z cpu8:66965)2 other PCPUs are in panic.

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

Cause

This issue occurs if the unicast agent configuration of a node is added to its own unicast agent list.

Resolution

This issue is resolved in vSAN 6.6.1 U2.

Workaround

To workaround this issue, perform the steps below:

List the unicast agents with the command:

esxcli vsan cluster unicastagent list

Note: This should give the list of the neighbor nodes as well as the local node, in case you find local node details, please remove the node from the unicastagent list.

esxcli vsan cluster unicastagent remove -a xx.xx.xx.xx -u host uuid.

Note: Once the workaround is applied, make sure you never add the unicast info of the local node to its own unicast agent list.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.6.x

VMware vSAN 6.5.x

VMware vSAN 6.2.x

VMware vSAN 6.1.x

VMware vSAN 6.0.x

Take Our Survey

Support Assistant