Reprovisioning Virtual Machine Resources

Reprovision a virtual machine (VM) to change its allocation of virtual CPUs (vCPUs), memory, storage, or network resources.

Launch the Reprovision Virtual Machine wizard by clicking Config in the bottom pane of the Virtual Machines page. The wizard steps you through the process of reallocating resources to the VM.

To reprovision a virtual machine

1. Open the Virtual Machines page (see The Virtual Machines Page).
2. Select a VM and click Shutdown.
3. When the VM has stopped, click Config to display the Reprovision Virtual Machine wizard.
4. On the Name, Description, and Protection page:
   1. Type the Name and an optional Description for the VM as they will appear in the everRun Availability Console.
   2. Select the level of protection to use for the VM:
      • Fault Tolerant (FT)
      • High Availability (HA)

      For information about these levels of protection, see Creating a New Virtual Machine and Modes of Operation.

   3. Click Next.

5. On the vCPUs and Memory page:

   1. Specify the number of vCPUs and the amount of Memory to assign to the VM. For more information, see Planning Virtual Machine vCPUs and Planning Virtual Machine Memory.
   2. If applicable, select the Keyboard Layout in Console to set the keyboard type for your country.
   3. Click Next.

6. On the Volumes page, you can:
   Notes:  

   • You cannot modify the VM boot volume, only data volumes
   • To expand a volume container, see Expanding a Volume Container on the everRun System.
   • Click Detach to disconnect a volume from a VM and keep it for future use.
   • Click Delete to permanently remove a volume from the everRunsystem.
   • Select an unattached volume from a pulldown menu (if displayed) and click Attach.
   • Add a new volume:
     1. Type the Name of the boot volume.

     2. Type the Container Size and Volume Size of the volume in gigabytes (GB). The container size is the total size for the volume including extra space to store snapshots. The volume size is the portion of the container that is available to the guest operating system. For more information about allocating storage, see Sizing Volume Containers andPlanning Virtual Machine Storage.

     3. Select the Storage Group for the volume, and, if applicable, select the Sector Size.

        Ensure that you select a storage group that supports the sector size of the volume (see Planning Virtual Machine Storage). Note that the boot volume must have a sector size of 512 B. You can select the sector size, either 4K or 512B, only for data disks.

     4. If applicable, click Add New Volume to create a new data volume. (If the button is not visible, scroll down to the bottom of the wizard page.) Specify the parameters for the new volume.
     5. If applicable, click Attach to connect a volume to a VM.

   To continue, click Next.

7. On the Networks page, activate the check box for each shared network that you want to attach to the VM.

   For each shared network that you attach, you can also optionally:

   • Set a custom MAC address (for details, see Assigning a Specific MAC Address to a Virtual Machine).
   • Set the State to Enabled or Disabled, which allows you to allow or block network traffic to the selected network.

   For more information, see Planning Virtual Machine Networks. To continue, click Next.

8. On the Configuration Summary page:

   Caution: Make sure that any volumes marked for removal are correct. When you click Finish, permanent data loss occurs on disks marked for removal.
   
   1. Review the configuration summary. If you need to make changes, click Back.
   2. To accept the VM as provisioned, click Finish.
9. Click Start to restart the VM.
10. For Windows-based VMs, if you changed the number of assigned virtual CPUs in a Windows-based VM from 1 to n or or n to 1, after restarting the VM at the end of the re-provisioning process you must shut down and restart the VM a second time. This allows the VM to correctly reconfigure itself for Symmetric Multiprocessing (SMP). The VM displays odd behavior and is not usable until it is restarted.

Related Topics

Managing Virtual Machine Resources

Planning Virtual Machine Resources

Managing Virtual Machines