Fixing ESXi 6.5 On HPE G7 Servers4 min read

HP, you motherfuckers.

So there I was, moving VMs off of my main host (DL380 G7, 2x x5690’s, 192GB RDIMM), getting ready to replace the 8x 300GB RAID10 array I’ve been using for a while now with some 1TB disks and SSDs, awesome, right?

So the host was powered down, ready for an upgrade, and being the logical guy I am I decided to do some software upgrades.

I used the latest SPP and ran that through, for some reason I was using a BIOS from 2010? Once that was done I had updated firmware, so I moved onto ESXi. I’ve been running 6.0.0U2 for the longest time and thought this would be the ideal time to upgrade.

I got the HPE official ISO, ran through the upgrade, waited for it to boot annnddd….

PSOD.

After some digging, it would appear this is actually a known issue with most G7 servers (unsure about G6).

The issue.

It would appear that one driver is causing this in the 6.5 image,  “hpe-smx-provider” (650.03.11.00.17-4240417). Installing the standard ESXI 6.5 ISO does allow the server to boot, but is missing a lot of drivers and does not give the pretty all-inclusive system stats that the HPE ISO does.

So what now? I didn’t want to settle for the standard image, so I did the following to bundle the U2 hpe-smx-provider into the 6.5 image.

For the lazy: There is a link at the end of this post with a download to the compiled ISO.

Using PowerCLI Image Builder.

The first thing you want to do is download PowerCLI for Windows.

Once that is all installed, grab both of the following files and put it somewhere easy, I just shoved them in C:\HPE.
VMware-ESXi-6.5.0-OS-Release-4564106-HPE-650.9.6.0.28-Nov2016-depot.zip
VMware-ESXi-6.0.0-Update2-3620759-HPE-600.9.6.5.7-Dec2016-depot.zip

I also renamed them to make it easier for myself, “ESXIHP65” “ESXIHP6U2”.

Once that is done, fire up PowerCLI, and do the following commands:

  1. Add the 6.5 image bundle
    Add-EsxSoftwareDepot -DepotUrl C:\HPE\ESXIHP65.zip
  2. Check the profile was added.
    Get-EsxImageProfile
  3. Clone the profile so we can work on the clone.
    New-EsxImageProfile -CloneProfile HPE-ESXi-6.5.0-OS-Release-6* -Name "ESXICUST"
    Set Vendor to whatever, I used ‘Custom’.
  4. Check the profile was added.
    Get-EsxImageProfile
  5. Remove the driver from the clone.
    Remove-EsxSoftwarePackage ESXICUST hpe-smx-provider
  6. Add the 6.0U2 image bundle
    Add-EsxSoftwareDepot -DepotUrl C:\HPE\ESXIHP6U2.zip
  7. Check the profile was added.
    Get-EsxImageProfile
  8.  Now we can see both driver versions from the bundles.
    Get-EsxSoftwarePackage | findstr smx
  9. Add the good driver into the custom image.
    add-esxsoftwarepackage -imageprofile ESXICUST -softwarepackage "hpe-smx-provider 600.03.11.00.9-2768847"
  10. Export your custom bundle to ISO.
    Export-EsxImageProfile -ImageProfile ESXICUST -ExportToIso -filepath "c:\HPE\ESXI65CUST.iso"
    You should now have ‘ESXI65CUST.iso’ in your working folder.

Result.

So, once that’s all done mount the ISO however you like, I use iLO and go through the install as per normal, continue through the warning about CPUs of this socket being depreciated. And, eventually….

BOOM.

Post edit: You must do a clean install for this to work, upgrading will not work as the offending driver will not be overwritten. 

If you’re lazy and trust me enough then here is a link to the compiled ISO, ready to be installed.
The user ‘DA1’ linked a compiled 6.7 patched image below in the comments, ISO is here.

I hope this helped some of you out, best of luck! MM~~

