Whats New in VMware

vSphere

5.1 Platform
VMware vSphere 5.1
T E CH NI C AL MAR K E T I NG DOCU ME NTAT I ON
V 2 . 0 / U P DAT E D J U NE 2 01 2
Whats New in VMware
vSphere 5.1 Platform
T E C H NI C AL WH I T E PAP E R / 2
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vSpherePlatformEnhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UserAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vMotionEnhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ExtendedGuestOSandCPUSupport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AgentlessAntivirusandAntimalware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VirtualMachineEnhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NewVirtualMachineFeatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IntroducingVirtualMachineCompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AutoDeploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
StatelessCachingMode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
StatefulInstallMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RemoteLoggingandDumpCollection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ImprovedScalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T E C H NI C AL WH I T E PAP E R / 3
Whats New in VMware
vSphere 5.1 Platform
Introduction
VMware vSphere 5.1 (vSphere 5.1) provides many new features and enhancements that further extend
the core capabilities of the VMware vSphere (vSphere) platform. Included among these are notable
improvements in the areas of host security, logging, monitoring, and deployment; new VMware vSphere
vMotion (vMotion) capabilities that enable virtual machines to be migrated between hosts and clusters with
no shared storage; and support for the latest processors and guest operating systems (OS). This paper provides
an overview of the new features and capabilities being introduced with vSphere 5.1.
This paper is organized into the following four sections:
vSo|ere|o:eaJre:anden|ancenen:
|n|ancedv|o|oncaoab||||e:
V|rJa|nac||neeaJre:anden|ancenen:
nrodJc|onoV|varevSo|ereAJo|eo|oyAJo|eo|oy:ae|e::cac||nqand:aeJ||n:a||
vSphere Platform Enhancements
A|eyocJ:orvSo|ereva:on|norov|nq|o::ecJr|yaJd||nqandnon|or|nqT||:|nc|Jdede||n|na|nq
the reliance on a shared root user account and adding support for SNMPv3.
User Access
Ac|a||enqev||ear||ervSo|erere|ea:e:va:|ereoJ|renenoradn|n|:raor:o:|areaconnonroo
J:eraccoJnv|envor||nqron|e|o::|e||T|ere||anceona:|aredadn|n|:ra|veaccoJncanev||
several challenges:
A||:|e||ac|v|yva:|oqqeda:roona||nq|d|cJ|oaJd||nd|v|dJa|J:erac|v|yon|e|o:
T|eneedocoord|naeoa::vordre:e:anonqnanyadn|n|:raor:oenre:J|ed|n|erooJ:er
becon|nqanexceo|onoreoccJrr|nqoa::vordc|anqeoo||c|e:A:are:J||eroooa::vordva:rare|y
if ever, changed.
va:d|cJ|orac||enJnberoadn|n|:raor:v||rooacce::
va:d|cJ|orenoveacce::v|enoer:onne||e|econoanyorc|anqedro|e:
Toaddre::|e:ec|a||enqe:and|norove|o::ecJr|yV|varenade:evera||norovenen:o|e|SX|:|e||
in vSphere 5.1:
ThereisnolongeradependencyonasharedrootaccountLocalusersassignedadministrativeprivileges
automaticallygetfullshellaccessWithfullshellaccesslocalusersnolongermustsutoroottorun
privilegedcommands
Adn|n|:ra|veor|v||eqe:canberenovedron|edeaJ|rooaccoJneec|ve|ye||n|na|nqaoooJ|ar
targetforanyonewhomightattempttogainunauthorizedaccesstoavSpherehost
TheabilitytoautomaticallyterminateidleshellsessionswithanewUserVarsESXiShellInteractiveTimeOutvariable
Terminationofinactiveshellsessionshelpspreventsecuritybreachesthatcanoccurwhenadministrators
failtoproperlylogoutoftheshell
T E C H NI C AL WH I T E PAP E R / 4
Whats New in VMware
vSphere 5.1 Platform
Auditing
nvSo|erea|||o:ac|v|yronbo||e:|e||and|e||recCon:o|eU:ernerace|CU|:nov|oqqed
Jnder|eaccoJno|e|oqqed|nJ:erT||:en:Jre:J:eraccoJnab|||yna||nq|ea:yonon|orandaJd|
activity on the host.
Monitoring
vSphere 5.1 adds support for SNMPv3, which provides many improvements over SNMPv2. These include added
security, with SNMP authentication, and added privacy, with SSL encryption. SNMPv3 also provides additional
conqJra|oncaoab||||e:|roJq|SN||SeA|:o|nvSo|ere|eSN||aqen|a:beenJnbJnd|edron|e
V||erne|andnovrJn:a:an|ndeoendenaqenon|e|o:T||:na|e:|ea:|ero|ncorooraeSN||Jodae:
andoac|e:becaJ:e|eyareno|onqer|edo|evSo|ere|erne|
vMotion Enhancements
|n|ancenen:ov|o|on|nvSo|ereorov|deanev|eve|oea:eandex|b|||yor||vev|rJa|nac||ne
migrations. vSphere 5.1 now enables users to combine vMotion and VMware vSphere Storage vMotion
(Storage vMotion) into one operation. The combined migration copies both the virtual machine memory and its
d|:|over|enevor|o|ede:|na|on|o:n:na||erenv|ronnen:|eab|||yo:|nJ|aneoJ:|yn|qraebo|
memory and storage enables virtual machines to be migrated between hosts that do not have shared storage.
In larger environments, this capability enables virtual machines to be migrated between clusters that do not
have a common set of datastores.
VM VM
VMDK VMDK
VMDK
VM
Migration
Network Network
ESXi host
Local
datastore
Local
datastore
Local
datastore
Local
datastore
ESXi host ESXi host ESXi host
Figure 1.
T E C H NI C AL WH I T E PAP E R / 5
Whats New in VMware
vSphere 5.1 Platform
Extended Guest OS and CPU Support
A|onqv||:ecJr|yaJd||nqandnon|or|nqJodae:and|een|ancedv|o|oncaoab||||e:vSo|ereadd:
:Joooror|e|ae:qJe:ooera|nq:y:en:andC|U:vSo|ere|nrodJce::Joooror||cro:o\|ndov:
bo|:erverandde:|ooed||on:a|onqv||:Joooror|e|ae:A||andne|C|U:|nc|Jd|nq|eA||
Piledriver series and the Intel Ivy Bridge and Sandy Bridge series.
Figure 2.
For a comprehensive list of the supported guest operating systems and server hardware, refer to the
VMware Compatibility GuideT|eqJ|de|:JodaedreoJen|y:o|:aqood|deaoc|ec||oenoqe|e
latest updates.
Agentless Antivirus and Antimalware
V|varevS||e|d|ndoo|nvS||e|d|ndoo|nnov|nc|Jded|nvSo|ereooad:an|v|rJ:and
antimalware agent processing inside guest virtual machines to a dedicated secure virtual appliance delivered
byV|vareoarner:So|J|on:ba:edonvS||e|d|ndoo|n|norovecon:o||da|onra|o:andoerornanceby
eliminating antivirus storms due to signature updates, because updating occurs on the security virtual
appliance instead of inside each individual virtual machine. These solutions also streamline antivirus and
antimalware deployment and monitoring in VMware environments and satisfy compliance and audit
reoJ|renen:|roJq||oqq|nqoan|v|rJ:andan|na|vareac|v||e:
Virtual Machine Enhancements
vSo|ere|nc|Jde::evera|v|rJa|nac||ne|norovenen:a:ve||nov:Jooor:JoovC|U:|na
single virtual machine, enables improved graphics support with the introduction of hardware-based virtual
qrao||c:oroce::|nqJn|:vC|U:|nrodJce:qJe:|eve|:oraqerec|ana|onandorov|de:|norovedC|U
virtualization capabilities.
NOTE: The vGPU and guest-level storage reclamation capabilities provided in vSphere 5.1 have a dependency
on a future version of VMware View (View). Refer to the View documentation for information on when these
features will be available.
New Virtual Machine Features
64-vCPU Support
V|rJa|nac||ne:rJnn|nqonavSo|ere|o:canbeconqJredv||JoovC|U:v||c|denon:rae:|e
naJr|yo|evSo|ere|yoerv|:orand|ov||:ve||:J|edoa|eoneven|e|arqe:oaoo||ca|onvor||oad:
\|||eab|||yo|o:v|rJa|nac||ne:rJnn|nqJoovC|U:andT|oPA|vSo|ereenab|e:J:er:o
v|rJa||.eany:|.evor||oadv||condence
T E C H NI C AL WH I T E PAP E R / 6
Whats New in VMware
vSphere 5.1 Platform
Hardware-Accelerated 3D Graphics Support
\||vSo|ereV|vare|a:oarneredv||NV|Aoorov|de|ardvareba:edvC|U:Jooor|n:|de|e
v|rJa|nac||nevC|U:|norove|eqrao||c:caoab||||e:oav|rJa|nac||nebyo|oad|nqqrao||c|nen:|ve
vor||oad:oao|y:|ca|C|U|n:a||edon|evSo|ere|o:nvSo|ere|enevvC|U:Jooorarqe:V|ev
env|ronnen:|arJnqrao||c|nen:|vevor||oad::Jc|a:qrao||cde:|qnandned|ca||naq|nq
|ardvareba:edvC|U:Jooor|nvSo|ere|:||n|edoV|evenv|ronnen:rJnn|nqonvSo|ere|o::v||
:JoooredNV|AC|Ucard:reero|eV|vareConoa|b|||yCJ|deordea||:on:JoooredC|Uadaoer:
nadd||on|e|n||a|re|ea:eovC|U|::Joooredon|yv||de:|oov|rJa|nac||ne:rJnn|nq||cro:o
\|ndov:orPeero|eV|evdocJnena|onornore|norna|onon|evC|Ucaoab||||e:ovSo|ere
NOTE: vGPU support is enabled in vSphere 5.1, but the ability to leverage this feature is dependent on a future
release of View. Refer to the View documentation for information on when this feature will be available.
Guest OS Storage Reclamation
Over|ne|e:oraqereoJ|renen:ov|rJa|nac||ne:v|||c|anqe\|||e||norov|:|on|nqenab|e:J:er:o
dynan|ca||yaddcaoac|yoav|rJa|nac||nea:|::oraqereoJ|renen:|ncrea:eor|orovSo|ere|ere
was not a way to return storage to the storage array free pool when it was no longer being used by the guest
OS\||vSo|ere||:|:novoo::|b|eJ:|nq|eCJe:OSSoraqePec|ana|oneaJre\||CJe:OS
SoraqePec|ana|onv|en|e:arerenovedron|n:|de|eqJe:OS|e:|.eo|eV||||ecanberedJced
and|edea||ocaed:oraqe:oacereJrnedo|e:oraqearray:reeooo|CJe:OSSoraqePec|ana|on
J|||.e:anevS|:oar:eV|||ornaava||ab|ev||V|ev
NOTE: Guest OS Storage Reclamation is enabled with vSphere 5.1, but the ability to leverage this feature is
dependent on a future release of View. Refer to the View documentation for information on when this feature
will be available.
Improved CPU Virtualization
nvSo|ere|evSo|ere|o:|:beerab|eov|rJa||.e|eo|y:|ca|C|Uandexoo:enore|norna|onaboJ
|eC|Uarc||ecJreo|ev|rJa|nac||neT||:|norovedC|Uv|rJa||.a|onreerredoa:v|rJa||.ed|ardvare
v|rJa||.a|onV|Vorov|de:|eqJe:OSv||nearna|veacce::o|eo|y:|ca|C|UV|Venab|e:orexano|e
|erJnn|nqo||cro:o\|ndov:X||oderon|n:|dea\|ndov:orv|rJa|nac||ne
NOTE: Microsoft Windows XP Mode enables running legacy Windows XP applications that are not compatible
with newer Windows versions inside a simulated XP environment on Microsoft Windows 7 or 8.
nadd||ono|e|norovedC|Uv|rJa||.a|onv||V|VvSo|ereadd:|eab|||yoexoo:enore|ov|eve|
C|UcoJner|norna|ono|eqJe:OSv||c|enab|e:|noroveddebJqq|nqJn|nqandroJb|e:|oo|nqo
the OS and applications running inside the virtual machine. This facilitates the ability to develop, test and
oo|n|.eaoo||ca|onvor||oad:rJnn|nq|n:|deaV|varev|rJa|nac||ne
Figure 3.
T E C H NI C AL WH I T E PAP E R / 7
Whats New in VMware
vSphere 5.1 Platform
Introducing Virtual Machine Compatibility
With each new vSphere release, VMware continues to enhance virtual machine features and capabilities.
To|e|orac||eeaJre:andcaoab||||e:a::oc|aedv||aq|venv|rJa|nac||neV|vare|a:rad||ona||y
J:edav|rJa|nac||ne|ardvarever:|onnJnberA||:ov|rJa|nac||ne|ardvarever:|onnJnber:a::oc|aed
with each vSphere release is shown in the following table:
vSPHERE RELEASE VI RTUAL MACHI NE HARDWARE VERSI ON
Virtual Infrastructure 3.5 Version 4
vSphere 4.0 Version 4
vSphere 4.1 Version 7
vSphere 5.0 Ver:|on
vSphere 5.1 Version 9
Table 1. Virtual Machine Hardware Version Support Matrix
U:|nqav|rJa|nac||ne:|ardvarever:|onnJnberadn|n|:raor:canread||y|den|yeac|v|rJa|nac||ne:
feature set and capabilities. Historically, it has been considered a good practice that each time an upgrade is
nadeoavSo|ere|nra:rJcJreV|varevCenerServervCenerServeranda::oc|aedvSo|ere|o::
the virtual machine hardware version for each virtual machine is also upgraded. This would ensure that each
virtual machine had the ability to fully benet from the latest updates and newest features. However, over time
several challenges to this approach have been identied:
Uoqrad|nqav|rJa|nac||ne:|ardvarever:|onreoJ|re:oover|nqo|ev|rJa|nac||nev||c|reoJ|re:
dovn|ne\||nanyv|rJa|nac||ne:nov|o:|nqn|::|oncr||ca|vor||oad:|canbed|cJ|o
scheduledowntime
A:|e:|.eo|ev|rJa||nra:rJcJreqrov:ry|nqo|eeoa|arqenJnberov|rJa|nac||ne:rJnn|nqa
aconnonv|rJa|nac||ne|ardvarever:|onorove:d|cJ||no|norac|ca|
nnanyca:e:av|rJa|nac||ne:reoJ|renen:areJ||y:a|:edv|||eo|derv|rJa||ardvarever:|on
soavirtualmachineupgrademightyieldlittleornobenet
With these challenges in mind, and to help simplify virtual infrastructure upgrades, VMware formally extended
the virtual machine compatibility matrix in vSphere 5.0. The extended support matrix enables virtual machines
running older virtual hardware versions to run fully supported on newer versions of vSphere. The following table
shows the extended virtual machine hardware version support matrix:
vSPHERE RELEASE SUPPORTED VI RTUAL MACHI NE HARDWARE VERSI ONS
Virtual Infrastructure 3.5 Version 4
vSphere 4.0 Version 4
vSphere 4.1 Version 4, 7
vSphere 5.0 Ver:|on
vSphere 5.1 Ver:|on
Table 2. Extended Virtual Machine Hardware Version Support Matrix
T E C H NI C AL WH I T E PAP E R / 8
Whats New in VMware
vSphere 5.1 Platform
Anoab|ebeneo|eexended:Jooornar|x|:|eab|||yoJoqradeavSo|ere|nra:rJcJrevCener
Server and vSphere hosts) with no virtual machine downtime. Following the vSphere infrastructure upgrade, any
v|rJa|nac||ne:|adonoreoJ|reanyo|enevereaJre:orcaoab||||e:orov|dedv|||e|ae:ver:|oncan
con|nJeorJnv|||eo|derv|rJa||ardvarecono|ee|yJnaecedby|eJnder|y|nq|nra:rJcJreJoqrade
A||oJq||eexended:Jooornar|xre|axe:|ereoJ|renenoJoqradeav|rJa|nac||ne:|ardvarever:|on
nanyadn|n|:raor::|||e|conoe||edoJoqrade:|no|yo|eeoJov||anever|ncrea:|nqv|rJa|nac||ne
|ardvarever:|onnJnbernaneoro|e|oe||n|nae||:|aenore::Jreo|eeoJoV|vare|a:nadea
critical change to the virtual machine hardware nomenclature in vSphere 5.1 with the introduction of virtual
machine compatibility.
Virtual machine compatibility provides the means to readily identify the features and capabilities associated with
av|rJa|nac||neby|nd|ca|nq|ecorre:oond|nqvSo|erere|ea:eonv||c||ev|rJa|nac||ne|:ba:edUn|||e
the virtual hardware version number, virtual machine compatibility is tied to a specic vSphere release. For
example, a virtual machine created on vSphere 4.1 will show as compatibility level 4.x; a virtual machine
created on vSphere 5.1 will show as compatibility level 5.1. The following table shows the virtual machine
compatibility levels in vSphere 5.1:
vSPHERE RELEASE VI RTUAL MACHI NE
HARDWARE VERSI ON
vSPHERE 5. 1
COMPATI BI LI TY
Virtual Infrastructure 3.5 Version 4 V|vare|SXxand|aer
vSphere 4.0 Version 4 V|vare|SXxand|aer
vSphere 4.1 Version 7 V|vare|SXxand|aer
vSphere 5.0 Ver:|on V|vare|SXand|aer
vSphere 5.1 Version 9 V|vare|SXand|aer
Table 3. Virtual Machine Compatibility Levels In vSphere 5.1
Virtual machine compatibility removes ambiguity regarding virtual machine upgrades by eliminating the need to
associate, for example, a virtual machine running virtual machine hardware version 7 with vSphere 4.1 or one
running virtual machine hardware version 9 with vSphere 5.1.
Figure 4.
Changing Virtual Machine Compatibility Levels
S|n||aroJoqrad|nqav|rJa|nac||ne:|ardvarever:|onJ:er:cana|:oJoqraderononeconoa|b|||y|eve|o
a||q|erone|oveverav|rJa|nac||necannobedovnqradedoa|over|eve|Uoqrad|nqav|rJa|nac||ne:
conoa|b|||y|eve|doe:reoJ|redovn|nebecaJ:e|ev|rJa|nac||nenJ:beooveredo
T E C H NI C AL WH I T E PAP E R / 9
Whats New in VMware
vSphere 5.1 Platform
Setting a Default Virtual Machine Compatibility Level
To help with managing virtual machine compatibility across clusters, vSphere 5.1 enables users to dene a
default compatibility at both the host and cluster levels. This enables users to ensure that new virtual machines
created on a host/cluster are done so using the preferred compatibility level. This prevents a new virtual
machine from automatically defaulting to the highest compatibility level. It is especially useful during rolling
upgrades, when users might be running a mix of vSphere host versions together in a cluster.
Figure 5.
NOTE: In vSphere 5.1, virtual machine compatibility is available only from the new Web UI. The VMware
vSphere Client (vSphere Client), VMware vSphere Command-Line Interface (vSphere vCLI), VMware
vSphere PowerCLI (vSphere PowerCLI) and VMware vSphere Storage APIs continue to use the virtual
hardware version number.
Auto Deploy
vSo|ere|nrodJcedV|varevSo|ereAJo|eo|oyanevvayorao|d|ydeo|oynevvSo|ere|o::\||
AJo|eo|oy|evSo|ere|o:|X|boo:over|enevor|and|:connecedoanAJo|eo|oy:erverv|ere
|evSo|ere|o::ovare|:orov|:|onedd|rec|y|no|e|o::nenoryAer|evSo|ere:ovare|a:been
|n:a||edon|e|o:|eAJo|eo|oy:erverconqJre:|e|o:J:|nqaV|varevCenervCener|o:
oro|eT|en|e|o:|:connecedo|evCenerServer
AJo|eo|oy:|qn|can|yredJce:|eanoJno|nereoJ|redodeo|oynevvSo|ere|o::AndbecaJ:ean
AJo|eo|oy|o:rJn:d|rec|yronnenory|ere|:noreoJ|renenoraded|caedbood|:|T||:noon|y
provides cost savings, because there is no need to allocate boot storage for each host, but it also can simplify
|eSANconqJra|onbecaJ:e|ere|:noneedoorov|:|onand.one|UN:eac||neanev|o:|:deo|oyed
In addition, because the host conguration comes from a host prole there is no need to create and maintain
custom pre- and postinstall scripts.
A|onqv|||erao|ddeo|oynenco::av|nq:and:|no||edconqJra|onAJo|eo|oyorov|de:|e
following benets:
|ac||o:reboo|:conoarab|eoare:||n:a||T||:e||n|nae:conqJra|ondr|
\||noconqJra|ondr|beveenvSo|ere|o::|e::|nev|||be:oenroJb|e:|oo|nqandd|aqno:|nq
conguration issues.
S|no||edoac||nqandJoqrad|nqAoo|y|nqJodae:|:a:ea:ya:crea|nqanev|naqeoro|eJoda|nq|e
corre:oond|nqrJ|eon|eAJo|eo|oy:erverandreboo|nq|e|o::n|eJn|||e|yevenyoJnJ:renove
anJodaerever|nqbac|o|eorev|oJ:|naqeoro|e|:a|:oea:yPeJodae|erJ|eoa::|qn|eor|q|na|
image prole and 2) do another reboot.
T E C H NI C AL WH I T E PAP E R / 1 0
Whats New in VMware
vSphere 5.1 Platform
NOTE: Because an Auto Deploy host runs directly from memory, it often is referred to as being stateless. This is
because the host state (i.e., conguration) that is normally stored on a boot disk comes from the vCenter host prole.
nvSo|ereAJo|eo|oy:Joooredon|yoneooera|ona|nodev||c|va:reerredoa::ae|e::a|:o
|novna:d|:||e::vSo|ereexend:AJo|eo|oyv|||eadd||onovonevooera|ona|node:
stateless caching and stateful installs.
Option 1: Stateless
Auto
Deploy
Option 2: Stateless caching
Option 3: Stateful installs
Figure 6.
Stateless Caching Mode
T|eAJo|eo|oy:ae|e::cac||nqnodeva:|no|enenedo|e|oaddre::ava||ab|||yconcern:v|||e|X|
boo|nra:rJcJreandAJo|eo|oy:erver\||:ae|e::|o::||e|X|booa||edor||eAJo|eo|oy
server was unavailable, the host would not be able to boot until the outage was corrected. However, with stateless
cac||nq|a|o:cannoboodJeoaorob|env|||e|X|env|ronnenorAJo|eo|oy:erver||:ab|eoa||
bac|oboo|nqoacac|ed|naqe:avedoaded|caedboodev|ceAerboo|nqron|ecac|ed|naqe|e
adn|n|:raor|:ab|eoJ:e|e|o:o|e|oroJb|e:|ooand|den|yv|y|e|X|boon|q||avea||ed
T|e:ae|e::cac||nqnode|:very:|n||aro|e:ae|e::node|n|adJr|nqnorna|ooera|on|e|o:|X|
boo:ron|eAJo|eo|oy:erver|ovever|ed|erence|:|av||:ae|e::cac||nqanadd||ona|:eo|:
a|env|ere|e:ovare|naqerJnn|nq|nnenory|:cac|ed:avedoaded|caedboodev|ce|oca|d|:|
SANUS|T||:cac|ed|naqe|enac:a:abac|Joronv||c||e|o:canboo|n|eeven|ere|:a
orob|env|||e|X|booorAJo|eo|oy|nra:rJcJre
Figure 7.
Un|||e|e:ae|e::node:ae|e::cac||nqreoJ|re:aded|caedboodev|ceoreac|vSo|ere|o:nadd||on
J:er:nJ:conqJre|e|o::|OS:e|nq:or:aenoobooover|enevor|and||aa||:oa||
bac|oboo|nqrond|:|
T E C H NI C AL WH I T E PAP E R / 1 1
Whats New in VMware
vSphere 5.1 Platform
\||:ae|e::cac||nq||ere|:a|oca||.edoJaqe|aaec:|e|X|boo|nra:rJcJre||C|orT|T|
:erveror|eAJo|eo|oy:erverbJdoe:noaec|evCenerServer|n:ancebyJ:|nq|ecac|ed|naqe
|e|o:v|||beab|eobooand|eadn|n|:raorab|eonanJa||yreconneco|evCenerServer
NOTE: Stateless caching does not protect against a vCenter Server failure. Always protect a vCenter Server by
running it in a vSphere cluster protected by VMware vSphere High Availability (VMware HA) or VMware
vCenter Server Heartbeat (vCenter Server Heartbeat).
Stateful Install Mode
AJo|eo|oy:aeJ||n:a||nodeenab|e:adn|n|:raor:o|everaqe|eAJo|eo|oy|nra:rJcJreoorov|:|on
nevvSo|ere|o::\||:aeJ||n:a||J:er:oerornaone|ne|X|boooanev|o:ron|eAJo|eo|oy
:erver|o||ov|nq|eone|ne|X|booa||:Jb:eoJenreboo:v|||a|eo|aceron|eded|caedbood|:|
Se|nqJo:aeJ||n:a||:|::|n||aroconqJr|nq:ae|e::cac||nqT|ed|erence|:|e|OSbooorder
conqJredon|e:erver\|ere:ae|e::cac||nq|::eobooron|enevor|r:anda||bac|o|e|oca|
d|:|on|yv|en|e|X|booa||:v||:aeJ||n:a||:|e|o:|:conqJredoa|vay:ryobooron|e|oca|
d|:|r:andbooron|enevor|on|yv|ennoboo|naqecanbeoJndon|ed|:|\||AJo|eo|oy
:aeJ||n:a||nodeanev|o:v|||oerornan|n||a|one|ne|X|booJ:|nq|eAJo|eo|oy|nra:rJcJre
oconqJre|e|o:Aer|e|n||a|booa||:Jb:eoJenreboo:a|eo|aceJ:|nq|eboodev|ce
Figure 8.
\||:aeJ||n:a||:|eAJo|eo|oy|nra:rJcJre|:be|nq|everaqeda:aorov|:|on|nqoo|:|n||ar|yo|ov
:cr|oed|n:a||a|on:or||c|:arn|q|beJ:edT|eadvanaqeoAJo|eo|oy:aeJ||n:a|||:|aJ:er:are
able to rapidly deploy hosts without having the need to create and maintain custom scripts. The software to be
|n:a||ed|:deern|nedJ:|nq|eAJo|eo|oyrJ|e:enq|neand|e|o:|:conqJredJ:|nq|evCener|o:
oro|e:and|ereoredoe:nre|yonexerna|:cr|o:
\||:aeJ||n:a||:J:er:|everaqe|eAJo|eo|oy|nra:rJcJreoorov|:|onnev|o::bJorqono:o|e
benets of stateless or stateless caching because after the vSphere hosts have been deployed, they must be
maintained, patched and updated individually.
Remote Logging and Dump Collection
|ecaJ:eAJo|eo|oy|o::rJnn|nq|n|e:ae|e::or:ae|e::cac||nqnoderJnd|rec|yronnenory
|:|nooranoenab|erenoe|oqq|nqand:eJorenoedJnoco||ec|on\||oJrenoe|oqq|nqordJno
co||ec|on|oq|e:anddJno:v|||be:oredonaPA|d|:||nnenoryandv|||be|o:eac||ne|e|o:
is rebooted.
To|e|ov||renoe|oqq|nqanddJnoco||ec|onV|vareorov|de:voAJo|eo|oyaddonconoonen:
|eSy:|oqCo||ecorand|e|SX||JnoCo||ecor|o|o|e:eaddonconoonen:arereeoc|arqeand
areorov|deda:oaro|evCener|n:a||a|onned|a
T E C H NI C AL WH I T E PAP E R / 1 2
Whats New in VMware
vSphere 5.1 Platform
NOTE: The VMware vCenter Server Appliance (VMware VCSA) comes with the Auto Deploy Server, Syslog
Collector and ESXi Dump Collector preinstalled. It is not necessary to install these components when using the
VCSA. Users simply must enable them with the VCSA conguration interface.
Improved Scalability
nvSo|ereoo|n|.a|on:|avebeennadeo|evay|e|o:|naqe|:oa::edron|eAJo|eo|oy:erver
o|e|o:enab||nqJooconcJrren|o:reboo:rona:|nq|eAJo|eo|oy:erver
NOTE: To scale beyond 80 concurrent reboots per Auto Deploy host, use reverse Web proxies.
Conclusion
VMware vSphere 5.1 introduces many new features and enhancements that further extend the core capabilities
of the vSphere platform. The core platform enhancements in vSphere 5.1 include the following:
noroved:ecJr|yandaJd||nqbyrenov|nqre||anceona:|aredrooaccoJn
norovedSN||non|or|nqv||SN||vaJ|en|ca|onandSS|encryo|on
|n|ancedv|o|on:Jooorenab||nqv|rJa|nac||ne:oben|qraedbeveen|o::andc|J:er:|adono
have shared storage
SJoooror|e|ae:ne|andA||C|U:a|onqv||:Joooror||cro:o\|ndov:
|Jnd||nqoV|varevS||e|d|ndoo|na:oaro|ecorevSo|ereorodJc
A|onqv|||ecoreo|aorn|norovenen:vSo|ereorov|de:|eo||ov|nq:evera|v|rJa|nac||nere|aed
enhancements:
SJooororJoovC|U:oerv|rJa|nac||nedoJb||nq|enJnbero:JooorvC|U:ronvSo|ere
|n|ancedC|Uv|rJa||.a|onenab||nq|eoa::|nqo|ov|eve|C|UcoJner:ando|ero|y:|ca|C|Uar|bJe:
directly to the virtual machine, where they can be accessed by the guest OS
nrodJc|onov|rJa|nac||neconoa|b|||yna||nq|ea:|ero|den|yandrac|v|rJa|nac||necaoab||||e:
renove:anb|qJ|yreqard|nqv|rJa|nac||neJoqrade:and|e|o:e||n|naeore::Jreo|eeoJov||an
ever-increasing virtual hardware version
For VMware View environments, vSphere 5.1 puts in place the following critical enabling technologies that will be
used with future releases of View:
|n|anced|ardvareacce|eraedqrao||c::Jooorv||v|rJa|C|U:vC|U:
CJe:OSPec|ana|onorov|d|nq|eab|||yoreJrndea||ocaed:oraqe:oace|n:|de|eqJe:OSo|e
storage array
vSo|erea|:oorov|de::evera|cr||ca|en|ancenen:oV|varevSo|ereAJo|eo|oy
noroved:ca|ab|||yo|eAJo|eo|oy:erverv||:JooororJooconcJrrenreboo:v|ce|e
number of concurrent reboots with vSphere 5.0
Anev:ae|e::cac||nqnode|aenab|e:|eAJo|eo|oy|o:oreboo|n|eevenoanoJaqeaec|nq
|e|X||nra:rJcJreorAJo|eo|oy:erver
Anev:aeJ||n:a||node|aenab|e:|eAJo|eo|oy|nra:rJcJreobeJ:eda:aorov|:|on|nqoo|o
deploy new vSphere hosts

VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com
Copyright 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed
at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be
trademarks of their respective companies. Item No: VMW-WP-WHATS-NEW-PLTFRM-USLET-101 Docsouce: OIC-12VM007.04