VS5ICM_M07_VMManagement

7/30/2019 VS5ICM_M07_VMManagement

1/67

Virtual Machine Management

Module 7

2011 VMware Inc. All rights reserved


2/67

You Are Here

Course Introduction

Introduction to Virtualization

Virtual Machines

Data Protection

Access & Authentication Control

Resource Management and Monitoring

7-2


VMware vSphere: Install, Configure, Manage Revision A

Configure and Manage Virtual Networks

Configure and Manage Virtual Storage

Managing Virtual Machines

Scalability

Patch Management

Installing vSphere Components


3/67

Importance

You must perform many cumbersome tasks when using physicalmachines. For example, you must move server storage from onestorage array to another, deploy servers with the same configuration,

and add resources dynamically.To address these issues and more, VMware vSphere 5 providesmethods for you to add memory and expand virtual machine diskdrives.

7-3



The ability to clone and deploy virtual machines from a templateenables you to capture the state of a problematic virtual machine ordeploy a virtual machine from a pre-configured standard.

Also, vSphere 5 gives you the ability to migrate virtual machines and

virtual machine disks from one VMware ESXi host to anotherwhile the virtual machines are running.


4/67

Module Lessons

Lesson 1: Creating Templates and Clones

Lesson 2: Modifying Virtual Machines

Lesson 3: Migrating Virtual MachinesLesson 4: Creating Virtual Machine Snapshots

Lesson 5: Creating a vSphere vApp and Registering a VirtualMachine

7-4




5/67

Lesson 1:Creating Templates and Clones

7-5




6/67

Learner Objectives

After this lesson, you should be able to do the following:

Create a template.

Deploy a virtual machine from a template.

Clone a virtual machine.

Allow guest operating system customization by VMware vCenter

7-6



Server.


7/67

Using a Template

A template is a master copy ofa virtual machine used to

7-7



crea e an prov s on newvirtual machines.

The template is an image thattypically includes a guestoperating system, a set of

applications, and a specificvirtual machine configuration.


8/67

Creating a Template

Clone the virtual machine to atemplate.

The virtual machine can eitherbe powered on or powered off.

Convert the virtual machine to atemplate.

The virtual machine must bepowered off.

7-8



Clone a template.

Select the template ininventory first.


9/67

Viewing Templates

Two ways to view templates:

Use the VMs and Templates inventory view.

Use the Virtual Machines tab in the Hosts and Clusters inventoryview.

7-9




10/67

Deploying a Virtual Machine from Template

To deploy a virtual machine, you must provide such information asthe virtual machine name, inventory location, host, datastore, andguest operating system customization data.

7-10




11/67

Updating a Template

To update a template:

1. Convert thetemplate to a

virtual machine.2. Place the virtual

machine on anisolated network

7-11



access.3. Make appropriate

changes to thevirtual machine.

4. Convert the

virtual machine toa template.


12/67

Cloning a Virtual Machine

Cloning is analternative to

deploying a virtualmachine.

A clone is an exact

7-12



machine.

The virtual machinebeing cloned caneither be powered on

or powered off.


13/67

Customizing the Guest Operating System

VMware recommends customization of a clones guestoperating system to prevent software and network conflicts.

During cloning or deploying from template, you have the optionof running the Guest Customization wizard.

The wizard lets you create a specification that you can use to

7-13



prepare t e guest operat ng systems o v rtua mac nes.

Specifications can be stored in the database.

You can edit specifications in the Customization SpecificationsManager.


14/67

Deploying Virtual Machines Across Datacenters

Virtual machinedeployment is allowed

across datacenters. Clone a virtual

machine from onedatacenter to

7-14



anot er.

Deploy from atemplate in onedatacenter to avirtual machine in a

different datacenter.


15/67

Lab 10

In this lab, you will deploy a virtual machine from a template andclone a virtual machine.

1. Create a template.

2. Copy Sysprep files to the vCenter Server appliance.

3. Create Customization Specifications.

7-15



4. Deploy a virtual machine from a template.5. Clone a virtual machine that is powered on.


16/67

Review of Learner Objectives

You should be able to do the following:

Create a template.

Deploy a virtual machine from a template.

Clone a virtual machine.

Allow guest operating system customization by vCenter Server.

7-16




17/67

Lesson 2:Modifying Virtual Machines

7-17




18/67

Learner Objectives


Describe virtual machine settings and options.

Add a hot-pluggable device. Dynamically increase the size of a virtual disk.

Add a raw device mapping (RDM) to a virtual machine.

7-18




19/67

Modifying Virtual Machine Settings

You can modify a virtualmachines configuration in itsProperties dialog box:

Add virtual hardware.

