vMotion - absentee-neptune/SYS-350 GitHub Wiki

Create TEST01 VM

  • On the ESXI1 host (10.0.17.20) in the cluster, create a new VM called TEST01
    • Set the OS family to Linux and the OS to CentOS 7
    • Set the Hard Disk to 2GB
    • This VM will not have the CD Drive connected, so no .iso file
    • This VM will be connected to Management Network
  • Start the VM once ready

Verify Nested Hosts Configuration

  • On each Nested-ESXi host, verify that there is a VMkernel adapter labeled vMotion with an IP of 10.0.17.3X and the vMotion service enabled
  • On the Nested-ESXi cluster, make sure DRS is enabled and that it is set to Fully Automated

Migrate

  • Right-click on TEST01 on press Migrate
    • Select Change both compute resource and storage as the migration type
    • Select the ESXI2 host (10.0.17.21) as the compute resource
    • Select a datastore to transfer the VM storage
    • Leave the default Network Settings
    • Leave the default vMotion priority settings
    • Select Finish when ready
  • Pay close attention to the VM Console, Recent Tasks (Bottom of Screen), Cluster Stats, and the Power Status of the VM
    • What changes?
    • What Stays the Same?

Observed Processes with Migration

  • When the migration completes, the following is observed:
    • The set host on the TEST01 VM summary page changes to the destination host set during migration
    • The power status of the VM surprisingly did not change, yet I would think the VM would require a reboot anyway after a host change
    • Only one task popped up in the Recent Task section of the vCenter console, Relocate virtual machine, with the target being the TEST01 VM
    • When looking at the Recent Task section of the Nested-ESXi1 console, only Refresh Network System popped up as a task
    • When looking at the Recent Task section of the Nested-ESXi2 console, Refresh Network System and Register VM popped up as tasks
    • A spike in CPU usage was seen in both Nested-ESXi hosts, but the destination host CPU spike was higher than the source host during migration

Milestone Completion

Reflection