{"id":1228,"date":"2015-04-30T10:30:07","date_gmt":"2015-04-30T17:30:07","guid":{"rendered":"http:\/\/jim-zimmerman.com\/?p=1228"},"modified":"2015-04-30T10:30:07","modified_gmt":"2015-04-30T17:30:07","slug":"vmware-esxi-and-hp-dl380-heap-issue","status":"publish","type":"post","link":"https:\/\/jim-zimmerman.com\/?p=1228","title":{"rendered":"VMWare ESXi and HP DL380 Heap issue."},"content":{"rendered":"<p>I was getting the following message when I would try to start up a VM on an HP DL380.  <\/p>\n<blockquote><p>Heap globalCartel-1 already at its maximum size of 7869288. Cannot expand. Could not start VMX: msg.vmk.status.VMK_NO_MEMORY<\/p><\/blockquote>\n<p>The machine had plenty of memory and seemed to operating fine for currently running VMs.  When I brought up the direct console on the machine, there was screen full of the following:<\/p>\n<blockquote><p>\/bin\/sh: can&#8217;t fork<\/p><\/blockquote>\n<p>I could not enter any commands other than &#8220;exit.&#8221;  I could log in and out, and that is about it.<\/p>\n<p>In VMWare KB article 2085618, it acknowledged the issue with the HP specific image and the HP AMS driver.<\/p>\n<p>Updated the HP AMS driver per VMWare KB article 2085618.<\/p>\n<p>To determine version running:<\/p>\n<blockquote><p>esxcli software vib list | grep ams<\/p><\/blockquote>\n<p>Old version:<\/p>\n<blockquote><p># esxcli software vib list | grep ams<br \/>\nhp-ams                         550.10.0.0-18.1198610                  Hewlett-Packard  PartnerSupported  2014-11-07  <\/p><\/blockquote>\n<p>Download updated driver from HP:<br \/>\n<a href=\"http:\/\/h20564.www2.hp.com\/hpsc\/swd\/public\/detail?swItemId=MTX_b05d4c644fb742aa87cb5f5da1\" target=\"_blank\">hp-ams-esxi5.5-bundle-10.0.1-2.zip<\/a><\/p>\n<p>Then, I used scp to copy the downloaded zip file to my ESXi 5.5 server.  I copied it to a hp-ams-esxi5.5-bundle-10.0.1.2 directory I created. Directory: \/vmfs\/volumes\/vmhost02-datastore1\/Software\/hp-ams-esxi5.5-bundle-10.0.1-2.  <\/p>\n<p>Login to the ESXi host using ssh.<\/p>\n<blockquote><p># cd \/vmfs\/volumes\/vmhost02-datastore1\/Software\/hp-ams-esxi5.5-bundle-10.0.1-2<\/p><\/blockquote>\n<p>Unzip the file:<\/p>\n<blockquote><p># unzip hp-ams-esxi5.5-bundle-10.0.1-2.zip<br \/>\nArchive:  hp-ams-esxi5.5-bundle-10.0.1-2.zip<br \/>\n  inflating: index.xml<br \/>\n  inflating: vendor-index.xml<br \/>\n  inflating: metadata-hp-ams-esxi5.5-bundle-10.0.1-2.zip<br \/>\n  inflating: hp-esxi-fc-enablement-550.2.1.8-1198610.vib<br \/>\n  inflating: hp-smx-limited-550.03.06.00.22-1198610.vib<br \/>\n  inflating: char-hpilo-550.9.0.2.3-1OEM.550.0.0.1198610.x86_64.vib<br \/>\n  inflating: char-hpcru-5.5.6.6-1OEM.550.0.0.1198610.x86_64.vib<br \/>\n  inflating: hp-ams-550.10.0.1-07.1198610.vib\n<\/p><\/blockquote>\n<p>Files contained in the zip:<\/p>\n<blockquote><p># ls -l<br \/>\ntotal 19456<br \/>\n-rw-r&#8211;r&#8211;    1 root     root         13590 Apr 29 12:15 char-hpcru-5.5.6.6-1OEM.550.0.0.1198610.x86_64.vib<br \/>\n-rw-r&#8211;r&#8211;    1 root     root         12676 Apr 29 12:15 char-hpilo-550.9.0.2.3-1OEM.550.0.0.1198610.x86_64.vib<br \/>\n-rw-r&#8211;r&#8211;    1 root     root       1271770 Apr 29 12:15 hp-ams-550.10.0.1-07.1198610.vib<br \/>\n-rw-r&#8211;r&#8211;    1 root     root       6829546 Apr 29 12:15 hp-ams-esxi5.5-bundle-10.0.1-2.zip<br \/>\n-rw-r&#8211;r&#8211;    1 root     root       1213780 Apr 29 12:15 hp-esxi-fc-enablement-550.2.1.8-1198610.vib<br \/>\n-rw-r&#8211;r&#8211;    1 root     root       4482274 Apr 29 12:15 hp-smx-limited-550.03.06.00.22-1198610.vib<br \/>\n-rw&#8212;&#8212;-    1 root     root           328 Apr 29 12:15 index.xml<br \/>\n-rw-r&#8211;r&#8211;    1 root     root          8531 Apr 29 12:15 metadata-hp-ams-esxi5.5-bundle-10.0.1-2.zip<br \/>\n-rw&#8212;&#8212;-    1 root     root           238 Apr 29 12:15 vendor-index.xml<\/p><\/blockquote>\n<p>Shutdown or migrate all the guests on the ESXi server, and then put the server in maintenance mode:<\/p>\n<blockquote><p># esxcli system maintenanceMode set &#8211;enable on<\/p><\/blockquote>\n<p>Update the software:<\/p>\n<blockquote><p># esxcli software vib update -v \/vmfs\/volumes\/542c3aae-03b91418-ff2a-a0d3c1f0cdf0\/Software\/hp-ams-esxi5.5-bundle-10.0.1-2\/hp<br \/>\n-ams-550.10.0.1-07.1198610.vib<br \/>\nInstallation Result<br \/>\n   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.<br \/>\n   Reboot Required: true<br \/>\n   VIBs Installed: Hewlett-Packard_bootbank_hp-ams_550.10.0.1-07.1198610<br \/>\n   VIBs Removed: Hewlett-Packard_bootbank_hp-ams_550.10.0.0-18.1198610<br \/>\n   VIBs Skipped: <\/p><\/blockquote>\n<p>At this point, you need to reboot the ESXi host.<\/p>\n<p>New version:<br \/>\n# esxcli software vib list | grep ams<br \/>\nhp-ams                         550.10.0.1-07.1198610                  Hewlett-Packard  PartnerSupported  2015-04-29  <\/p>\n<p>Take the server out of maintenance mode:<\/p>\n<blockquote><p># esxcli system maintenanceMode set &#8211;enable off<\/p><\/blockquote>\n<p>Migrate or startup guests back to the server.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I was getting the following message when I would try to start up a VM on an HP DL380. Heap globalCartel-1 already at its maximum size of 7869288. Cannot expand. Could not start VMX: msg.vmk.status.VMK_NO_MEMORY The machine had plenty of memory and seemed to operating fine for currently running VMs. When I brought up the [&#038;hellip<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[397,153,395,396,394,33],"class_list":["post-1228","post","type-post","status-publish","format-standard","hentry","category-documentation","tag-dl380","tag-esxi","tag-heap","tag-hp","tag-vmk_no_memory","tag-vmware"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1228","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1228"}],"version-history":[{"count":7,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1228\/revisions"}],"predecessor-version":[{"id":1237,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/1228\/revisions\/1237"}],"wp:attachment":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1228"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1228"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1228"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}