172 thoughts on “Fixing ESXi 6.5 On HPE G7 Servers4 min read

  1. Hello, Great post btw! I am having the same issue with my dl380’s. So I have 6U2 and 6.5 HPE images. Did you just extract the iso and save as zip? I’m stuck on step one. I extracted the iso saved contents as zipped ran powercli with same commands and the index.xml file cannot be found. Any help is appreciated!

    • So the files your looking for are actually the offline bundles for running on the host, not the ISO. These can be acquired on the internet if you search for the packages. They are also on the /r/homeab FTP, you can find that on the Homelab wiki…

  2. I think the main problem here is that even everything is working correct this server isn’t supported for 6.5 by VMware neither by HP. So for homelab or labs this is totally fine but when running this server in production and you have further problems, you would be out of luck when opening a support ticket.

    http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=server&productid=12845&deviceCategory=server&details=1&keyword=%22dl380%20g7%22&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc

    http://h17007.www1.hpe.com/us/en/enterprise/servers/supportmatrix/vmware.aspx#.WK6jFxLsLxg

    • Indeed, however even though it’s officially unsupported it kind of sucks that HP either didn’t bother checking before release or checked and didn’t care. I still see plenty of G7’s in the wild and considering you have to pay for even software updates one would think they would repay that with at least checking their updates…

      HP have now released a patch for this now, only a week or so after I posted this so all is well again :). I am getting a lot of questions about this and I can’t seem to find it now… If I do I will make sure to update this post.

        • So I did a complete reinstall to SD card as I had to replace it. Everything went well with the custom ISO but VC is not showing sensor data. I have removed host from VC and reset entire network to reconfigure it again then added it back. Any thoughts?

          • Also it is the Web Client that I am referring to as fat client is no more. I did run it and connect to the host though to see the hardware data. Just need Web Client working. 馃檪

  3. Hi.I have faced the same trouble too.I have tried your guide step by step,but it still does no work. (I used upgrade way,not reinstall way) So I’m interested about your firmware version.I used HP SPP released at 2016.10 to updated my DL380 G7 server.My BIOS is using ver 2015,P410i firmware is ver 6.64,and ILO ver 1.88.How about yours?Thanks.

  4. So when attempting to clone the profile I am getting an error that some of the VIBs failed to validate. Any Ideas on this?

      • It was apparently the version of PowerCLI I was using. That being said after rebuilding the image I am still getting the PSOD. I am going to try a full install instead of an upgrade and see hwo that goes. THanks again.

        • You need to full install, an upgrade will not override the offending driver, I’m going to add that into the post now.

          Let me know how it goes!

          • Still no go. I had tried adding some other drivers from newer HPEUTils release so one of these may still be causing it. This is really frustrating that HPE won’t release a fixed image. Next round of servers we buy I will vote with my pocket book.

          • Well I got it now. Initially I was trying to slip in some of the latest HP Updates and do this at the same time. I think my script was overwriting something when I did it. Here is a quick script to do it all.

            Get-EsxSoftwareDepot | remove-esxsoftwaredepot

            $HPImage = “A:\ESXi_ISOs\ESXI_HP6-5_2.zip”
            $BaseHPImage = “A:\ESXi_ISOs\ESXI_HP6-5_Cloned.zip”
            $NewDriverDepot1 = “A:\ESXi_ISOs\ESXi_HP6-0.zip”
            $NewDriverDepot2 = “A:\ESXi_ISOs\HPEUtils.zip”
            $FixedBaseHPImageIso = “A:\ESXi_ISOs\HPE_ESXi_6-5_Final_04272017.iso”
            $BadBaseImage = “A:\ESXi_ISOs\ESXI_HP6-5_2.zip”
            ###Make a clone of the HP Images
            Add-EsxSoftwareDepot $HPImage
            $BaseHPImageName = Get-EsxImageProfile
            New-EsxImageProfile -CloneProfile $BaseHPImageName -Name $BaseHPImage -Vendor HPCustom
            $BaseHPImageName = Get-EsxImageProfile -Vendor HPCustom
            Export-EsxImageProfile -ImageProfile $BaseHPImageName -ExportTobundle -Force -FilePath $BaseHPImage
            #Add HP custom Image
            Get-EsxSoftwareDepot | remove-esxsoftwaredepot
            Add-EsxSoftwareDepot $BaseHPimage
            Get-EsxSoftwarePackage -Name hpe-smx-provider
            $BaseHPImageName = Get-EsxImageProfile
            Remove-EsxSoftwarePackage -ImageProfile $BaseHPImageName -SoftwarePackage hpe-smx-provider
            Export-EsxImageProfile -ImageProfile $BaseHPImageName -ExportTobundle -Force -FilePath $BaseHPImage
            Get-EsxSoftwareDepot | remove-esxsoftwaredepot
            Add-EsxSoftwareDepot $BaseHPImage
            Get-EsxSoftwarePackage -Name hpe-smx-provider
            ####HOpefully the above get command is empty.
            Add-EsxSoftwareDepot $NewDriverDepot1
            Get-EsxSoftwarePackage -Name hpe-smx-provider
            ####HOpefully you just found my driver levi….
            Add-EsxSoftwarePackage -ImageProfile $BaseHPImageName -SoftwarePackage hpe-smx-provider
            Export-EsxImageProfile -ImageProfile $BaseHPImageName -ExportTobundle -Force -FilePath $BaseHPImage
            Get-EsxSoftwareDepot | remove-esxsoftwaredepot
            Add-EsxSoftwareDepot $BaseHPImage
            Get-EsxSoftwarePackage -Name hpe-smx-provider
            Get-EsxImageProfile | Export-EsxImageProfile -ExportToIso -Force -FilePath $FixedBaseHPImageIso

  5. Hi,

    Using VMware Update Manager, I tried to upgrade HP ProLiant BL460c G7 ESXi from 6.0 to 6.5 using HP image, but it failed with PSOD.

    Then I performed fresh installation using same HP image and PSOD encountered again. Then I tried fresh installation using VMware standard image and it worked fine.

    I’ve noticed you mentioned standard image would be missing a lot of drivers. Is there any drawback using standard VMware image? If we must use HP image then we must follow the above process?

    Please suggest.

    Kind regards,

    Mobin

  6. Hey Muff. I just used the standard ISO from the VMWare site. What should I do to run the HPE image? Everything works (seemingly) at the moment so I’m not sure what to do!

    • So, there isn’t a real issue with running the base image however you will be missing some system stats, monitoring and drivers that are baked in.

      I pretty much need these things, and whilst you can add them into the stock image with VIBs it is a lot easier just to use the HP image with everything baked in, things like iLO management and RAID management from the ESX CLI can all be done with the HP image. If you also look at the hardware view of the host you will get a *much* better view with the HP image.

      To use the latest HP image on your G7 host just do the above.

      Cheers, MM

      • So, I tried it, followed the guide and ran the ISO, started the upgrade and got a random directory is not empty error at about 19% and then it stopped… Rebooted the box and ESXi failed to boot, ended up having to restore from a backup before the upgrade. I think I’ll stick with dodgy sensors I think!

          • My bad I missed that huge lettering! Do you just suggest to re-register the VMs or is there a better way to do it from a fresh install?

          • It’s all good.

            So I normally vMotion VMs somewhere else but if that isn’t an option for you then just shut them down, do the clean install and readd them from the datastore once you’re back up and running.

            Should be pretty painless unless you have loads of VMs.

            If you ensure you setup networking with the same names as before the VMs should just import and start without issue.

            MM~~

  7. Great work! As i am totaly noob to VMs and VMware in general but recived an outsorted ML110 G7 to begin learn this stuff at home, i like to ask: is there a posibility that you share your custom made image with us? Kind regards, Adam

  8. hi,

    thx for this documentation. On current HPE image I also need to disable hpe-cru after downgrade the smx.
    This was on dl385G7

  9. Hi MM

    HPE released a new image recently:

    VMware-ESXi-6.5.0-OS-Release-5146846-HPE-650.9.6.5.27-May2017.iso

    Does that fix the problem? If YES, does it fix it

    – for UPDATE
    – only for FRESH INSTALL

    If you look at HPEs “content of the image”
    http://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay/?docId=c04430318

    You see the following…

    6.5 May 2017 vSphere 6.5 Build 5146846

    hpe-build – 650.9.6.5.27-4240417
    hpe-cru 650.6.5.8.24-1.4240417
    hpe-ilo 650.10.0.2-2.4240417
    hpe-smx-provider 650.03.11.00.17-4240417
    hpe-esxi-fc-enablement 650.2.6.10-4240417
    amshelper- 650.10.6.0-24.4240417

    So is this image GOOD ?

    Did you test it?

    Any feedback would be appreciated 馃檪

    Regards,
    Oliver

  10. hi
    i test this image: VMware-ESXi-6.5.0-OS-Release-5146846-HPE-650.9.6.5.27-May2017.iso directly from hp with NO PATCH, and it’s NOT WORK :(.

    please would you like to update your iso file in the first page?

    many thanks….

  11. I try the new ISO with the described workaround and it works on a DL385 G7. But under the monitoring of the storage thjere seems to be an issue. There are no metrics available and I see just this text: “The Small Footprint CIM Broker Daemon (SFCBD) is running, but no data has been reported. You may need to install a CIM provider for your storage adapter.”

    Any idea?

    • I too am working on this issue. Does anyone know if this is caused by the smx driver (hpe-smx-provider–600.03.11.00.9-2768847–HPE–VMwareAccepted–2016-01-22) replacing hpe-smx-provider–650.03.11.00.17-4240417–HPE–VMwareAccepted–2017-11-15? I’m working on a comparison of all VIBs but its hard to tell what VIB provides what functionality.

  12. I麓ve tried it with a DL360 G7 – new install. It fixed the purble screen issue – but I wasn麓t able to get it work. I had problems with the esxi web GUI – I wasn麓t able to configure a network to my vm麓s … And I麓ve got many display problems and it was extremly slow so I decided to install the 6.5 from vm ware again. I really hope, that HP will get it work soon. It makes no fun …

  13. Albeit I’m very clear on how to get iso images on to usb thumb drives, and other isos work perfectly for installing, I’m failing with the supplied MUFFINS6.5FIX.iso

    Has anyone gotten a DL380 to boot off of MUFFINS6.5FIX.iso and if so, what’s your RC5 checksum?

    Thanks

      • I was unable to boot with any USB device connected, PSODs on VMKUSB — I have read that 6.5 added/replaced the USB drivers with this new module (however removing it doesnt help). If I boot the installer fully, with all USB removed (so yea, have to iLo, PXE, or burn a CD..yuck) then plug in my target USB stick I’m able to install no problem

    • I would try the generic VMware update and not the HPE one as the VMware ISO wont have any HP specific drivers. VUM should also run a check on compatibiliy issues first. But no guarantees on the outcome 馃槈

  14. I have 6.5 installed on a ML350 G6 succesfully using the generic VMware ISO, so no HP drivers installed. Now I’m obviously missing out on hardware monitoring. What would happen if I install th hpe-smx-provider-600.03.11.00.9-2768847.vib on my ML? I’m a bit hessitant because I’m not a great fan of PSOD’s 馃槈

  15. Hi MM,

    Do you have updated .iso with release 7388607?
    This is the last ESXi issued from VMware which I have.
    Unfortunately suffers same illness as the previous image but I do not have those vib file “hpe-smx-provider”.
    Also do you have by any chance 1.89 BIOS for DL360G7?

    Regards,
    MSM

  16. I am looking for a version without the spectre/meltdown patches, for example 6765664 from november 2017. I don’t want to cap this system.

  17. I used this on a fresh install and it worked great. I am curious. Can I use this to upgrade from 5.5 to 6.5 or would I need to perform a clean install? I have a few G7s. Here we are nearly a year later and the latest custom ISO doesn’t seem to work.

  18. Hello!
    I want to make a fresh build based on the latest releases
    VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-Depot
    and
    VMware-ESXi-6.5.0-Update2-8294253-HPE-Gen9plus-650.U2.10.2.0.14-May2018-Depot

    moved smx-provider,
    added drivers
    QLG-NetXtremeII-5.0-offline_bundle-4362634 and scsi-hpsa_6.0.0.124-1OEM.600.0.0.2494585

    What else should I add or remove drivers to get a full build?

    Thank you!

    • We use QLogic 10GB SFP adapters NC523SFP 2 Port 10GB adapters. I have been installing this after running your ISO.

  19. Hi- This has been working well. I just updated a few G7s to 6.5 U2. It seems that this may have broken the health sensors. Whenever vCenter updates the hosts hardware information (seems to run a few times a day), I see an invalid fault in the logs for the hosts I’ve updated. I have to assume it’s something with a VIB the G7s are using. Any insight?

      • Well, I have an ML350G6 with ILO2, and I can guarantee you that upgrading from i.e. 5.5 or 6.0 to 6.5 using the HP ISO will lead to many, many hours of recovery fun!

  20. Hi Guys – I have a HP DL380 G6 and concur that an unmodified HP 6.5 image doesnt work and recovering isn’t fun.

    Does anyone know if i inject hpe-smx-provider 600.03.11.00.9-2768847 driver into a HP ESXi 6.7 image will work?

    Thanks in advance.

    • I haven’t tried it since I didn’t get the 2nd gen7 server but I was able to boot the installer so no CPU incompatibility issues. In theory it should work but I would suggest someone tests it.

  21. Got the DL580 G7 running on esxi 6.7 from VMware-ESXi-6.7.0-8169922-HPE-Gen9plus-670.10.3.0.30-Jun2018-depot.zip with hpe-smx-provider injected from VMware-ESXi-6.0.0-Update3-7967664-HPE-preGen9-600.9.8.0.7-Jun2018-depot.zip. So far works OK.

  22. Thanks Muffin. We upgraded our SQL Servers to a DL380 G10 and I wanted to repurpose the DL380 G7 as an Application Server Host. Some of the Application Virtual Machines are used for production applications, but I find once you figure out how to work around HP’s failures – in this case, the wonky driver – and VMWare issues, everything usually runs tickety-boo from then on. Right now many of these Application Virtual Machines are running on a DL365 G1 with ESXi 5.1, but it’s getting a little long in the tooth now (just like me), and performance can be a bit slooowww.

    I arrived at this site after I tried installing the standard ESXi HP OEM PreGen9 ISO on our G7, and fairly quickly got a PSOD on the console although I could still communicate with ESXi and operated it, but PSODs usually suggest some instability.

    I tried the Lazy technique of using Muffin’s ISO next and it seemed stable but I couldn’t get a networking connection. I’d connected both NICs of the G7 using Link Aggregation to two ports on the local switch and figured that something in Muffin’s ISO had a networking issue, perhaps because it was an older version of 6.5.0 than is currently available to me.

    Seeing as how networking had worked on my original 6.5.0 ISO, and Muffin’s ISO was otherwise stable on my G7, my third try was to follow Muffin’s incredibly well documented instructions with the latest 6.5.0 HP OEM PreGen9 ISO and the SMX-Provider from the latest 6.0.0 HP OEM ISO and build a custom ISO that I loaded onto a thumb drive, installed freshly onto the SD card of the G7 and now it’s been running great for a few days.

    The G7 is still under warranty with HP so it’s very annoying that they don’t directly support this when it’s so simple to make it work, and judging by the number of people who have made it work with Muffin’s and others’ instructions it’s viable software.

    Thank you Muffin for such wonderful, easy-to-follow instructions.

  23. On my home server DL ProLiant DL380 G7 (2 x Intel(R) Xeon(R) CPU E5649 / 120 GB RAM) I’ve just upgraded the HPE ESXi 6.0 U3 with VMware-ESXi-6.7.0-8169922-HPE-Gen9plus-670.10.3.0.30-Jun2018 (and applied also the latest ESXi patch ESXi670-201808001 – build 9484548).
    After the upgrade, the system was stable from the beginning, after patching, the same.
    The mention is that the ESXi 6.7 was automatically upgraded with smx-limited version 600.03.14.00.3-2768847.
    I’ve tried to install the esxi6.7uX-mgmt-bundle-3.3.0-10.zip but this over-written the smx-limited version with smx-provider-670.03.14.00.2-7535516, which hanged the OS after reboot.
    I’ve Rolled-Back the ESXi and installed only the ams-esxi6.7-bundle-11.3.0-5, which updated the smx-limited to 670.03.14.00.3-7535516, but with the same result, ESXi server is unavailable for management
    After roll-back, the system is working properly only with smx-limited version 600.03.14.00.3-2768847.

  24. HP DL380 G7 with SSD’s on P410i – performance isnt what I expect ~1000 random IOPs. 6.5u1 ESXi, (Build 7967591). I see nhpsa driver … any suggestions?

  25. yes, strange, I tried all kind of images…even my old consumer core 2 pc can boot vm 6.5
    have you done any bios adjustments?

  26. Has anyone gotten the latest G7 BIOS to install on ESXi? The VMEXE was written for 5.1-6.0. But there’s got to be a way to change this somewhere.

  27. Hi, I have a conflict on HP ProLiant DL380 G7 on vib ehci-ehci-hcd version 1.0-4vmw.600.3.69.5572656.

    What’s the solution ?

    Thanks,
    Almeyric

  28. Thanks Muffin. Your ISO of v6.5 works for mine on Blade BL490c G7.
    I am going to test it another round with Blade BL460c-G6.

  29. When I Use the HPE Image “VMware-ESXi-6.5.0-Update2-9298722-HPE-preGen9-650.U2.9.6.8.3-Sep2018.iso” on an ML350 G6 with actual BIOS I get no PSOD but the system will not connect with vCenter and after a few minutes every halt, machines can not be startet….
    I try the same on two DL 380 G6 and work fine.
    Has anyone else this problem ?

    When I try with the MUFFINS6.5FIX.iso i get the update conflict problem with the vib ehci-ehci-hcd version 1.0-4vmw.600.3.69.5572656

  30. I followed everything to a T for a 6.0 to 6.5 upgrade.
    Works on my HP Proliant ML350 G6, with the exception that I can’t see the storage related components in the monitoring.

    I suppose this is due to the driver for the P410 add-in card. For 6.0 to work, I had to actually use the 5.5 hspa vib, else storage had kept dropping out (and this was with the HPE ISO) after about 14-20 days or so. Not sure if this will work on 6.5..may try it, may try the 6.7 iso linked next week if this stays stable…

    Here is the 5.5 driver vib:

    cd /tmp
    wget http://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p964549618/v97400/scsi-hpsa-5.5.0.60-1OEM.550.0.0.1331820.x86_64.vib
    esxcli software vib install -v /tmp/scsi-hpsa-5.5.0.60-1OEM.550.0.0.1331820.x86_64.vib

    If anyone has thoughts on how to bring back storage monitoring, I’m all ears! Hoping to get 6.5 or 6.7 nice and stable on my old gal to buy it another year before I’m really forced to upgrade.

  31. Hey Muffin Lovers,

    So I’ve got a beloved (yes, believe it) Flea Market find in a DL360 G7 – $30 for just the chassis, 2 power supplies, random ram which I tossed and scrounged around for new stuff (60GB), but all in all super good condition. Some compressed air, alot of iso 95% and tender love – and she’s been running rock solid for 3 months now, powering my evil learning ways.

    I ‘found’ updates for the BIOS/UEFI, and got her patched up to the latest 2018/11 (I think), along with a nice entitlement for the old iLO2. She’s a damned workhorse, and I’m proud of her.

    But: does running a customized ESXi 6.7 image give me significant benefit?

    First, let me show you how she blows away a similar-classed IBM xSeries (as in ‘x-files’, because it’s alien how this sucks so bad).

    https://imgur.com/uxn5aFU

    The Proliant was doing 4 simultaneous installs of VM’s (2×2016, 2xWin10) during the heavy copying phase in that diagram. Just before (in the left) she was allowing a Win2016 host to copy a large file to USB 3.0 passthrough. First, I don’t know if 50MB sustained is good for the config (it’s noted in the graphic), but it’s what I have, and I’m satisfied right now because #iHaveALabAndManyPeopleDont

    Being analytical, of course, I figure: those systems are all 3.0Gbps SATA at the core, which should offer some HUNDREDS of megabytes per scond transfer, if my maths haven’t failed me. Of course, that’s in theory, and practice means accounting for every aspect: card (SmartArray) [including cache], card firmware (BIOS), drives [doh!], drive firmware, logical setup of the RAID, and then hypervisor driver architecture.

    This is what brought me here.

    Bottom line question: what does (aside from pretty views in the Monitor/Manager section of a standalone ESXi host portal) the customization solution of having a tuned ESXi build for the 360 offer? I know that because HP creates a special driver for the 410 SmartArray in my 360 g7, and VMWare certifies it – this is preferred. But is it preferred because of stability or performance? Or both?

    Are there real world, quantifiable before/after testings I can refer to? I truly want to get my 360 up to a better level, but it already kicks ass and I don’t think I’m going to be upgrading the SmartArray any time soon. Of course, I would definitely put some pro level/enterprise-class SSD’s in there soon, and perhaps optimize the layout, etc.

    The IBM will continue to suck eternally, and I’m not sure if they offer a customized version of ESXi anyhow.

    Thanks all for being patient and wading through my rant.

    Cheers.

  32. Got given 2 old n40l 2gram 250g hdd and a bios update and your muffin iso has given me hours of homelab and esxi experience…thank you so much 馃檪 to everyone here

  33. Have a project going on. One fresh N54L setup hopefully with 6.7U2. Will have to wrap my head around making a customU2. Was hoping on the one that was mentioned in the comments. Have send email and waiting for a reply. Unless somebody else has a customU2…

  34. I just applied the latest updates to my DL 360 G7s running the 6.5 custom image. I am now seeing a “System Board 7 Memory” error under CIM data. The host version is now VMware ESXi, 6.5.0, 13932383.

  35. soo cool… I’ve just bought a Gen7 HP server with dual opteron, called HP SL165z G7, with 192 GB RAM lemme see if the ESX 6.5 or 6.7 image is going to work with that 馃檪

  36. How does the stability of 6.7 compare to 6.0 on a DL380G7? Any known issues? I use PCI pass-through (for an actual video card for a workstation VM).

  37. Got the 6.7 image installed on my DL380 G7, working well so far. The only issue I had was having to remove and re-add my PCI passthrough devices.

    Under Monitor – Hardware – Storage, I see a number of devices with “Cannot report on the current status of the physical element”. Is there a fix for this? It seems to monitor most of the important stuff.

  38. I’ve tried to mimic all the same versions in the working 6.7 image for the HPE, Microsemi and MSCC packages on a custom build of HPE 6.7U3 using this guide/PowerCLI, it boots and versions are what I want them to be, but with no fix for the dodgy CIM results with 6.7U3 on at least my DL360 G7 (ilo3 1.91, SPP G7.1-3).

    I noticed while experimenting with this that there are additional “lsu-xyz” packages in 6.7U3, not present in 6.7, provided by VMware – lsu-smartpqi-plugin is new, and there was already “smartpqi” by vendor HPE… Those are storage related, maybe removing them or downgrading some others is worth a go next but I’ve run out of time tonight.

    (info dump begin)
    For the record and if anyone else wants to pick up where I’ve left off for now:

    Tried 6.7U3 HPE, removed “smx-provider” and added/replace all other packages with following:
    amsd 670.11.3.5-6.7535516
    bootcfg 6.7.0.02-05.00.4.7535516
    conrep 6.7.0.03-02.00.1.7535516
    cru 670.6.7.10.14-1OEM.670.0.0.7535516
    fc-enablement 670.3.20.12-7535516
    hpe-smx-provider 600.03.11.00.9-2768847
    hponcfg 6.7.0.5.3-0.2.7535516
    ilo 670.10.1.0.16-1OEM.670.0.0.7535516
    oem-build 670.10.3.5-7535516
    scsi-hpdsa 5.5.0.60-1OEM.550.0.0.1331820
    ssacli 3.30.14.0-6.7.0.7535516
    testevent 6.7.0.02-00.01.12.7535516
    nhpsa 2.0.30-1OEM.670.0.0.7535516
    smartpqi 1.0.2.1038-1OEM.670.0.0.8169922

    No change, CIM information still broke. Other differences I’ve spotted with “lsu-” packages:

    6.7 HPE has:
    lsu-hp-hpsa-plugin 2.0.0-14vmw.670.0.0.14539518
    lsu-lsi-lsi-mr3-plugin 1.0.0-12vmw.670.0.0.8169922
    lsu-lsi-lsi-msgpt3-plugin 1.0.0-8vmw.670.0.0.8169922
    lsu-lsi-megaraid-sas-plugin 1.0.0-9vmw.670.0.0.8169922
    lsu-lsi-mpt2sas-plugin 2.0.0-7vmw.670.0.0.8169922

    6.7U3 HPE has:
    lsu-hp-hpsa-plugin 2.0.0-16vmw.670.1.28.10302608
    lsu-intel-vmd-plugin 1.0.0-2vmw.670.1.28.10302608
    lsu-lsi-drivers-plugin 1.0.0-1vmw.670.2.48.13006603
    lsu-lsi-lsi-mr3-plugin 1.0.0-13vmw.670.1.28.10302608
    lsu-lsi-lsi-msgpt3-plugin 1.0.0-9vmw.670.2.48.13006603
    lsu-lsi-megaraid-sas-plugin 1.0.0-9vmw.670.0.0.8169922
    lsu-lsi-mpt2sas-plugin 2.0.0-7vmw.670.0.0.8169922
    lsu-smartpqi-plugin 1.0.0-3vmw.670.1.28.10302608

    Starting to think this may be a wild goose chase…

      • Had another go doing the next obvious choice – remove all the new 6.7U3 lsu-* packages, and replace upgraded ones with previous versions… no difference!

        Next I’ll try the same with these-

        6.7 HPE (working):
        ipmi-ipmi-devintf ipmi driver 39.1-4vmw.670.0.0.8169922
        ipmi-ipmi-msghandler ipmi driver 39.1-4vmw.670.0.0.8169922
        ipmi-ipmi-si-drv ipmi driver 39.1-4vmw.670.0.0.8169922

        6.7U3 HPE (not working):
        ipmi-ipmi-devintf ipmi driver 39.1-5vmw.670.1.28.10302608
        ipmi-ipmi-msghandler ipmi driver 39.1-5vmw.670.1.28.10302608
        ipmi-ipmi-si-drv ipmi driver 39.1-5vmw.670.1.28.10302608

        CIM relies on IPMI and builds on it, from the 30 seconds of searching I just did. Therefore if they’ve changed something there, perhaps?

        • Nope no good with all those packages swapped out, it still boots and runs but all the health information is borked.
          For now I’m going back to plain 6.7, swapping smx-provider for the 6.0 latest release of hpe-smx-provider, I think that is the latest version we can get working nicely at the moment unless a ESXi guy can dig into this a bit.

          On a side note – generally, which is considered “better”: 6.5 U3 (if it works) or plain 6.7? What does 6.7 bring to the table – features we can honestly make use of on a HP G7-era server, in a homelab (as in, no vSphere)? Having more support lifetime is useless here.

          The only noticeable difference I’ve seen between plain 6.7 and 6.7U3 is Windows Server 2019 is “recognised”, but I dont think that matters, I was running 6.5 U-something with Server 2019 on a Server 2016 ESXi profile on this HP G7, and it didnt seem to matter.
          Otherwise, to me basic ESXi seems nearly the same as it has been since 6.0, except some WebUI improvements, again we don’t get much out of that going forward without a vSphere environment to use HTML5.

  39. First of all, thank you so much. This should be done by the HP motherfuckers, but they don’t care with “old” expensive hardware.

    I have a C7000 with BL460c blades. I installed the 6.5 standard version and everything went fine, but i miss some HBA and 10GBe Network on ESXI.

    So i try to install all the custom HPE versions, but all end with this error. I made the custom build for 6.5 U3, removing the smx driver and add the previous one from 6.0.

    Everything works like a charm, the host boots with no problem. I was happy but then …

    When i restart the host, i got another purple screen, this time for HPE-NMI driver … And this one is really hard to solve. The 6.0 HPE version has the same driver version, so i cant do the same process l did on smx driver issue.

    The 6.7 doesnt have any HPE-NMI driver, so i’m really stuck on this, and i can’t have the servers with purple screens everytime i need to reboot.

    Do you have any idea of how to solve this ??

    Thank you so much

  40. Has anyone else noticed that using 6.5 or 6.7 breaks the power management policy? As in, ESXI doesn’t put the CPU in the correct C-State when it’s idling.

    You will notice via iLO that when the G7 is idling, it’s still pulling quite a bit of power, and the fans running faster.

    Example. I’m using 6.0 U3, Fans run at 13% and idles at 104 Watts. Using 6.5 or 6.7 makes 3 of the fans run at 23-25% and idles at 140 Watts.

  41. Thanks MM, took me over couple days until I found your solution, and it’s working fine. Just wondering if your G7 take over 2- 3 mins to boot up each time? compare to G5 it’s take a less than a mins to boot up.

  42. I havent tested with 6.0 but my DL 380 G7 is also running quite noisy and consumes about 150-180W in more or less idle state. This is a bit more than all benchmarks would suggest so there might be indeed an issue with the power management. Nt sure how to look further into this.

  43. Google drive tells me, that you trashed the 6.5 … could you please undo this? … — I would really like to test it on my g7 … Thanks in advance!

  44. Andy body had Andy luck with ESXi 7 and gen7?
    I would be super happy if some one could share a a working iso.

  45. Yes, I鈥檝e seen that. I was hoping someone have put together a gen7 friendly version With other fixes to (if there is any).

    I have one more question, I鈥檓 running ESXi from a USB memory, can the installation 鈥渟e鈥 that usb if I run the upgrade/installation from another usb?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: