Reconfiguring VM Resources

Reconfiguring VM resources means:

  • changing the amount of memory and the number of virtual processors assigned to a VM, or changing the instance type
  • adding or deleting network adapters
  • adding, changing or removing storage

Note: Not all of these options are available on all cloud platforms.

You can manually reconfigure VM resources if you have the required permissions. Otherwise, you can submit a change request to reconfigure VM resources, or apply a rightsizing recommendation.

In this topic:

Reconfiguring resources for Amazon EC2 instances

To reconfigure resources for an EC2 instance:

  1. From the Applications page, select an instance.
  2. Select Actions > VM > Reconfigure Resources.
  3. To change the instance type, select an instance type from the drop-down list.

    Note: The instance must be powered off.

    Select Details to see the full set of properties for the selected instance type.

    EBS Optimized: If the selected instance type supports EBS optimization, this option is active. EBS optimization enables additional, dedicated throughput between Amazon EC2 and Amazon EBS, and therefore improved performance for Amazon EBS volumes. Additional charges from AWS apply if you enable this option.

  4. To add a disk, select Add Disk in the Storage drop-down panel, then specify the following:

    Device Name: Specify the name that the block device driver for the instance will assign when mounting the volume. The name recommended by Amazon is provided; edit this value if required. See Block Device Mapping in the AWS documentation for more information.

    Capacity: Specify the disk capacity, in GB.

    Volume Type: Select one of the following types from the drop-down list:

    • General Purpose (SSD): General purpose Solid-State Drive volume that balances price and performance for a wide variety of transactional workloads. Recommended for system boot volumes, virtual desktops, low-latency interactive apps, development and test environments.
    • Provisioned IOPS (SSD): Highest-performance SSD volume designed for mission-critical applications. Best for critical business applications that require sustained IOPS performance, or more than 10,000 IOPS or 160 MiB/s of throughput per volume, such as large database workloads and EBS-optimized instances. The ratio of IOPS provisioned and the volume size requested can be a maximum of 50.
    • Magnetic: Previous-generation Hard Disk Drive volumes for workloads where data is infrequently accessed. Not recommended for new applications.
    • Throughput Optimized (HDD): Low-cost Hard Disk Drive volume designed for frequently accessed, throughput-intensive workloads. Best for streaming workloads requiring consistent, fast throughput at a low price, such as big data, data warehouses, and log processing. The minimum disk size for this type is 500 GB. can't be a boot volume.
    • Cold (HDD): Lowest-cost Hard Disk Drive volume designed for less frequently accessed workloads. Best for throughput-oriented storage for large amounts of data that's infrequently accessed. The minimum disk size for this type is 500 GB. can't be a boot volume.

    Encrypted: Specify whether to encrypt the disk. Note that not all instance types support disk encryption; see Amazon EBS Encryption in the AWS documentation for the list of supported instance types.

    IOPS: If you select the Provisioned IOPS (SSD) volume type, you must specify the number of I/O operations per second (IOPS) this volume will support. Specify a number between 100 and 4000. A maximum ratio of 30:1 is permitted between IOPS and volume size; for example, a volume with 3000 IOPS must be at least 100 GB in size.

    Delete on Termination: If enabled, this disk will be deleted when the VM to which it's attached is terminated. If you want to preserve this disk so that it can be attached to a different VM when this VM is terminated, disable this option.

    Note: The new disk is created in the same availability zone as the instance it's attached to.

  5. To delete a disk, select .

    Note: You can't remove the base disk or modify existing disks.

  6. Select Submit to complete the operation.

Reconfiguring resources for GCP instances

You can change the instance type for a GCP instance, but you can't change network or storage resources.

In addition to choosing a predefined GCP instance type, you can also choose custom values for memory and CPU. To learn more, see Creating a VM Instance with a custom machine type in the GCP documentation.

Note: To change CPU and memory resources, the instance must be powered off.

To change memory and CPU resources for a GCP instance:

  1. From the Applications page, select an instance.
  2. Select Actions > VM > Reconfigure Resources.
  3. If one of the predefined instance types meets your needs, select it from the drop-down list.

    Note: Select Details to see the full set of properties for the selected instance type.

  4. If none of the predefined instance types fits your needs:
    1. Select Custom from the drop-down list.
    2. Enter values for CPU Count and Memory (GB) as required.

      The maximum CPU count is determined by the region and the CPU platform. The value you enter isn't validated. If you enter an invalid value, the task may fail.

      The minimum and maximum memory depend on the value you entered for CPU Count.

    3. A custom machine can have up to 6.5 GB of memory per vCPU. If this isn't enough memory for your workload, enable Extended Memory.

      The maximum extended memory depends on the region. The value you enter isn't validated.

      Caution: Extended memory incurs additional costs. To learn more, see Adding extended memory to a machine type in the GCP documentation.

  5. Select Submit to complete the operation.

Reconfiguring resources for Azure instances

