Manually Reconfiguring VM Resources

Access through:

Views menu > Operational or VMs and Templates

Available to:

Administrator, Operator with Approval, Operator Access Rights

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 (not supported for AWS)

adding, changing or removing storage

Reconfiguring resources is not supported for Azure Service Manager (Classic) VMs.

There are three ways to reconfigure VM resources in Embotics® vCommander® and the Service Portal:

Apply a vCommander-generated rightsizing recommendation.

Submit a change request.

Manually reconfigure VM resources, as detailed in this topic.

The method you choose to expose to users depends on how much control you want over VM configuration changes. If you need to control VM configuration changes for some or all of your users, you should require users to apply a recommendation or to submit a change request, rather than allowing them to manually reconfigure VM resources.

NotePencil-smallThis task requires the Service Portal permissions Modify VM CPU & Memory and Modify VM Storage. Service Portal users can reconfigure memory, CPU, storage and network resources (or change the instance type, in the case of public cloud VMs).

caution

Networks are not filtered by deployment destination or user visibility, which means a user with the Modify VM Network permission is able to see networks that they do not have access to.

What you can change depends on the power state of the VM. The following table indicates whether you must power off the VM in order to perform each task.

Table: Hot/Cold Resource Changes for Each Virtualization Platform

 

VM must be powered down to reconfigure?

Task

vCenter

SCVMM

AWS

ARM

Change CPU / memory resources OR change instance type

Dictated by CPU Hot Plug and Memory Hot Plug settings for the VM in vCenter

Yes

Yes

Yes

Add network adapters

--

Yes

--

Yes

Delete network adapters

Yes

Yes

--

Yes

Change subnet (network)

N/A

N/A

N/A

Yes

Expand disk capacity

--

Yes

Existing disks cannot be expanded.

Yes

Add storage resources

--

--

--

--

Delete storage resources

--

--

--

--

Reconfiguring VM resources for vCenter and SCVMM

1.Select a VM in the tree or on the Virtual Machines tab.

2.Right-click and select Configuration Management > Reconfigure VM Resources.

3.In the menu, select the resource you want to configure.

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

NotePencil-smallvCenter: If you've enabled CPU Hot Add, CPU Hot Remove or Memory Hot Add for the VM, you can change CPU and memory resources while the VM is powered on, within the allowed range.

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.

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

NotePencil-smallIf you have a large number of networks, click search-field-icon next to the Network drop-down menu to open a pop-up dialog for easier searching.

6.Storage: For existing disks, you can modify their capacity and delete them.

NotePencil-smallIt's not possible to resize IDE disks, independent disks, or disks involved in a snapshot or linked clone chain.

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:

a)Click Add and then specify disk capacity, disk type and location.

b)If you choose Select a datastore from the Location drop-down menu, the Select Datastore dialog appears, allowing you to specify the datastore.  vCommander provides capacity information to guide your decision.  

c)The options available in the Disk Provisioning drop-down menu depend on the selected datastore and the VM's hardware version:

vCenter disk provisioning options

SCVMM disk provisioning options

Thin: Allocate disk space on demand. Supports over-allocation of storage resources.

SEsparse: Allocate disk space as it is used by the guest OS. Supports over-allocation of storage resources. Block size is configurable and space may be reclaimed.

NotePencil-smallThe SEsparse format is supported only for vSphere version 5.1 or higher and 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.

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 are creating (for example, 20 GB on disk for a 20 GB VHD). This is the default format.

NotePencil-smallThe 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, select it in the Disks list and click Delete.

Reconfiguring resources for AWS VMs

1.Select a VM in the tree or on the Virtual Machines tab.

2.Right-click and select Configuration Management > Reconfigure VM Resources.

3.To change the instance type, go to the Instance Type page.

NotePencil-smallTo change the instance type, the VM must be powered off.

Select an instance type from the drop-down menu.

Clicking Details provides 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, click Storage in the menu.

NotePencil-smallYou cannot modify existing disks.

To create a new EBS volume and attach it to this VM, click Add and 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 menu. Mouseover the help-16x16 icon for details on each type; see Amazon EBS Volume Types in the AWS documentation for more information.

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. Cannot 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 is infrequently accessed. The minimum disk size for this type is 500 GB. Cannot be a boot volume.

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 10,000. A maximum ratio of 50:1 is permitted between IOPS and volume size; for example, a volume with 3000 IOPS must be at least 60 GB in size. The minimum disk size for this storage type is 4 GB.

Encryption: 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.

Delete on Termination: By default, 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.

NotePencil-smallThe new disk is created in the same availability zone as the instance it's attached to.

5.To delete a disk, click Storage in the menu.

Select a disk and click Delete.

Confirm the deletion by clicking OK.

NotePencil-smallYou cannot remove the base disk.

Reconfiguring resources for Azure Resource Manager VMs

1.Select a VM in the tree or on the Virtual Machines tab.

2.Right-click and select Configuration Management > Reconfigure VM Resources.

3.To change the instance type, go to the Instance Type page.

NotePencil-smallThe VM must be powered off.

Select an instance type from the drop-down menu.

Clicking Details provides the full set of properties for the selected instance type.

4.To change the subnet, go to the Network page.

NotePencil-smallThe VM must be powered off.

Select a subnet from the list of those available in the VM's network.

5.To add storage resources, click Storage in the menu.

Click Add and specify the following:

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.

NotePencil-smallLimitation: 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 menu:

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 are not supported for all instance types.

HDD: Standard disks (HDD) are backed by magnetic drives and are preferable for applications where data is accessed infrequently.

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.

NotePencil-smallLimitation: You cannot configure encryption for a new disk.
NotePencil-smallEach Azure instance type has limitations for the number and type of disks that can be added.

6.To delete a disk, click Storage in the menu.

Select a disk and click Delete.

Confirm the deletion by clicking OK.

NotePencil-smallYou cannot remove the base disk.

7.To expand an existing disk, click Storage in the menu.

NotePencil-smallThe VM must be powered off.

Select the disk you want to expand.

Enter a number in the Capacity field.

Click OK.