An administrator is configuring Playbooks and is concerned about adding or reducing CPU and memory...

When configuring Playbooks to automate the scaling of CPU and memory resources for VMs, the administrator should consider the following prerequisites:

CPU can be added to a powered on VM if the guest OS supports it. This is also known as hot-plug CPU. The administrator should check the compatibility of the guest OS and the hypervisor before enabling this feature. For example, Windows Server 2019 supports hot-plug CPU on AHV, ESXi, and Hyper-V, but not on XenServer1.

Memory can be removed from a powered on VM if the guest OS supports it. This is also known as hot-unplug memory. The administrator should check the compatibility of the guest OS and the hypervisor before enabling this feature. For example, Linux supports hot-unplug memory on AHV, ESXi, and XenServer, but not on Hyper-V2.

VM must be powered off to add CPU if the guest OS does not support hot-plug CPU. This is also known as cold-plug CPU. The administrator should plan for the downtime required to power off and power on the VM after adding CPU.

VM must be powered off to reduce memory if the guest OS does not support hot-unplug memory. This is also known as cold-unplug memory. The administrator should plan for the downtime required to power off and power on the VM after reducing memory. References: Nutanix Multicloud Automation Administration (NMCAA), page 10; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 3; Nutanix Support Portal - Guest OS Compatibility Matrix