Some hardware can be addedwhile the virtual machine is

7-19



.

Remove virtual hardware.

Set virtual machine options.

Control a virtual machinesCPU and memory resources.

Create an RDM.


20/67

Hot-Pluggable Devices

Examples of hot-pluggable devices: USB

controllers, Ethernetadapters, and hard diskdevices.

7-20



and memory while thevirtual machine ispowered on.


21/67

Create an RDM

To create an RDM:

1. Edit Settings to modify the virtual machine configuration.

2. Click the Add button to add a device.

3. Click Hard Disk.4. Select Raw Device Mappings and complete the Add Hardware wizard

information by defining the following items:

-

7-21



Mapped datastore - Storethe RDM file with the virtual

machine or on a different

datastore

Compatibility mode Virtual device node


22/67

Dynamically Increasing a Virtual Disks Size

Increases the size of theexisting virtual disk file.

7-22



Dynamically increase avirtual disk from, for

example, 2GB to 20GB.


23/67

Virtual Machine Options

guest operatingsystem type

VM directory

.vmx file location

VM display name

7-23




24/67

Options: VMware Tools

When to runVMware Tools

scripts

Customize powerbutton actions.

7-24



Updatechecks andtime sync.


25/67

Advanced: Boot Options

Advanced options rarely need to be set.

Delay power on.

7-25



Boot into BIOS.

Retry after failedboot.


26/67

Lab 11

In this lab, you will modify a virtual machines hardware and add araw LUN to a virtual machine.

1. Increase the size of a VMDK file.

2. Adjust memory allocation on a virtual machine.

3. Rename a virtual machine in the vCenter Server inventory.

7-26



4. Add a raw LUN to a virtual machine and verify that the guestoperating system can see it.

5. Expand a thin-provisioned virtual disk.


27/67



Describe virtual machine settings and options.

Add a hot-pluggable device.

Dynamically increase the size of a virtual disk.

Add an RDM to a virtual machine.

7-27




28/67

Lesson 3:Migrating Virtual Machines

7-28




29/67

Learner Objectives


Describe the types of migration.

Explain the importance of VMware vSphere vMotion.

Identify vMotion requirements (Virtual machine, Host).

Verify vMotion requirements (CPU constraints and guidelines).

7-29



Perform a vMotion migration.


30/67

Migrating Virtual Machines

Migration Moving a virtual machine from one host or datastoreto another. Types of migrations:

Cold Migrate a virtual machine that is powered off.

Suspended Migrate a virtual machine that is suspended.

vMotion Migrate a virtual machine that is powered on.

vSphere Storage vMotion Migrate a virtual machines files,

7-30



Concurrent migrations are possible:

A host can be involved in up to two migrations with vMotion orStorage vMotion at one time.

A maximum of eight simultaneous vMotion, cloning, deployment,

or Storage vMotion accesses to a single VMFS-5 datastore issupported.


31/67

Comparison of Migration Types

Migrationtype

VM powerstate

Changehost/datastore?

Acrossvirtualdatacenters?

Sharedstoragerequired?

CPUcompatibility?

Cold Off

Host or

datastoreor both

Yes No

Different CPU

familiesallowed

Sus ended Sus endedHost ordatastore Yes No

Must meetCPU

7-31



or both

requirements

vMotion On Host No Yes

Must meetCPUcompatibilityrequirements

StoragevMotion

On Datastore No No N/A


32/67

vMotion Migration

A vMotion migration movesa powered-on virtualmachine from one host toanother.

vMotion can be used to: Improve overall hardware

utilization

7-32



machine operation whileaccommodatingscheduled hardwaredowntime

Allow vSphere DistributedResource Scheduler(DRS) to balance virtualmachines across hosts

H M i Mi i W k


33/67

How vMotion Migration Works

vMotion

VM A(network =

Production)

7-33



network

Productionnetwork

Vi t l M hi R i t f M ti Mi ti


34/67

Virtual Machine Requirements for vMotion Migration

A virtual machine must meet the following requirements:

A virtual machine must not have a connection to an internal vSwitch

(vSwitch with zero uplink adapters). A virtual machine must not have a connection to a virtual device (such

as a CD-ROM or floppy drive) with a local image mounted.

7-34



.

If the virtual machines swap file is not accessible to the destinationhost, vMotion must be able to create a swap file accessible to the

destination host before migration can begin.

If a virtual machine uses an RDM, the RDM must be accessible by the

destination host.

H t R i t f M ti Mi ti


35/67

Host Requirements for vMotion Migration

Source and destination hosts must have:

Visibility to all storage (Fibre Channel, iSCSI, or NAS) used by thevirtual machine:

128 concurrent vMotion migrations per VMFS datastore At least a Gigabit Ethernet network:

