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

HPE HBA driver "smartpqi" reports "Out of memory" (67667)

Last Updated: 2/27/2024Categories: PatchTotal Views: 19011Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

In some HPE server, configured with the HPE Smart PQI controllers.

The driver "smartpqi" was used for this HBA / IO controller.

The ESXi host was non-responsive in the vCenter.

The host management agent "hostd" was non-responsive.

-- vmkernel.log
2019-03-28T12:15:01.414Z cpu42:2657267)ALERT: hostd detected to be non-responsive

* The HBA driver "smartpqi" was report " "Out of memory" in the log.
-- vmkernel.log
2019-03-28T06:25:22.704Z cpu58:875065)smartpqi: pqi_AllocDmaFromMemPool:92: vmk_MemPoolAlloc failed: Out of memory.
2019-03-28T06:25:22.704Z cpu58:875065)smartpqi: os_dma_mem_alloc:195: Failed to allocate dma mem from mem pool
2019-03-28T06:25:22.704Z cpu58:875065)smartpqi: pqisrc_passthru_ioctl:56: Failed to Allocate dma mem for Ioctl PassthruCmd Buffer : -1

Cause

The HBA driver "smartpqi" always requests the physical memory address below 4 GB range

This fails to get additional memory If there was no any DMA memory available in that range.

As lack of memory, the 3th utility "SSA CLI" will slowly get feedback from the HBA driver.

This will lead to host management agent "hostd" to turn non-responsive

Impact / Risks

The ESXi host will be un-responsive from the vCenter

Resolution

The latest driver "smartpqi" version "1.0.3", an enhancement was added to fix this issue.

It's release on Jan 2019.

Download VMware ESXi 6.5 smartpqi 1.0.3.2035 SAS Driver for HPE Smart PQI controllers

https://customerconnect.vmware.com/web/vmware/details?downloadGroup=DT-ESXI65-MICROSEMI-SMARTPQI-1032035&productId=614

In the release note snippet :
Fixes & Enhancements:
---------------------
* Added an enhancement to remove "Below 4 GB" DMA memory usage.
The driver always requests the physical memory address below 4 GB range and there might not be any DMA memory available in that range.

Note: As this enhancement,it's requested to use the 64-bit SSA CLI utility to work with the latest driver.

Workaround

Sometimes, the host will be resume by restarting the hostd.

# /etc/init.d/hostd restart

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
•
因 pod-startup.log 文件过多，导致 vCenter Appliance /storage/log 分区过满 (80803)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESXi

Related Versions:

VMware ESXi 6.7.x

VMware ESXi 6.5.x

Take Our Survey

Support Assistant