Section 1 – Plan, Install and Upgrade VMware ESX/ESXi
- Objective 1.2 – Upgrade VMware ESX/ESXi
In order to upgrade to vSphere 4, an ESX host must have a /boot partition of at least:
vSphere Upgrade Guide ESX 4.0 ESXi 4.0 vCenter Server 4.0 vSphere Client 4.0 Page 73
Direct, in-place upgrade from ESX 2.5.5 to ESX 4.0 is not supported, even if you upgrade to ESX 3.x as an intermediary step. The default ESX 2.5.5 installation creates a /boot partition that is too small to enable upgrades to ESX 4.0. As an exception, if you have a non-default ESX 2.5.5 installation on which at least 100MB of space is available on the /boot partition, you can upgrade ESX 2.5.5 to ESX 3.x and then to ESX 4.0.
The vSphere 4 Host Update Utility upgrades the (Choose Two):
A.service console if present
C.virtual machine hardware
vSphere Upgrade Guide, ESX 4.0, ESXi 4.0, vCenter Server 4.0, vSphere Client 4.0, page 67
‘vSphere Host Update Utility Graphical utility for standalone hosts. Allows you to perform remote upgrades of ESX 3.x/ESXi 3.5 hosts to ESX 4.0/ESXi 4.0. vSphere Host Update Utility upgrades the virtual machine kernel (vmkernel) and the service console, where present. vSphere Host Update Utility does not upgrade VMFS datastores or virtual machine guest operating systems.’
Before you upgrade an ESX/ESXi host (Choose Three):
A.verify current hardware is supported per the vSphere Systems Compatibility Guide
B.run the VMware CPU Identification Utility
C.run the vSphere 4 Pre-Upgrade Script from the command line
D.schedule a maintenance window for 32-bit hardware
E.compare the md5sum of the downloaded file to the value on the VMware download website
Ensure that the hardware and/or virtual machine meets the minimum system requirements for VMware vCenter 4.0
You can use vSphere Host Update Utility to upgrade ESX 3.x to ESX 4.0 and ESXi 3.5 hosts to ESXi 4.0. You cannot use vSphere Host Update Utility to convert ESX hosts to ESXi hosts, or the reverse. When you select a host to be upgraded, the tool performs an automated host compatibility check as a preupgrade step. The check verifies that each host is compatible with ESX 4.0/ESXi 4.0, including the required CPU, and has adequate boot and root partition space. In addition to the automated preupgrade script, you can specify a postupgrade configuration script to ease deployment.
Note the preupgrade script is automated and so does not need to be run explicitly.
ESX and vCenter Server Installation Guide, ESX 4.0 vCenter Server 4.0, page 13.
ESX Hardware Requirements * 64-Bit Processor
The following ESX versions are supported for direct upgrading to vSphere 4 (Choose Two):
D.ESX 3.0.0, 3.0.1, 3.0.2
vSphere Upgrade Guide ESX 4.0, ESXi 4.0, vCenter Server 4.0, vSphere Client 4.0, Page ‘Upgrade Support for ESX/ESXi:
ESX 3.0.0, ESX 3.0.1, ESX 3.0.2, ESX 3.0.3, ESX, ESXi 3.5 – Yes
ESX 2.5.5 Limited Support’
Which of the following are true regarding the ESX Service Console file system structure (Choose Two)?
A.separate mount points are created for /tmp, /var/log and swap by default
B.running out of space on /var/log can cause vSphere Client connectivity disruptions
C.running out of space on / can cause vSphere Client connectivity disruptions
D.separate mount points are created for /var/log and swap by default
Mastering VMware vSphere 4 Page 24.
Default VMware ESX Partition Scheme
Mount Point Name Type Size /boot Ext3 250MB / Ext3 5000MB (5GB) (none) Swap 600MB /var/log Ext3 2000MB (2GB) (none) Vmkcore 100MB
The / (or "root") partition stores the ESX system and all files not stored in another custom partition. If this partition is filled to capacity, the ESX host could crash. It is imperative to prevent this.
Note: The explanation uses partition sizes from VI3 days, not vSphere 4.