Get experience using VM management tasks from Prism, which include power actions, searching, cloning, and migrating.
Now that you have a couple VMs deployed, let’s have some fun and explore some of the VM management tasks with AHV.
Explore VM power actions and console access.
In Prism Central > Explore > VMs.
Locate the Linux VM you created in the previous lab (Linux_VM-initials). (Use Prism’s search function if necessary)
Note
Note that the Power State column for that VM shows a red dot, indicating that the VM is powered off.
Now lets power on the VM:
Select the VM, then click Power On from the Actions drop-down menu.
Note
See the list of available actions (Update, Delete, Clone, Launch Console, Power On, Pause/Suspend, Snapshot, Migrate, and so on). Note that Launch Console is shaded. This action is not available because the VM is off.
Next lets open a console session:
Select the VM, then click Launch Console from the Actions drop-down menu.
Note
When the console window opens, note that there are three actions available in the console (Send CTRL-ALT-DEL, Take Screen Capture, and Power).
Power On in the Actions menu changes to Power Off once the VM has been powered on. You can also click on the name of the VM to open a console window for a specific VM. This console window contains all of the options available under the Actions menu, performance-related information, and other relevant VM details.
Note
In ESX:
The Prism search function makes it easier to identify problems or find feature documentation in Prism Central. Use Prism Central’s search capabilities by typing a few search queries to see how easy this can make the tasks above.
Suggestions:
In Prism Central > .
Note
The search hot key (a slash mark, or /) can be used from anywhere in the Prism Central UI to bring up the search function.
In Prism Central > Explore > VMs.
Find and clone four copies of the CentOS-base virtual machine.
Select the VM, then click Clone from the Actions drop-down menu.
Fill out the following fields and click Save:
Leave them powered off as they are used in the optional Flow Lab.
In Prism Central > Explore > VMs.
Locate the Linux Vm from the previous lab (Linux_VM-initials).
You should see that it has no entry in the Host column when it is powered off.
Power on the VM, and make note of the Hosts Name in the Host column.
Select the VM, then click Migrate from the Actions drop-down menu.
You can either choose one of the other hosts in the cluster as a migration target for the VM, or accept the default and let AHV automatically select a location.
Click Migrate to finalize the action.
When the task completes, verify that your VM host location has changed from the host recorded above to the new location you selected.
In Prism Central > Explore > VMs.
Locate the Linux Vm from the previous lab (Linux_VM-initials).
Select the VM, then click Configure VM Host Affinity from the Actions drop-down menu.
Select one Host to which the VM can have affinity, and click Save to finish.
Power On the VM, and verify it is on the Host you selected in the affinity policy.
Select the VM, then click Migrate from the Actions drop-down menu.
Click Cancel to exit migration.
Select the VM, then click Configure VM Host Affinity from the Actions drop-down menu.
Select another Host to which the VM can have affinity, and click Save to finish.
Select the VM, then click Migrate from the Actions drop-down menu.
Either select a host manually or allow AHV to select it, then click Migrate.
You should see that the VM has moved to the other host.
High availability is enabled by default for AHV and will restart VMs in a best-effort manner in the event of a host failure. Additional configuration can set resource reservations to ensure there is capacity during an HA event.
VMware HA works by providing high availability for virtual machines by pooling the virtual machines and the hosts they reside on into a cluster. The hosts in that cluster are then monitored and in case there is a failure, the VMs residing on the failed host would get restarted on alternate hosts. This feature must be turned on in vSphere, as opposed to AHV where it’s on by default without reservation.