You own a dedicated server running ESXi 5.0 and want to simply upgrade from ESXi 5.0 to 5.1? Just use the "esxcli" commands.
Real-world use case
You're on an OVH dedicated server running ESXi 5.0 and want to move to version 5.1 without breaking anything: here's how to do it.
This article covers an ESXi upgrade on a 2013 mSP dedicated server available at OVH.
The method works on other server ranges, you'll just need to adapt this method.
The 5.0 to 5.1 upgrade has been offered by VMware since August 2012.
Understanding the migration process well:
Before starting the migration of an infrastructure, it's important to know a few basic steps, with certain points to remember:
- The upgrade is a multi-step process, perform the steps in order.
- Before upgrading, you need to understand the process as a whole.
- The steps are irreversible!
- If you use plugins, check their compatibility with ESXi 5.1.
- Check your server's current hardware compatibility with ESXi 5.1.
- You also need to master the technical language (VIB, image profile, software depot, etc.).
- Take precautions (it's never repeated enough) : back up your VMs!
- Understand the "esxcli" command and its parameters.
Good to know: the mSP offering was only available for two months! Quickly replaced by the XEON E3 offering on: www.soyoustart.com, and it's architected the same way hardware-wise.
The problem:
Our issue is to migrate a hypervisor running VMware ESXi from 5.0 to 5.1.
For the migration process (ESXi 5.0 to 5.1) you need to ask yourself certain questions: (examples)
- Is my ESXi server physically accessible? Is it hosted in a datacenter?
- What components make up my server? Are they compatible with ESXi 5.1?
- Are drivers available for the future ESXi 5.1 system I want to set up?
This kind of question is essential before starting any kind of migration.
Don't hesitate to take the time to list your issues and find answers to them.
In the case of my 2013 mSP dedicated server, here's the result of my "brainstorming":
- Is my server compatible with the VMware 5.1 solution?
The server I use is an mSP 2013, already virtualized under VMware ESXi 5.0, hosted by OVH. The components are already designed for VMware, with the components it uses listed below:
- CPU: Intel Xeon CPU E3-1245 V2 @ 3.40 GHz
- RAM: 32GB available
- BIOS: version 1101 on P8H77-M PRO motherboard
- Virtualization enabled, vmx or svm flag present.
- Disks: 2 x 2000GB in sata / sda / sdb => 194, 90 MB/s and no bad sectors.
To check hardware compatibility with VMware: the VMware compatibility guide.
- How can I access my dedicated server?
Since the server is hosted in a datacenter, I can't access it physically! The only option available to me is remote access via: https and ssh.
- Is a migration possible via my available remote access?
Yes, there are two possibilities:
- The vSphere client lets you notably enable SSH on the server and allows certain actions on system management, certain software/hardware checks, viewing security rules, etc.
- SSH access (once enabled) lets you tackle the migration via commands available through ESX.
- Is the command syntax available online?
VMware provides official documentation via their support on the syntax to use.
Available at this address: the official documentation.
A word of caution before upgrading
The upgrade is a major step in the evolution of an IT system.
You need to understand that it's a set of consecutive processes that shouldn't be taken lightly.
A wrong command, one extra option can play bad tricks on you, be careful!
Make sure you properly follow the logical sequence of the process to successfully complete your upgrade.
Adapt your case to your own upgrade, follow step by step, this article can help you.
The entire migration needs to be done in the hypervisor's terminal over SSH, enable SSH.
Enabling the SSH server and client in VMware vSphere:
Head to the "configuration" tab then "security profile", click properties (firewall):
https://content.kassianoff.fr/vignette\_ovh\_01.png
The firewall properties window appears:
https://content.kassianoff.fr/vignette\_ovh\_02.png
Apply the changes and start backing up your virtual machines.
Moving a virtual machine via SCP:
Here's an example with a virtual machine I'm moving to another ESXi:
scp /vmfs/volumes/datastore1/Vyatta-1/* user@server:/vmfs/volumes/datastore1/Vyatta-1/
Upgrading VMware from 5.0 to 5.1:
VSphere Installation Bundle (VIB)
I'm going to talk to you about "VIB", which is similar to a ZIP archive.
VIB stands for "vSphere Installation Bundle", a VIB is added to an ESXi image, and the VIB's files will be installed on the host. When a VIB is removed from an ESXi image, its files are deleted.
A VIB is a package made up of three files:
- An archive file
- An XML file descriptor
- A signature file
Why am I telling you about VIB? Because we're going to list all of our VIBs on our ESXi 5.0.
We'll be able to find out the name, version, vendor, acceptance level, and installation date of all our VIBs running on our current ESXI 5.0.
Keep in mind that VIB lets you distribute software and drivers on an ESXi host.
The command to list the VIBs installed on our ESXi 5.0:
esxcli software vib list
The command returns the following list:
Name Version Vendor Acceptance Level Install Date
----------------------------- ---------------------------------- ------ ------------------ ------------
net-e1001e 1.0.0 Chilly CommunitySupported 2013-11-27
ata-pata-amd 0.3.10-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ata-pata-atiixp 0.4.6-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ata-pata-cmd64x 0.2.5-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ata-pata-hpt3x2n 0.3.4-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ata-pata-pdc2027x 1.0-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ata-pata-serverworks 0.4.3-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ata-pata-sil680 0.4.8-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ata-pata-via 0.3.3-2vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
block-cciss 3.6.14-10vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ehci-ehci-hcd 1.0-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
esx-base 5.1.0-0.0.799733 VMware VMwareCertified 2013-11-26
esx-dvfilter-generic-fastpath 5.1.0-0.0.799733 VMware VMwareCertified 2013-11-26
esx-tboot 5.1.0-0.0.799733 VMware VMwareCertified 2013-11-26
esx-xlibs 5.1.0-0.0.799733 VMware VMwareCertified 2013-11-26
esx-xserver 5.1.0-0.0.799733 VMware VMwareCertified 2013-11-26
ima-qla4xxx 2.01.31-1vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ipmi-ipmi-devintf 39.1-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ipmi-ipmi-msghandler 39.1-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ipmi-ipmi-si-drv 39.1-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
misc-cnic-register 1.1-1vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
misc-drivers 5.1.0-0.0.799733 VMware VMwareCertified 2013-11-26
net-be2net 4.1.255.11-1vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-bnx2 2.0.15g.v50.11-7vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-bnx2x 1.61.15.v50.3-1vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-cnic 1.10.2j.v50.7-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-e1000 8.0.3.1-2vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-e1000e 1.1.2-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-enic 1.4.2.15a-1vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-forcedeth 0.61-2vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-igb 2.1.11.1-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-ixgbe 3.7.13.6iov-10vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-nx-nic 4.0.558-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-r8168 8.013.00-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-r8169 6.011.00-2vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-s2io 2.1.4.13427-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-sky2 1.20-2vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-tg3 3.110h.v50.4-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
net-vmxnet3 1.1.3.0-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
ohci-usb-ohci 1.0-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
sata-ahci 3.0-13vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
sata-ata-piix 2.12-6vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
sata-sata-nv 3.5-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
sata-sata-promise 2.12-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
sata-sata-sil24 1.1-1vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
sata-sata-sil 2.3-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
sata-sata-svw 2.3-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-aacraid 1.1.5.1-9vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-adp94xx 1.0.8.12-6vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-aic79xx 3.1-5vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-bnx2i 1.9.1d.v50.1-5vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-fnic 1.5.0.3-1vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-hpsa 5.0.0-21vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-ips 7.12.05-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-lpfc820 8.2.3.1-127vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-megaraid-mbox 2.20.5.1-6vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-megaraid-sas 5.34-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-megaraid2 2.00.4-9vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-mpt2sas 10.00.00.00-5vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-mptsas 4.23.01.00-6vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-mptspi 4.23.01.00-6vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-qla2xxx 902.k1.1-9vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-qla4xxx 5.01.03.2-4vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
scsi-rste 2.0.2.0088-1vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
uhci-usb-uhci 1.0-3vmw.510.0.0.799733 VMware VMwareCertified 2013-11-26
tools-light 5.1.0-0.0.799733 VMware VMwareCertified 2013-11-27
We have a lot of VIBs installed on our ESXi 5.0, and only one VIB isn't VMware certified.
The label "CommunitySupported" lets you distinguish it, while the others are "VMwareCertified".
The "CommunitySupported" acceptance level is created by individuals or external partners of the VMware partnership program.
Our network card, listed below, isn't VMware certified:
net-e1001e 1.0.0 Chilly CommunitySupported 2013-11-27
Why am I telling you about this network card's uncertified vib?
Imagine upgrading your ESXi without reinstalling the VIB for the network card.
Without this VIB, the network card wouldn't be recognized, so it would be impossible to reach the ESXi 5.1...
All the information about VIBs is available on VMware's official blog post.
To download official VIBs: VMware-patch
To download Community VIBs: vm-help and on vm-help-forum
To check the network card's xml file: net-e1001e
Tools developed by VMware engineers: labs-vmware
We'll now list all the updates available on the VMware depot:
esxcli software sources profile list -d http://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
The command returns the list of available updates:
Name Vendor Acceptance Level
-------------------------------- ------------ ----------------
ESXi-5.0.0-20130804001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20120404001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120704001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20120701001s-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-799733-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20121201001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20121201001s-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20130704001-no-tools VMware, Inc. PartnerSupported
ESXi-5.5.0-1331820-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20111204001-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-799733-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20130304001-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20131001001s-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120302001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20130804001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120901001s-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120302001-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20121004001-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20130704001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-469512-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20120604001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20120701001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20120704001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20130801001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20131001001s-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20121204001-no-tools VMware, Inc. PartnerSupported
ESXi-5.5.0-1331820-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120604001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20110904001-notools VMware, Inc. PartnerSupported
ESXi-5.0.0-20131002001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20130304001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20120504001-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20130504001-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20130701001s-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20111204001-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20121201001s-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20130401001s-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20130301001s-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120504001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20130301001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20121202001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20130801001s-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20111104001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120901001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20121204001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20121201001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20120904001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120301001s-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20130504001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20110904001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20111104001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-469512-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20121004001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20120904001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20121202001-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20130304001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120404001-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20131004001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20130504001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20120301001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20131001001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20130701001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20130304001-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20130402001-standard VMware, Inc. PartnerSupported
ESXi-5.0.0-20131001001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20130401001s-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20131004001-no-tools VMware, Inc. PartnerSupported
ESXi-5.0.0-20131002001-no-tools VMware, Inc. PartnerSupported
ESXi-5.1.0-20130504001-standard VMware, Inc. PartnerSupported
ESXi-5.1.0-20130402001-no-tools VMware, Inc. PartnerSupported
In our case, the depot we're interested in is "ESXi-5.1.0-799733-standard".
Before starting the upgrade process, there's still one step left: maintenance mode.
Maintenance mode on ESXi 5.0:
Maintenance mode lets you put the hypervisor into a special mode in order to modify the system.
If maintenance mode isn't enabled, an error will tell you the system change failed.
How do you enable maintenance mode?
- Through the vSphere interface, right-click the server and select "maintenance mode".
- In the terminal via SSH with the following command:
vim-cmd hostsvc/maintenance_mode_enter
An error like "mode_failed" appears?
Enter maintenance mode mode failed
'vim.Task:haTask-ha-host-vim.HostSystem.enterMaintenanceMode-509037695'
You need to shut down all your virtual machines and try again.
Once maintenance mode is enabled:
vim-cmd hostsvc/maintenance_mode_enter
'vim.Task:haTask-ha-host-vim.HostSystem.enterMaintenanceMode-509042051''vim.Task:haTask-ha-host-vim.HostSystem.enterMaintenanceMode-509037695'
In vSphere, your ESXi host is now in maintenance mode.
Installing the ESXi 5.0 to 5.1 upgrade
Starting the upgrade to ESXi 5.1 is the most critical step, don't mistake your option and don't reboot your server after installing version 5.1.
Here's the command to run in your terminal:
esxcli software profile install -d http://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-5.1.0-799733-standard --ok-to-remove
The command's result:
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMware_bootbank_ata-pata-amd_0.3.10-3vmw.510.0.0.799733, VMware_bootbank_ata-pata-atiixp_0.4.6-4vmw.510.0.0.799733, VMware_bootbank_ata-pata-cmd64x_0.2.5-3vmw.510.0.0.799733, VMware_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.510.0.0.799733, VMware_bootbank_ata-pata-pdc2027x_1.0-3vmw.510.0.0.799733, VMware_bootbank_ata-pata-serverworks_0.4.3-3vmw.510.0.0.799733, VMware_bootbank_ata-pata-sil680_0.4.8-3vmw.510.0.0.799733, VMware_bootbank_ata-pata-via_0.3.3-2vmw.510.0.0.799733, VMware_bootbank_block-cciss_3.6.14-10vmw.510.0.0.799733, VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.510.0.0.799733, VMware_bootbank_esx-base_5.1.0-0.0.799733, VMware_bootbank_esx-dvfilter-generic-fastpath_5.1.0-0.0.799733, VMware_bootbank_esx-tboot_5.1.0-0.0.799733, VMware_bootbank_esx-xlibs_5.1.0-0.0.799733, VMware_bootbank_esx-xserver_5.1.0-0.0.799733, VMware_bootbank_ima-qla4xxx_2.01.31-1vmw.510.0.0.799733, VMware_bootbank_ipmi-ipmi-devintf_39.1-4vmw.510.0.0.799733, VMware_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.510.0.0.799733, VMware_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.510.0.0.799733, VMware_bootbank_misc-cnic-register_1.1-1vmw.510.0.0.799733, VMware_bootbank_misc-drivers_5.1.0-0.0.799733, VMware_bootbank_net-be2net_4.1.255.11-1vmw.510.0.0.799733, VMware_bootbank_net-bnx2_2.0.15g.v50.11-7vmw.510.0.0.799733, VMware_bootbank_net-bnx2x_1.61.15.v50.3-1vmw.510.0.0.799733, VMware_bootbank_net-cnic_1.10.2j.v50.7-3vmw.510.0.0.799733, VMware_bootbank_net-e1000_8.0.3.1-2vmw.510.0.0.799733, VMware_bootbank_net-e1000e_1.1.2-3vmw.510.0.0.799733, VMware_bootbank_net-enic_1.4.2.15a-1vmw.510.0.0.799733, VMware_bootbank_net-forcedeth_0.61-2vmw.510.0.0.799733, VMware_bootbank_net-igb_2.1.11.1-3vmw.510.0.0.799733, VMware_bootbank_net-ixgbe_3.7.13.6iov-10vmw.510.0.0.799733, VMware_bootbank_net-nx-nic_4.0.558-3vmw.510.0.0.799733, VMware_bootbank_net-r8168_8.013.00-3vmw.510.0.0.799733, VMware_bootbank_net-r8169_6.011.00-2vmw.510.0.0.799733, VMware_bootbank_net-s2io_2.1.4.13427-3vmw.510.0.0.799733, VMware_ [truncated]
VIBs Removed: Chilly_bootbank_net-e1001e_1.0.0, VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-atiixp_0.4.6-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-cmd64x_0.2.5-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-pdc2027x_1.0-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-serverworks_0.4.3-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-sil680_0.4.8-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-via_0.3.3-2vmw.500.0.0.469512, VMware_bootbank_block-cciss_3.6.14-10vmw.500.0.0.469512, VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.500.1.11.623860, VMware_bootbank_esx-base_5.0.0-1.11.623860, VMware_bootbank_esx-tboot_5.0.0-0.0.469512, VMware_bootbank_ima-qla4xxx_2.01.07-1vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-devintf_39.1-4vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.500.0.0.469512, VMware_bootbank_misc-cnic-register_1.1-1vmw.500.0.0.469512, VMware_bootbank_misc-drivers_5.0.0-1.11.623860, VMware_bootbank_net-be2net_4.0.88.0-1vmw.500.0.7.515841, VMware_bootbank_net-bnx2_2.0.15g.v50.11-5vmw.500.0.0.469512, VMware_bootbank_net-bnx2x_1.61.15.v50.1-1vmw.500.0.0.469512, VMware_bootbank_net-cnic_1.10.2j.v50.7-2vmw.500.0.0.469512, VMware_bootbank_net-e1000_8.0.3.1-2vmw.500.0.7.515841, VMware_bootbank_net-e1000e_1.1.2-3vmw.500.1.11.623860, VMware_bootbank_net-enic_1.4.2.15a-1vmw.500.0.0.469512, VMware_bootbank_net-forcedeth_0.61-2vmw.500.0.0.469512, VMware_bootbank_net-igb_2.1.11.1-3vmw.500.0.0.469512, VMware_bootbank_net-ixgbe_2.0.84.8.2-10vmw.500.0.0.469512, VMware_bootbank_net-nx-nic_4.0.557-3vmw.500.1.11.623860, VMware_bootbank_net-r8168_8.013.00-3vmw.500.0.0.469512, VMware_bootbank_net-r8169_6.011.00-2vmw.500.0.0.469512, VMware_bootbank_net-s2io_2.1.4.13427-3vmw.500.0.0.469512, VMware_bootbank_net-sky2_1.20-2vmw.500.0.0.469512, VMware_bootbank_net-tg3_3.110h.v50.4-4vmw.500.0.0.469512, VMware_bootbank_oh [truncated]
VIBs Skipped:
You've officially just migrated to VMware ESXi 5.1! Make sure not to reboot.
What do the options in the previous command correspond to?
- esxcli: management command on VMware ESXi 5.x
- software: allows management of the ESXi image and packages.
- profile: specifies the name of the installed image profile.
- install -d: install from a depot.
- –ok-to-remove: confirms removing the old package.
For more information on the commands, visit VMware's documentation.
You can display all available commands via:
esxcli esxcli command list
Earlier I stressed not rebooting ESXi 5.1, why?
Without adding the network card's VIB, the network card wouldn't be recognized, so it would be impossible to reach the ESXi 5.1.
Installing the "net-e1001e" network card's VIB:
Our network card, at the "CommunitySupported" acceptance level, needs to be reinstalled on ESXi 5.1.
Run the following command:
esxcli software vib install -v http://files.v-front.de/net-e1001e-1.0.0.x86_64.vib
The command's result:
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: Chilly_bootbank_net-e1001e_1.0.0
VIBs Removed:
VIBs Skipped:
Your "net-e1001e" network card is now installed, your server is operational.
Conclusion
This article detailed upgrading a VMware ESXi 5.0 hypervisor to 5.1 on an OVH mSP dedicated server, via enabling SSH, analyzing the installed VIBs, and using the esxcli command to apply the update profile. Special attention was given to the non-VMware-certified network card, whose VIB had to be manually reinstalled to avoid losing network access after the reboot. This method, although irreversible once started, remains applicable to other server ranges with a few adjustments. Disable maintenance mode on the server:
vim-cmd hostsvc/maintenance_mode_exit
Rebooting the server:
reboot
On startup, the vSphere client will offer you the upgrade to 5.1.
https://content.kassianoff.fr/vignette\_ovh\_03.png
You've officially succeeded in upgrading VMware ESXi 5.0 to 5.1!
For those interested, there's: ESXi-Customizer (ESXi-Customizer-v2.7.1.exe) which lets you customize an ESXi 5.x ISO, which allows you to inject your VIBs.
Another small tip for those with a virtualized ESXi (Workstation or ESXi), a VMware Tools VIB is available on VMware's labs: vmware-tools-for-nested-esxi.
One or more long lines were truncated at 2000 characters