After completing this section, you should be able to change the configuration of virtual hardware for an existing virtual machine.
To persistently change the settings of a virtual machine, navigate to the list of virtual machines by clicking in the menu bar, and then selecting . Right-click the virtual machine and select from the menu. This brings up the Edit Virtual Machine window.
![]() |
The Edit Virtual Machine window is nearly identical to the New Virtual Machine window, discussed earlier. In order to see all of the settings, you will need to click the button. Please note that some changes require that the virtual machine is shut down and restarted. You will be alerted if a shutdown is required; when viewing the list of virtual machines, the impacted virtual machine will be marked with an orange pending changes icon.
The following section describes some of the main tabs in the New Virtual Machine window, and the types of changes you might make within them.
Settings found in the System tab allow you to change memory, virtual CPUs, and time zone. The Instance Type menu populates the memory and CPU fields every time you change the selection, but you can always customize from there.
Memory Size: Increasing the Memory Size or the Physical Memory Guaranteed can be done on a running virtual machine. Reducing the Memory Size, reducing or increasing the Maximum Memory, and reducing the Physical Memory Guaranteed requires restarting the virtual machine.
Virtual Sockets: You can hot-plug vCPUs, but the operating system must support this feature. You can also unplug vCPUs, but only if they were hot-plugged. You cannot unplug more vCPUs than the virtual machine had when it was created.
These settings can adjust how the machine boots initially, using either Cloud-Init or Sysprep.
The Initial Run tab will be discussed later in this chapter.
These settings affect how the virtual machine is accessed, either through the Administration Portal or the VM Portal. You can also specify the keyboard layout, whether or not USB support is enabled, whether or not to enable single sign-on, and more from the Console tab.
There may be cases where you need a virtual machine to run on a specific host. If you run a virtual machine on a specific host, you can disable automatic migration, but still leave manual migration as an available option. For example, suppose two out of five hosts in a cluster have extra capabilities. You may need a virtual machine to run on one of them. You could start the virtual machine on one of the hosts, and then migrate it to the other host, if necessary. Specifying that a virtual machine should run on a particular host, and deciding if a virtual machine should be migrated, are some of the types of changes that can be made from the Hosts tab.
You can flag a virtual machine as being highly available on the High Availability tab. Additionally, you can specify a priority for the run/migration queue on the machine. More information regarding high availability is presented later in this course.
You can make adjustments to CPU and memory allocation from the Resource Allocation tab. When creating a new virtual machine from a template, you can specify if the the virtual machine will be a clone, or if the virtual machine will have a thin storage overlay. A cloned virtual machine can exist independently of the template used to create it, but a virtual machine with a thin storage overlay continues to use the template from which it was created. More information about templates is presented later in this chapter.
These settings allow you to persistently specify a boot order. For example, you can persistently attach an ISO to the CD drive of the virtual machine, or pass additional information to GRUB. The Boot Options tab also allows you to pass additional information to GRUB.
In the Administration Portal, you can configure virtual non-uniform memory access (NUMA) nodes on a virtual machine, and pin them to physical NUMA nodes on one or more hosts. This can be done from the Host tab when viewing in either the New Virtual Machine window, or the Edit Virtual Machine window. The default policy is to schedule and run virtual machines on any available resources on the host. As a result, resources backing a large virtual machine that cannot fit within a single host socket could be spread out across multiple NUMA nodes. Over time these resources may be moved around, leading to poor and unpredictable performance. Configure and pin virtual NUMA nodes to avoid this outcome and improve performance.
RHV allow adding network interfaces and disks to running virtual machines. This is referred to as hot-plugging. For network interfaces, it is possible to add a network interface to a virtual machine and then plug it in, or unplug it, as necessary. A plugged in network interface is accessible to the virtual machine, while an unplugged one is not. One way to view network interfaces from a Linux virtual machine is using the ip link command.
Additional hard disks can be added in a similar way. A new hard disk is accessible to the virtual machine when it is activated. A deactivated hard disk is still associated with a virtual machine, but it is not accessible by the virtual machine. One way to view hard disks from a Linux virtual machine is using the lsblk command.
Care must be taken when removing network interfaces or disks from running virtual machines to ensure that they are not being used.
Virtual machines connect network interfaces to logical networks in your RHV environment. You can create multiple network interfaces on your virtual machines, each of which can be associated with a specific logical network.
For a logical network to be available to a virtual machine, it must be configured as a VM Network by the cluster.
A quick way of adding a new network interface is to use the same basic procedure that you used when creating the virtual machine. To add a new network interface, edit the virtual machine and go to the General tab. The Instantiate VM network interfaces by picking a vNIC profile section allows you to add new network interfaces or remove existing ones, using the and buttons. You cannot specifically plug or unplug a network interface from the General tab. New network interfaces added from the General tab are automatically plugged in and accessible to the virtual machine.
More options are available when you view virtual machine details by clicking the name of an individual virtual machine listed on the Compute >> Virtual Machines page. From the details page, you can click the Network Interfaces tab. Here you can either add a new network interface or select an existing network interface to edit. When adding a new network interface, in addition to selecting a VM Network profile, you can select a driver type, and you can customize the MAC address. When adding or editing a network interface, you can specify the link state as being Up or Down, and the card status as being either Plugged or Unplugged. You can edit a network interface on a running machine, but depending on the changes you make, the virtual machine might need to be restarted.
New disks can be added to a virtual machine. As with network interfaces, there is a quick method and a more advanced method. The quick method uses the same basic procedure that you used when creating the virtual machine. To add a new disk, edit the virtual machine and go to the General tab. The Instance Images section allows you to add new disks or remove existing disks, using the and buttons. Existing disks can be modified using the button.
More options are available when you view virtual machine details by clicking the name of an individual virtual machine listed on the Compute >> Virtual Machines page. From the details page, click the Disks tab. Additional configuration fields are available when you choose to add or edit a disk. To deactivate an individual disk, highlight the row containing the disk by clicking an empty cell in the row. With the row highlighted, click the three vertical dot menu, located to the right of the button, and select . A deactivated disk can be removed. When you attempt to remove a disk, you will be prompted to confirm you action. You must also decide if the disk should be removed permanently. A disk which is not removed permanently can be attached to a different virtual machine.
A bootable disk may contain the OS icon, or it may have (boot) as descriptive text.
Deleting the boot disk for a virtual machine will render it non-bootable.
Further information is available in the "Editing Virtual Machines" chapter of the Virtual Machine Management Guide for Red Hat Virtualization at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/virtual_machine_management_guide/index#chap-Editing_Virtual_Machines
Details on Edit Virtual Machine window settings are documented in the "Reference: Settings in Administration Portal and VM Portal Windows" appendix to the Virtual Machine Management Guide for Red Hat Virtualization at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/virtual_machine_management_guide/index#appe-Reference_Settings_in_Administration_Portal_and_User_Portal_Windows