To reconfigure resources for an Azure instance:

  1. From the Applications page, select an instance.
  2. Select Actions > VM > Reconfigure Resources.
  3. To change the instance type, select an instance type from the drop-down list.

    Note: The instance must be powered off.

    Select Details to see the full set of properties for the selected instance type.

  4. To add a disk, select Add Disk in the Storage drop-down panel.

    Device Name: Edit the suggested device name if required. Managed disk names must be unique in the target resource group. Unmanaged disk names must unique within the VM. The name must contain from 1 to 64 characters, must contain only letters, numbers, hyphens, dots and underscores, and must start with a letter or number.

    Note: Even though you can edit the name for a managed disk, the suggested name will be used.

    Capacity: Specify the disk capacity in GB. Note that you can't shrink existing disks, and you can't resize existing unmanaged disks.

    Disk Type: Select one of the following types from the drop-down list:

    • HDD: Standard disks (HDD) are backed by magnetic drives and are preferable for applications where data is accessed infrequently.
    • SSD: Premium disks (SSD) are backed by solid-state drives and offer consistent, low-latency performance. They provide the best balance between price and performance, and are ideal for I/O-intensive applications and production workloads. Premium disks aren't supported for all instance types.

    Storage Account: For unmanaged disks, select a storage account from the list. You can select only storage accounts that are available in the image's region and support the selected Disk Type.

    Note: Limitation: You can't configure encryption for a new disk.

  5. To delete a disk, select in the Storage drop-down

    Note: You can't remove the base disk.

  6. To expand an existing disk, in the Storage drop-down panel, enter a number in the disk's Capacity field.

    Note: The VM must be powered off.

  7. To change the subnet, in the Network drop-down panel, select a subnet from the list of those available in the VM's network.

    Note: The VM must be powered off.

  8. Select Submit to complete the operation.

Reconfiguring resources for SCVMM VMs

To reconfigure resources for an SCVMM VM:

  1. From the Applications page, select a VM.
  2. Select Actions > VM > Reconfigure Resources

    Note: Some reconfiguration options require that the VM be powered off.

  3. CPU & Memory: Specify values for memory size and CPU count as required.
  4. Storage: For existing disks, you can modify only capacity. The Disk Provisioning section indicates how the disk was provisioned. See the table below for a description of the provisioning types.

    To add a disk:

    1. Select Add Disk and then specify disk capacity, disk type and location.
    2. To specify the datastore: Select Select Datastore. Capacity information is provided to guide your decision.
    3. The options available in the Provisioning drop-down list depend on the selected datastore and the VM's hardware version:
      • Dynamically Expanding: Save storage space by creating a small file that grows as data is written to it, up to the configured limit.
      • Fixed Format: Allow the datastore to occupy the entire space provisioned for it by creating a file equivalent in size to the disk you're creating (for example, 20 GB on disk for a 20 GB VHD). This is the default format.

    Note: The datastore where the VM resides and the datastore where the new disk is placed must both be clustered, or must both be non-clustered. All new disks are created as SCSI disks. To delete a disk you added, select .

  5. Network: Specify network settings as required. To add adapters for the VM, select Add Adapter.

    Note: If you have a large number of networks, use the search field in the Network drop-down list to narrow the list.

  6. Select Submit to complete the operation.

Reconfiguring resources for vCenter VMs

To reconfigure resources for a vCenter VM:

  1. From the Applications page, select a VM.
  2. Select Actions > VM > Reconfigure Resources.

    Note: Some reconfiguration options require that the VM be powered off. If your administrator has configured it, you may be able to change CPU and memory resources for aVM while it's powered on, within an allowed range.

  3. CPU & Memory: Specify values for memory size and CPU count as required.

    Caution: If you change the number of virtual processors for a VM after the guest operating system has been installed, the VM may become unstable.

  4. Storage: For existing disks, you can modify only capacity. The Disk Provisioning section indicates how the disk was provisioned. See the table below for a description of the provisioning types.

    To add a disk:

    1. Select Add Disk and then specify disk capacity, disk type and location.
    2. To specify the datastore: Select Select Datastore. Capacity information is provided to guide your decision.
    3. The options available in the Provisioning drop-down list depend on the selected datastore and the VM's hardware version:
      • Thin: Allocate disk space on demand. Supports over-allocation of storage resources.
      • SEsparse: Allocate disk space as it's used by the guest OS. Supports over-allocation of storage resources. Block size is configurable and space may be reclaimed.

        Note: The SEsparse format is supported only for hardware version 9 or higher.

      • Thick - Lazy Zeroed: Allocate disk space now. Disk blocks are zeroed out on first write. This is the default format.
      • Thick - Eager Zeroed: Allocate disk space now. All disk blocks are zeroed out during disk creation. This is required to support clustering features such as Fault Tolerance.

    Note: The datastore where the VM resides and the datastore where the new disk is placed must both be clustered, or must both be non-clustered. All new disks are created as SCSI disks. To delete a disk you added, select .

  5. Network: Specify network settings as required. To add adapters for the VM, select Add Adapter.

    Note: If you have a large number of networks, use the search field in the Network drop-down list to narrow the list.

  6. Select Submit to complete the operation.