Four concurrent vMotion migrations on a 1Gbps network

7-35



g concurren v o on m gra ons on a ps ne wor

Access to the same physical networks

Compatible CPUs:

CPU feature sets of both the source and destination host must becompatible.

Some features can be hidden by using Enhanced vMotion Compatibility(EVC) or compatibility masks.

CPU Constraints on vMotion Migration


36/67

CPU Constraints on vMotion Migration

CPU characteristics Exact match required? Why or why not?

Clock speeds, cache sizes,hyperthreading, and number

of cores

No Virtualized away by VMkernel

Manufacturer (Intel or AMD)Family (P4, Opteron)

YesInstruction sets contain manysmall differences.

Presence or absence of

7-36



SSE3, SSSE3, or SSE4.1

instructions

Yes

directly by applications

Virtualization hardwareassist

For 32-bit VMs: No Virtualized away by VMkernel

For 64-bit VMs on Intel:

Yes

The VMware Intel 64-bit

implementation leverages VT.

Execution-disable(NX/XD bit)

Yes (but customizable)Guest operating system relieson NX/XD bit if detected.

Exposing or Hiding NX/XD


37/67

Exposing or Hiding NX/XD

7-37



Choose between NX/XD security featuresor broadest vMotion compatibility.

For future CPU features,edit mask at the bit level.

Identifying CPU Characteristics


38/67

Identifying CPU Characteristics

Theimagec annotbe displayed.Your computer may nothave enough memory to open theimage,or theimage may havebeen corrupted.Restartyour computer,and then open thefileagain. Ifthe red x stillappears,you may haveto deletetheimageand then insertit again.

7-38



To identify CPU characteristics, use theserver and CPU specifications, or use

the VMware CPU identification utility.

Verifying vMotion Layout: Virtual Machine Map


39/67

Verifying vMotion Layout: Virtual Machine Map

7-39



Checking vMotion Errors


40/67

Checking vMotion Errors

7-40



Storage vMotion


41/67

Storage vMotion

Storage vMotion allows you to: Perform storage maintenance

and reconfiguration

Redistribute storage load

Evacuate physical storage

soon to be retired

Perform storage tiering

VMkernel

7-41



Upgrade ESXi hosts without virtual

machine downtime

Storage vMotion isstorage-type independent.

Source and destination can bedifferent storage types.

Storage vMotion

Storage vMotion in Action


42/67

Storage vMotion in Action

mirror driver

data mover

vpx vpx

read/write I/Oto virtual disk

Initiate storage migration.

Start a new virtual machineprocess (VPX).

Mirror I/O calls to file blocksthat have already been copiedto virtual disk on the

7-42



.

Copy data using the VMkerneldata mover or vSphere StorageAPIs - Array Integration (VAAI).

Cut over to the destination VPXprocess to begin accessing thevirtual disk copy.

destinationdatastore

sourcedatastore

VAAI

storage array

Migrate Virtual Machine Wizard


43/67

Migrate Virtual Machine Wizard

vMotion

You can use the Migrate Virtual Machine wizard to perform bothhot and cold migrations.

7-43



Storage vMotion

Cold migration;Function available

when virtual machineis powered off

Storage vMotion Guidelines and Limitations


44/67

g

Guidelines:

Plan and coordinate with administrators.

Perform during off-peak hours.

Ensure that source host has access both to source datastores andtarget datastores.

7-44



m tat ons:

Virtual machine disks must be in persistent mode or be RDMs.

The virtual machine must be powered off to concurrently migrate toanother host and datastore.

Lab 12


45/67

In this lab, you will use vMotion to migrate virtual machines.

1. Create a virtual switch and VMkernel port group for vMotion

migration.2. Verify that your ESXi host meets vMotion requirements.

3. Verify that your virtual machines meet vMotion requirements.

7-45



4. Perform a vMotion migration of a virtual machine.

5. Migrate virtual machine files with Storage vMotion.



46/67

j


Describe the types of migration.

Explain the importance of vMotion. Identify vMotion requirements (virtual machine, host).

Verify vMotion requirements (CPU constraints and guidelines).

7-46



Perform a vMotion migration.


47/67

Lesson 4:Creating Virtual Machine Snapshots

7-47



Learner Objectives


48/67


Take a snapshot of a virtual machine and manage multiple

snapshots. Delete virtual machine snapshots.

7-48



Virtual Machine Snapshots


49/67

Snapshots allow you to preserve the state of the virtual machine, soyou can return to the same state repeatedly.

For example, if you make changes while testing software, snapshotsallow you to back out of those changes.

7-49



Virtual Machine Snapshot Files


50/67

