Hi sp4rt4n,
Is it still running stable after your changes?
Hi anyone else:)
I'm thinking about doing the same..Step 3 I mean:)
I've never used Image Builder but am curious to see with it what the steps are to remove something and add something else to it (am googling now for a tutorial)
EDIT 1:
I just did the same steps and for now, no more Pink Screen of love on my screen.
To make it easier for others also:
I made a custom ESX 6.5 image by using:
- HP ESXi 6.5 image as depot + cloned it via the image builder
- removed the hpe-smx-provider
- added the HP ESXi 6.0 U2 image as a depot
- added the hpe-smx-provider from it to the ESX 6.5 clone I made
- exported the clone as a new ISO
Instructions:
#add the offline bundle from 6.5
Add-EsxSoftwareDepot -DepotUrl C:\Tmp\VMware-ESXi-6.5.0-OS-Release-4564106-HPE-650.9.6.0.28-Nov2016-depot
.zip
#view and select an image profile
PowerCLI C:\tmp> Get-EsxImageProfile
Name Vendor Last Modified Acceptance Level
---- ------ ------------- ----------------
HPE-ESXi-6.5.0-OS-Release-6... Hewlett Pack... 11/18/2016 1... PartnerSupported
#clone it
New-EsxImageProfile -CloneProfile HPE-ESXi-6.5.0-OS-Release-6* -Name "ESX-6.5-old-driver"
PowerCLI C:\tmp> New-EsxImageProfile -CloneProfile HPE-ESXi-6.5.0-OS-Release-6* -Name "ESX-6.5-old-driver"
cmdlet New-EsxImageProfile at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
Vendor: Custom
Name Vendor Last Modified Acceptance Level
---- ------ ------------- ----------------
ESX-6.5-old-driver Custom 11/18/2016 1... PartnerSupported
#remove new hpe-smx-provider
Remove-EsxSoftwarePackage ESX-6.5-old-driver hpe-smx-provider
#add ESX 6.0 depot (offline bundle) - I renamed it as I was getting lazy to write those long names
PowerCLI C:\tmp> Add-EsxSoftwareDepot .\VMware-ESX6-depot.zip
Depot Url
---------
zip:C:\tmp\VMware-ESX6-depot.zip?index.xml
# we see both packages
PowerCLI C:\tmp> Get-EsxSoftwarePackage | findstr smx
hpe-smx-provider 600.03.11.00.9-2768847 HPE 4/15/2016 11:...
hpe-smx-provider 650.03.11.00.17-4240417 HPE 11/3/2016 10:...
# add only the old one
add-esxsoftwarepackage -imageprofile ESX-6.5-old-driver -softwarepackage "hpe-smx-provider 600.03.11.00.9-2768847"
#export to ISO
Export-EsxImageProfile -ImageProfile ESX-6.5-old-driver -ExportToIso -filepath "c:\tmp\gigel.iso"
# list packages in a vib to be sure the right one was included
(Get-EsxImageProfile -name ESX-6.5-old-driver).viblist | findstr smx
Burn the ISO.
The machine on which I was testing, just as a reference (and google keyword) is an HP DL385 G7 with 2 x AMD 6282SE CPUs.
Also extra for the search engines: Running ESX 6.5 on HP DL385 G7 / ESX 6.5 on G7.
Thanks to sp4rt4n for the whole idea!! You rock.
Before I saw your post I had abandoned any attempt at playing with this and did not think that just replacing a driver with an older version would solve it.
