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

Hostd process crashes repeatedly on ESXi host with virtual distributed switch (55845)

Last Updated: 6/11/2018Categories: TroubleshootingTotal Views: 8309Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When all virtual distributed switch (vDS) on the vCenter server is connected to 4 or more physical NICs.

Signal 11 or signal 6 errors are displayed.

hostd process crashes repeatedly.

In the hostd.log, you see entries similar to:

YYYY-MM-DDTHH:MM:SS.SSSZ info hostd[FFE16A80] [Originator@6876 sub=Default] hostd-118622-3073146.txt time=YYYY-MM-DD HH:MM:SS.000
--> Crash Report build=3073146
--> Signal 11 received, si_code 1, si_errno 0
-->    Bad access at 0
--> eip 0x758b915 esp 0x7e17fe7c ebp 0x7e1800a8
--> eax 0x0 ebx 0x7598d48 ecx 0x7598d48 edx 0x0 esi 0x7da25f64 edi 0x7e1801cc
--> stack 7E17FE7C : 0x0758dc3a 0x00000054 0x00000000 0x00000029
--> stack 7E17FE8C : 0x0000074f 0x7da5a370 0x7e1801cc 0x00000001
--> stack 7E17FE9C : 0x7dbbe854 0x00000000 0x7e18006c 0x00000000
--> stack 7E17FEAC : 0x00000001 0x7da00010 0x7da00010 0x7e17fee8
--> stack 7E17FEBC : 0x036cdad0 0x00000000 0x7e181b64 0x038f1e34
--> stack 7E17FECC : 0x00000004 0x036cda39 0x036c0976 0x7e17ff08
--> stack 7E17FEDC : 0x036cefa8 0x7e17fff8 0x075951fd 0x7e17ff08
--> stack 7E17FEEC : 0x08e54c4e 0x7dac9538 0x7e181b64 0x038efff4

In the vmkernel.log, you see entries similar to:

YYYY-MM-DDTHH:MM:SS.SSSZ cpu60:35233 opID=2a586eaa)User: 3816: wantCoreDump:hostd-worker signal:6 exitCode:0 coredump:enabled

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

Cause

This is caused when hotsd process fails to collect internal state.

Resolution

This issue is resolved in ESXi 6.0 and 5.5.

VMware ESXi 6.0 :

This issue is resolved in VMware ESXi 6.0 Update 1b, see VMware Downloads.

VMware ESXi 5.5 :

This issue is resolved in ESXi 550-201501401-BG, See VMware Downloads.

ESXi550-201501001 includes ESXi 550-201501401-BG. For more information, see the VMware ESXi 5.5, Patch Release ESXi550-201501001 (2099265).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant