Migrating Virtual Machines. Flashcards
ESXi Host And VM Requirements for VMotion.
VMotion moves the state of the VM without disrupting the user. State of the VM:
1. Settings: Settings in "Edit Settings" tab. VMX file. 2. Disk: VMDK and compatibility RDMs. 3. Memory: Active memory on VM.
Each of the three are handled differently:
Settings are easy.
Disk requires shared storage.
Memory: Copied gradually.
Host Requirements:
- Source and destination hosts must both have access to shared storage used VM.
- All hosts must have access to at least 1 Gbps Ethernet Adapter,
- Source and destination must have access to the same physical network or VLAN.
- Source and destination hosts must have VMKernel ports configured on vSS or vDS that are enabled for vMotion. (cross-swtich vMotion: vMotion from one vDS to another).
- Host CPUs must be the same vendor and family .
VM Requirements:
- VMs cannot have a connection to an internal switch.
- VMs cannot connection to a virtual device with a local image mounted (CD, floppy).
- VMs must not have CPU affinity configured.
- If VM swap file is not accessible to the destination host, vMotion must be able to create a swap files accessible to the destination host before migration can begin.
- IF VM has an RDM, the RDM must be accessible to the destination host as well.
ESXi Host And VM Requirements for Storage VMotion.
In Storage vMotion, VM’s state doesn’t move at all. What is copied are the files that the VM is using. (?:Pg.647)
- You can perform storage maintenance and reconfiguration without VM downtime.
- You can redistribute storage loads without VM downtime.
- You can evacuate physical storage without VM downtime.
Storage type independent.
Enhanced vMotion (Cross-Host vMotion).
- Can migrate a VM to a new host at the same time that the files are migrating to another datastore.
- Perform a migration of a VM from one host to another without having shared datastore between hosts.
Enhanced vMotion (Cross-Host vMotion) CPU Requirements.
CPU Feature set:
- Host CPU vendor, family and model.
- BIOS settings that might disable CPU features.
- ESXi version running on the host.
- VM’s virtual hardware version.
- VM’s guest OS.
EVC Cluster Requirements:
- All VMS with better feature set must be migrated off the cluster.
- All hosts in cluster must have CPUs from the same vendor.
- All hosts in cluster must be running ESXi 3.5U2.
- All hosts must hardware virtualization enabled (Intel-VT or AMD-V) and AMD NoeXecute or Intel eXecute Disable enabled in BIOS.
- All hosts in cluster must be configured for vMotion.
- All hosts in cluster must have supported CPUs for the EVC mode you want.
Long-Distance vMotion
- Must Enterprise Plus vSphere license.
- Latency round-trip (RTT) must be 150 ms or less.
- Both hosts must exist in the same Layer 2 environment, same VXLAN-based technology such as NSX must be used.
Snapshot Requirements for vMotion/Storage vMotion Migration.
vSphere 6.0 you can use Storage vMotion on VMs that have snapshots. Allows Storage DRS. Pg. 655.
Migrating Virtual Machines Using vMotoin/Storage vMotion.
vMotion implies that VMs are powered on. Shutting VM down before migrating is cold migration.
Migrating a VM’s Files Using Storage vMotion.
Storage vMotion does not move the VM state but moves the files that the VM is using, while its using them, from one physical storage area to another.
Configuring VM Swap File Location.
Size is equal to available memory of the VM minus the reservation assigned to it.
Swap file created on the source host must be visible to the destination host before the migration can begin. This usually means that the VM swap file is stored in the same location with the other VM files.
Figures 17-11,17-12 and 17-13 show places swap file location can be configured.
17-11 Per Cluster.
17-12 Per Host.
17-13 Per VM.
Migrating a Powered-Off or Suspended VM.
A suspended VM is still running a CPU instruction set. and must meet COU compatibility requirements as though it were being vMotioned.
Can migrate VM’s state to another host at the same time you migrate its files to another datastore.
Utilizing Storage vMotion Techniques.
Can use Storage vMotion to change VMDK from thick-provisioned eager-zeroed to thin-provisioned, e.g.