Updating CPU definitions

If a VM repeatedly prompts you to reactivate or reboot, it may be using an older CPU definition (also called a CPU mask). If you regularly shut down your VMs, you don’t need to do anything. If you leave your VM running, shut it down to install the update (if the VM is suspended, resume it so that it’s running, shut it down, and then restart it).

For more information, see Virtual CPU definitions FAQ.

Updating the CPU definition for a VM in an environment

If you have a VM that needs a CPU definition update, the update is automatically applied when the VM is started (if you have a suspended VM, resume it and shut it down first).

For each VM in the environment, do the following:
For a powered-off VM…
1. Start the VM.
For a running VM…
1. Shut down the VM (don’t suspend it).
2. Restart the VM.
For a suspended VM…
1. Resume the VM (so that it’s fully powered-on and running).
2. Shut down the VM (don’t suspend it).
3. Restart the VM.
Access each of the VM desktops to check the VM status.

After the update, the VM may need driver updates and the guest OS may need to be re-licensed.

Updating the CPU definition for a VM in a template

To update the CPU definitions for VMs in a template, create a temporary environment from the template, update the CPU definitions for the VMs in the temporary environment, and then save the temporary environment as a new template.

Create a temporary environment from the template. For detailed instructions, see Creating an environment from a template. For each VM in the temporary environment, do the following:
For a powered-off VM…
1. Start the VM.
For a running VM…
1. Shut down the VM (don’t suspend it).
2. Restart the VM.
For a suspended VM…
1. Resume the VM (so that it’s fully powered-on and running).
2. Shut down the VM (don’t suspend it).
3. Restart the VM.
Access each of the VM desktops to check the VM status.

After the update, the VM may need driver updates and the guest OS may need to be re-licensed.
Save the temporary environment as a new template. For detailed instructions, see Saving an environment as a template.

You can delete the temporary environment and the original template, or you can rename the old template to keep as an archived version.