vSphere Installation and Setup - Documentation - VMware
vSphere Installation and Setup - Documentation - VMware
vSphere Installation and Setup - Documentation - VMware
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>vSphere</strong> <strong>Installation</strong> <strong>and</strong> <strong>Setup</strong><br />
Changes in the ESXi<br />
installation <strong>and</strong> upgrade<br />
process<br />
For complete information on using <strong>vSphere</strong> Auto Deploy <strong>and</strong> ESXi Image<br />
Builder PowerCLI, see Chapter 5, “Installing ESXi Using <strong>vSphere</strong> Auto<br />
Deploy,” on page 63 <strong>and</strong> Chapter 6, “Using <strong>vSphere</strong> ESXi Image Builder<br />
CLI,” on page 143.<br />
ESXi 5.x uses a single installer wizard for fresh installations <strong>and</strong> upgrades.<br />
ESXi 5.x also provides a new option for deploying ESXi directly into the host<br />
memory with <strong>vSphere</strong> Auto Deploy. The vihostupdate <strong>and</strong> esxupdate utilities<br />
are not supported for ESXi 5.x. You cannot upgrade or migrate from earlier<br />
ESX or ESXi versions to ESXi 5.x by using any comm<strong>and</strong>-line utility. After you<br />
have upgraded or migrated to ESXi 5.x, you can upgrade or patch ESXi 5.x hosts<br />
using vCLI esxcli comm<strong>and</strong>s.<br />
IMPORTANT After you upgrade or migrate your host to ESXi 5.x, you cannot<br />
roll back to your version 4.x ESX or ESXi software. Back up your host before<br />
you perform an upgrade or migration, so that, if the upgrade or migration fails,<br />
you can restore your 4.x host.<br />
If you are upgrading an existing ESX or ESXi host, see the <strong>vSphere</strong> Upgrade<br />
documentation.<br />
Installer caching Instead of using a binary image to install the system, whatever bits were used<br />
at boot time are cached to the system. This caching reduces installation<br />
problems caused by accessing installation files across networks that are under<br />
load.<br />
Changes to partitioning<br />
of host disks<br />
<strong>VMware</strong> vCenter Server<br />
Appliance<br />
NOTE Scripted installations cannot PXE boot a server <strong>and</strong> then obtain the<br />
binary image from some other form of media.<br />
All freshly installed hosts in <strong>vSphere</strong> 5.x use the GUID Partition Table format<br />
instead of the MSDOS-style partition label. This change supports ESXi<br />
installation on disks larger than 2TB.<br />
Newly installed <strong>vSphere</strong> 5.x hosts use VMFS5, an updated version of the<br />
<strong>VMware</strong> File System for <strong>vSphere</strong> 5.x. Unlike earlier versions, ESXi 5.x does not<br />
create VMFS partitions in second <strong>and</strong> successive disks.<br />
Upgraded systems do not use GUID Partition Tables (GPT), but retain the older<br />
MSDOS-based partition label.<br />
NOTE Partitioning for hosts that are upgraded to ESXi 5.x differs significantly<br />
from partitioning for new installations of ESXi 5.x. See the <strong>vSphere</strong> Upgrade<br />
documentation.<br />
As an alternative to installing vCenter Server on a Windows machine, <strong>vSphere</strong><br />
5.x provides the <strong>VMware</strong> vCenter Server Appliance. The vCenter Server<br />
Appliance is a preconfigured Linux-based virtual machine optimized for<br />
running vCenter Server <strong>and</strong> associated services.<br />
10 <strong>VMware</strong>, Inc.
Change language