A snapshot consists of a set of files: the memory state (.vmsn), thedescription file (-00000#.vmdk), and the delta file (-00000#-delta.vmdk).

The snapshot list file (.vmsd) keeps track of the virtual machines

snapshots.

7-50



How Do Virtual Machine Snapshots Work?


51/67

Virtual machine snapshots employa copy-on-write mechanism.

Virtual machine snapshots containchanged blocks only.

Default space allocation for asnapshot is 16MB.

Security Patch1.0.1

Security Patch

2.0

Virtual machinewrites here.

7-51



Base Image

Security Patch1.0

flat-vmdk

VMFS

16MB

Taking a Snapshot


52/67

pending

transaction

s

committedtodisk

.vmdk

7-52



You can take a snapshot while a virtual machine is powered on,powered off, or suspended.

A snapshot captures the entire state of the virtual machine:

Memory state, settings state, and disk state

A snapshot is not recommended for backup and recovery!

Managing Snapshots


53/67

The SnapshotManager lets youreview allsnapshots for the

active virtualmachine and acton them directly:

Reverted fromSecurity Patch 2.0 toSecurity Patch 1.0.1

7-53



Revert to (Go to)

a snapshot.

Delete one or allsnapshots.

Delete a Virtual Machine Snapshot (1 of 3)


54/67

base disk (5GB)

You are here.snap01 delta (1GB)

base disk (5GB) +base disk (5GB) +snap01 datasnap01 data

7-54



snap02 delta (2GB)



55/67

base disk (5GB)

You are here.snap01 delta (1GB)

snap01 delta (1GB) +

7-55



snap02 delta (2GB)



56/67

base disk (5GB)

snap01 delta (1GB)

You are here.

7-56



snap02 delta (2GB)

Delete All Virtual Machine Snapshots


57/67

You are here.

base disk (5GB)

snap01 delta (1GB)

base disk (5GB) +base disk (5GB) +snap01/02 datasnap01/02 data

7-57



snap02 delta (2GB)

Insufficient Space to Store Snapshot Files


58/67

A

R

R

AY

VMFS-01

server A20GB

VMDK-1

BaseDisk

Delta Disk

20GB

BaseDisk

7-58



The delta files might expand and use all free space available on the LUN

When committing a large delta disk fails, try the following:

Clone the virtual machine to a datastore that has more space. Relocate the disk(s) of other virtual machines with cold migrationto another

datastore.

Relocate templates.

VMFS-02

VMDK-1



59/67


Take a snapshot of a virtual machine and manage multiplesnapshots.

Delete virtual machine snapshots.

7-59




60/67

Lesson 5:Creating a vApp and Registering a

Virtual Machine

7-60



Learner Objectives


61/67


Describe a vApp.

Build a vApp.

Manage virtual machines using vApp.

Remove a virtual machine from the vCenter Server inventory andcompletely from disk.

7-61



Manage virtual machine snapshots.

Managing Virtual Machines with vSphere vApp (vApp)


62/67

A vApp:

Is a container for one ormore virtual machines

Can be used to package andmanage related applications

7-62



Is an object in the vCenterServer inventory

vApp Characteristics


63/67

You can configurea vApp:

CPU andmemoryallocation

IP allocationpolicy

7-63



Advancedsettings

You can alsoconfigure thevirtual machinestartup andshutdown order.

Remove a Virtual Machine


64/67

Two ways to remove a virtualmachine:

Remove a virtual machine fromthe inventory.

Unregisters virtual machine The virtual machines files remain

on disk.

7-64



The virtual machine can later beregistered (re-added) to theinventory.

Delete a virtual machine fromdisk.

The virtual machine is removedfrom the inventory, and its filesare permanently deleted fromdisk.

Lab 13


65/67

In this lab, you will perform several virtual machine managementtasks.

1. Unregister a virtual machine in the vCenter Server inventory.2. Register a virtual machine in the vCenter Server inventory.

3. Unregister and delete virtual machines from disk.

7-65



4. Take snapshots of a virtual machine.

5. Revert to a snapshot.

6. Delete an individual snapshot.

7. Use the Delete All function in Snapshot Manager.



66/67


Describe a vApp.

Build a vApp.

Manage virtual machines using vApp. Remove a virtual machine from the vCenter Server inventory and

completely from disk.

7-66



Manage virtual machine snapshots.

Key Points


67/67

You can use several methods to create a virtual machine. Choosethe method that best fits your needs.

Deploying virtual machines from a template allows you to easily

create many virtual machines. vCenter Server provides useful features for provisioning virtual

machines, such as templates and cloning.

7-67



VS5ICM_M07_VMManagement

Documents

Transcript of VS5ICM_M07_VMManagement