Posted on 25 July, 2012 by Kyle Gleed, Sr. Technical Marketing Architect, VMware
Ever wondered how to create an ISO image from a patch that was downloaded from VMware’s web site? Here are the steps:
(1) Download the patch from VMware's web site. For help with the patch portal check here. At the time I’m writing this the latest 5.0 patch is "ESXi500-201207001.zip" so I’ll use it. As an FYI, here’s a link to the patch release notes.
(2) Start PowerCLI and import the patch using the “Add-EsxSoftwareDepot” cmdlet:
(3) View the available image profiles using the “Get-EsxImageProfile” cmdlet:
With each patch there will typically be an image profile with all the updates (security fixes, bug updates and enhancements) and one with just the security updates. The patch release notes explains why:
“Starting with ESXi 5.0 Update 1, VMware patch and update releases contain general and security-only image profiles. Security-only image profiles are applicable to new security fixes only. No new bug fixes are included, but bug fixes from earlier patch/update releases are included.
The general release image profile supersedes the security-only profile. Application of the general release image profile applies to new security and bug fixes.
The security-only image profiles are identified with the additional "s" identifier in the image profile name.”
For more information on how patches are classified in terms of bug fixes, security fixes and enhancements refer to KB article 2014447.
(4) Use the "Export-EsxImageProfile" cmdlet to save the image profile of your choice as an ISO image that you can use to boot your hosts and run the installer.
For more information on the ESXi Image Builder:
Using the ESXi Image Builder CLI
Image Builder and Auto Deploy PowerCLI Quick Reference
Follow me on Twitter @VMwareESXi
John Kenendy
Thanks Kyle. How do I make a depot (zip) file from a running instance of an ESXi server?
Kyle Gleed
There is no way to create a depot from a running vSphere hosts. To create a custom ZIP you need to start with a software depot provided by VMware or a partner, create a custom image profile, add/remove packages as needed, and then export the custom image as a depot.
nats
Hi Kyle,
Can i ask how to create a software depot provided by VMware or a partner?
I am using ESXi-5.0.0-381646-standard being seen in vSphere Client Summary tab. i am planning to include my device driver to support our PCIe Drive. The ESXi being used is just an evaluation, planned to acquire a legit version once proven to be working.
appreciate your immediate reply, thanks in advance.
Isaias Machado
Thanks Kyle Gleed .. Your message helped a lot in solving my problem with auto-start.
Chris Smith
to create the esx off line bundle attach to the software depot at vmware and export the required esx profile as a bundle..
Add-EsxSoftwareDepot -depoturl “https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml”
Get-EsxImageProfile
Export-EsxImageProfile “ESXi-5.1.0-799733-standard” -ExportToBundle -FilePath “C:IBesx5.1.zip”
Chris Smith
For Just a list of 5.1 Images
Get-EsxImageProfile | Where {$_.Name -match “ESXi-5.1”} | Select-Object -ExpandProperty Name
Barry
Hi Kyle,
If there are 2 patch files, does creating from the latest patch (ESXi510-201307001) cover the older patch file (ESXi510-201305001)?
What I mean for cover is that is the older patch included in LatestFile-standard?
Kyle Gleed
Hi Barry,
You need to look at the VIBs included with each patch. Recent patches/fixes may or may not include some of the fixes from previous patches. Depends what VIBs are being patched. At the VIB level patches are cumulative (meaning new VIB updates will include the fixes from any prior VIB updates). However, be aware that not all patches include the same VIBs. If patch 1 updates esx-base and tools-light and patch 2 only updates esx-base, then patch 2 would include the esx-base fixes from both patch 1 and patch 2, but would not include the tools-light fixes from patch 1.
In your specific example, patch ESXi510-201305001 updates the VIB “esx-base”. Patch ESXi510-201307001 updates VIBs “esx-base”, “net-e1000”, “tools-light”, and “scsi-hpsa”. So in this case, because the newer patch includes the same VIB (esx-base) as the previous patch the fixes in 201305001 are included in 201307001.
Barry
Hi Kyle,
Thanks for your prompt reply.
Your explanation helps.