“Nutanix Controller VM (CVM) is what runs the Nutanix software and serves all of the I/O operations for the hypervisor and all VMs running on that host.” Nutanix-bible.

The Controller VM recourses are shown under the VM page In the Nutanix Prism, but you will not be able to change the resources configuration, unless you connected to the Acropolis hypervisor (Host) and modified the configurations using virsh.

“virsh: is a command line interface tool for managing guests and the hypervisor.” Centos.org.

clip_image002

clip_image003

Connect to the Acropolis hypervisor (Host) using the root account with password “nutanix/4u”

clip_image005

Displays information about the host > virsh nodeinfo

clip_image006

Lists all the VMs on a host > virsh list –all

clip_image007

Displays information about a VM > virsh dominfo VM_Name

clip_image008

Displays information about the vCPU > virsh vcpuinfo VM_Name

clip_image009

Sets the number of virtual processors > virsh setvcpus VM_name count

Note: The count value cannot exceed the number of processors specified for the guest”

clip_image011

You can increase the number of processors by editing the virsh XML configuration file > virsh edit VM_Name

Ø Change from command mode to insert mode by typing <i>.

Ø Use the arrow keys to move to line “vcpu placement”, increase the value as required.

Ø Go back to command mode by pressing <Esc>.

Ø Save and exit by Typing <:wq>

clip_image012

clip_image014

Allocates memory for a guest > virsh setmem VM_Name count

You must specify the [count] in kilobytes. The new count value cannot exceed the amount you specified when you created the guest. A higher maximum memory value will not affect the active guest unless the new value is lower which will shrink the available memory usage.

clip_image015

clip_image016

clip_image017

Sets the maximum memory limit for a guest > virsh setmaxmem VM_Name

clip_image018

clip_image019

Shutdown the VM > virsh shutdown VM_Name

clip_image020

clip_image022

Starts an inactive VM > virsh start VM_Name

clip_image023

Restarts the VM > virsh reboot VM_Name

clip_image024

Reference:

Recommended Community Edition Hardware

Component

Minimum Requirement

CPUs

Intel CPUs with VT-x support.

4 core minimum; 2 cores dedicated to the Controller VM

System memory

  • 16 GB minimum
  • 32 GB or greater recommended for NOS features such as deduplication/compression or more user VMs

CentOS – Managing guests with virsh.

https://www.centos.org/docs/5/html/5.2/Virtualization/chap-Virtualization-Managing_guests_with_virsh.html

Advertisements