Appendix A: Reference Settings in Administration Portal and User Portal Windows

Explanation of Settings in the New Virtual Machine and Edit Virtual Machine Windows

Virtual Machine General Settings Explained

The following table details the options available on the General tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: General Settings

Field Name Description
Cluster The name of the host cluster to which the virtual machine is attached. Virtual machines are hosted on any physical machine in that cluster in accordance with policy rules.
Template

The template on which the virtual machine is based. This field is set to `Blank` by default, which allows you to create a virtual machine on which an operating system has not yet been installed. Templates are displayed as **Name | Sub-version name (Sub-version number)**. Each new version is displayed with a number in brackets that indicates the relative order of the version, with a higher number indicating a more recent version.

The version name is displayed as `base version` if it is the root template of the template version chain.

When the virtual machine is stateless, there is an option to select the `latest` version of the template. This option means that anytime a new version of this template is created, the virtual machine is automatically recreated on restart based on the latest template.

Operating System The operating system. Valid values include a range of Enterprise Linux and Windows variants.
Instance Type

The instance type on which the virtual machine's hardware configuration can be based. This field is set to Custom by default, which means the virtual machine is not connected to an instance type. The other options available from this drop down menu are Large, Medium, Small, Tiny, XLarge, and any custom instance types that the Administrator has created.

Other settings that have a chain link icon next to them are pre-filled by the selected instance type. If one of these values is changed, the virtual machine will be detached from the instance type and the chain icon will appear broken. However, if the changed setting is restored to its original value, the virtual machine will be reattached to the instance type and the links in the chain icon will rejoin.

Optimized for The type of system for which the virtual machine is to be optimized. There are two options: Server, and Desktop; by default, the field is set to Server. Virtual machines optimized to act as servers have no sound card, use a cloned disk image, and are not stateless. In contrast, virtual machines optimized to act as desktop machines do have a sound card, use an image (thin allocation), and are stateless.
Name The name of the virtual machine. The name must be a unique name within the data center and must not contain any spaces, and must contain at least one character from A-Z or 0-9. The maximum length of a virtual machine name is 255 characters. The name can be re-used in different data centers in the environment.
VM ID The virtual machine ID. The virtual machine's creator can set a custom ID for that virtual machine. If no ID is specified during creation a UUID will be automatically assigned. For both custom and automatically-generated IDs, changes are not possible after virtual machine creation.
Description A meaningful description of the new virtual machine.
Comment A field for adding plain text human-readable comments regarding the virtual machine.
Affinity Labels Add or remove a selected **Affinity Label**.
Stateless Select this check box to run the virtual machine in stateless mode. This mode is used primarily for desktop virtual machines. Running a stateless desktop or server creates a new COW layer on the VM hard disk image where new and changed data is stored. Shutting down the stateless VM deletes the new COW layer, which returns the VM to its original state. Stateless virtual machines are useful when creating machines that need to be used for a short time, or by temporary staff.
Start in Pause Mode Select this check box to always start the virtual machine in pause mode. This option is suitable for virtual machines which require a long time to establish a SPICE connection; for example, virtual machines in remote locations.
Delete Protection Select this check box to make it impossible to delete the virtual machine. It is only possible to delete the virtual machine if this check box is not selected.
Instance Images

Click Attach to attach a floating disk to the virtual machine, or click Create to add a new virtual disk. Use the plus and minus buttons to add or remove additional virtual disks.

Click Edit to reopen the Attach Virtual Disks or New Virtual Disk window. This button appears after a virtual disk has been attached or created.

Instantiate VM network interfaces by picking a vNIC profile. Add a network interface to the virtual machine by selecting a vNIC profile from the nic1 drop-down list. Use the plus and minus buttons to add or remove additional network interfaces.

Virtual Machine System Settings Explained

The following table details the options available on the System tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: System Settings

Field Name Description
Memory Size The amount of memory assigned to the virtual machine. When allocating memory, consider the processing and storage needs of the applications that are intended to run on the virtual machine.
Maximum Memory The maximum amount of memory that can be assigned to the virtual machine. Maximum guest memory is also constrained by the selected guest architecture and the cluster compatibility level.
Total Virtual CPUs The processing power allocated to the virtual machine as CPU Cores. Do not assign more cores to a virtual machine than are present on the physical host.
Virtual Sockets The number of CPU sockets for the virtual machine. Do not assign more sockets to a virtual machine than are present on the physical host.
Cores per Virtual Socket The number of cores assigned to each virtual socket.
Threads per Core The number of threads assigned to each core. Increasing the value enables simultaneous multi-threading (SMT). IBM POWER8 supports up to 8 threads per core. For x86 (Intel and AMD) CPU types, the recommended value is 1.
Custom Emulated Machine This option allows you to specify the machine type. If changed, the virtual machine will only run on hosts that support this machine type. Defaults to the cluster's default machine type.
Custom CPU Type This option allows you to specify a CPU type. If changed, the virtual machine will only run on hosts that support this CPU type. Defaults to the cluster's default CPU type.
Custom Compatibility Version The compatibility version determines which features are supported by the cluster, as well as, the values of some properties and the emulated machine type. By default, the virtual machine is configured to run in the same compatibility mode as the cluster as the default is inherited from the cluster. In some situations the default compatibility mode needs to be changed. An example of this is if the cluster has been updated to a later compatibility version but the virtual machines have not been restarted. These virtual machines can be set to use a custom compatibility mode that is older than that of the cluster
Hardware Clock Time Offset This option sets the time zone offset of the guest hardware clock. For Windows, this should correspond to the time zone set in the guest. Most default Linux installations expect the hardware clock to be GMT+00:00.
Provide custom serial number policy

This check box allows you to specify a serial number for the virtual machine. Select either:

  • Host ID: Sets the host's UUID as the virtual machine's serial number.
  • Vm ID: Sets the virtual machine's UUID as its serial number.
  • Custom serial number: Allows you to specify a custom serial number.

Virtual Machine Initial Run Settings Explained

The following table details the options available on the Initial Run tab of the New Virtual Machine and Edit Virtual Machine windows. The settings in this table are only visible if the Use Cloud-Init/Sysprep check box is selected, and certain options are only visible when either a Linux-based or Windows-based option has been selected in the Operating System list in the General tab, as outlined below.

Virtual Machine: Initial Run Settings

Field Name Operating System Description
Use Cloud-Init/Sysprep Linux, Windows This check box toggles whether Cloud-Init or Sysprep will be used to initialize the virtual machine.
VM Hostname Linux, Windows The host name of the virtual machine.
Domain Windows The Active Directory domain to which the virtual machine belongs.
Organization Name Windows The name of the organization to which the virtual machine belongs. This option corresponds to the text field for setting the organization name displayed when a machine running Windows is started for the first time.
Active Directory OU Windows The organizational unit in the Active Directory domain to which the virtual machine belongs.
Configure Time Zone Linux, Windows The time zone for the virtual machine. Select this check box and select a time zone from the Time Zone list.
Admin Password Windows

The administrative user password for the virtual machine. Click the disclosure arrow to display the settings for this option.

  • Use already configured password: This check box is automatically selected after you specify an initial administrative user password. You must clear this check box to enable the Admin Password and Verify Admin Password fields and specify a new password.
  • Admin Password: The administrative user password for the virtual machine. Enter the password in this text field and the Verify Admin Password text field to verify the password.
Authentication Linux

The authentication details for the virtual machine. Click the disclosure arrow to display the settings for this option.

  • Use already configured password: This check box is automatically selected after you specify an initial root password. You must clear this check box to enable the Password and Verify Password fields and specify a new password.
  • Password: The root password for the virtual machine. Enter the password in this text field and the Verify Password text field to verify the password.
  • SSH Authorized Keys: SSH keys to be added to the authorized keys file of the virtual machine. You can specify multiple SSH keys by entering each SSH key on a new line.
  • Regenerate SSH Keys: Regenerates SSH keys for the virtual machine.
Custom Locale Windows

Custom locale options for the virtual machine. Locales must be in a format such as en-US. Click the disclosure arrow to display the settings for this option.

  • Input Locale: The locale for user input.
  • UI Language: The language used for user interface elements such as buttons and menus.
  • System Locale: The locale for the overall system.
  • User Locale: The locale for users.
Networks Linux

Network-related settings for the virtual machine. Click the disclosure arrow to display the settings for this option.

  • DNS Servers: The DNS servers to be used by the virtual machine.
  • DNS Search Domains: The DNS search domains to be used by the virtual machine.
  • Network: Configures network interfaces for the virtual machine. Select this check box and click + or - to add or remove network interfaces to or from the virtual machine. When you click +, a set of fields becomes visible that can specify whether to use DHCP, and configure an IP address, netmask, and gateway, and specify whether the network interface will start on boot.
Custom Script Linux Custom scripts that will be run on the virtual machine when it starts. The scripts entered in this field are custom YAML sections that are added to those produced by the Engine, and allow you to automate tasks such as creating users and files, configuring yum repositories and running commands. For more information on the format of scripts that can be entered in this field, see the Custom Script documentation.
Sysprep Windows A custom Sysprep definition. The definition must be in the format of a complete unattended installation answer file. You can copy and paste the default answer files in the /usr/share/ovirt-engine/conf/sysprep/ directory on the machine on which the oVirt Engine is installed and alter the fields as required.

Virtual Machine Console Settings Explained

The following table details the options available on the Console tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: Console Settings

Field Name Description
Graphical Console Section
Headless Mode

Select this check box if you do not a require a graphical console for the virtual machine.

When selected, all other fields in the Graphical Console section are disabled. In the VM Portal, the Console icon in the virtual machine’s details view is also disabled.

Important: See “Configuring Headless Virtual Machines” in Chapter 4 for more details and prerequisites for using headless mode.

Video Type Defines the graphics device. **QXL** is the default and supports both graphic protocols. **VGA** and **CIRRUS** support only the VNC protocol.
Graphics protocol Defines which display protocol to use. SPICE is the recommended protocol as it supports more features. VNC is an alternative option and requires a VNC client to connect to a virtual machine. Select SPICE + VNC for the most flexible option.
VNC Keyboard Layout Defines the keyboard layout for the virtual machine. This option is only available when using the VNC protocol.
USB Support

Defines whether USB devices can be used on the virtual machine. This option is only available for virtual machines using the SPICE protocol. Select either:

  • Disabled - Does not allow USB redirection from the client machine to the virtual machine.
  • Legacy - Enables the SPICE USB redirection policy used in oVirt 3.0. This option can only be used on Windows virtual machines, and will not be supported in future versions of oVirt.
  • Native - Enables native KVM/SPICE USB redirection for Linux and Windows virtual machines. Virtual machines do not require any in-guest agents or drivers for native USB.
Console Disconnect Action

Defines what happens when the console is disconnected. This is only relevant with SPICE and VNC console connections. This setting can be changed while the virtual machine is running but will not take effect until a new console connection is established. Select either:

  • No action - No action is taken.
  • Lock screen - This is the default option. For all Linux machines and for Windows desktops this locks the currently active user session. For Windows servers, this locks the desktop and the currently active user.
  • Logout user - For all Linux machines and Windows desktops, this logs out the currently active user session. For Windows servers, the desktop and the currently active user are logged out.
  • Shutdown virtual machine - Initiates a graceful virtual machine shutdown.
  • Reboot virtual machine - Initiates a graceful virtual machine reboot.
Monitors The number of monitors for the virtual machine. This option is only available for virtual desktops using the SPICE display protocol. You can choose 1, 2 or 4. Note that multiple monitors are not supported for Windows 8 and Windows Server 2012 virtual machines.
Smartcard Enabled Smart cards are an external hardware security feature, most commonly seen in credit cards, but also used by many businesses as authentication tokens. Smart cards can be used to protect oVirt virtual machines. Tick or untick the check box to activate and deactivate Smart card authentication for individual virtual machines.
Disable strict user checking

Click the Advanced Parameters arrow and select the check box to use this option. With this option selected, the virtual machine does not need to be rebooted when a different user connects to it.

By default, strict checking is enabled so that only one user can connect to the console of a virtual machine. No other user is able to open a console to the same virtual machine until it has been rebooted. The exception is that a SuperUser can connect at any time and replace a existing connection. When a SuperUser has connected, no normal user can connect again until the virtual machine is rebooted.

Disable strict checking with caution, because you can expose the previous user's session to the new user.

Soundcard Enabled A sound card device is not necessary for all virtual machine use cases. If it is for yours, enable a sound card here.
Enable SPICE file transfer Defines whether a user is able to drag and drop files from an external host into the virtual machine’s SPICE console. This option is only available for virtual machines using the SPICE protocol. This check box is selected by default.
Enable SPICE clipboard copy and paste Defines whether a user is able to copy and paste content from an external host into the virtual machine’s SPICE console. This option is only available for virtual machines using the SPICE protocol. This check box is selected by default.
Serial Console Section
Enable VirtIO serial console The VirtIO serial console is emulated through VirtIO channels, using SSH and key pairs, and allows you to access a virtual machine's serial console directly from a client machine's command line, instead of opening a console from the Administration Portal or the User Portal. The serial console requires direct access to the Engine, since the Engine acts as a proxy for the connection, provides information about virtual machine placement, and stores the authentication keys. Select the check box to enable the VirtIO console on the virtual machine.

Virtual Machine Host Settings Explained

The following table details the options available on the Host tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: Host Settings

Field Name Sub-element Description
Start Running On

Defines the preferred host on which the virtual machine is to run. Select either:

  • Any Host in Cluster - The virtual machine can start and run on any available host in the cluster.
  • Specific - The virtual machine will start running on a particular host in the cluster. However, the Engine or an administrator can migrate the virtual machine to a different host in the cluster depending on the migration and high-availability settings of the virtual machine. Select the specific host or group of hosts from the list of available hosts.
Migration Options Migration mode

Defines options to run and migrate the virtual machine. If the options here are not used, the virtual machine will run or migrate according to its cluster's policy.

  • Allow manual and automatic migration - The virtual machine can be automatically migrated from one host to another in accordance with the status of the environment, or manually by an administrator.
  • Allow manual migration only - The virtual machine can only be migrated from one host to another manually by an administrator.
  • Do not allow migration - The virtual machine cannot be migrated, either automatically or manually.
Use custom migration policy

Defines the migration convergence policy. If the check box is left unselected, the host determines the policy.

  • Legacy - Legacy behavior of 3.6 version. Overrides in vdsm.conf are still applied. The guest agent hook mechanism is disabled.
  • Minimal downtime - Allows the virtual machine to migrate in typical situations. Virtual machines should not experience any significant downtime. The migration will be aborted if virtual machine migration does not converge after a long time (dependent on QEMU iterations, with a maximum of 500 milliseconds). The guest agent hook mechanism is enabled.
  • Suspend workload if needed - Allows the virtual machine to migrate in most situations, including when the virtual machine is running a heavy workload. Virtual machines may experience a more significant downtime. The migration may still be aborted for extreme workloads. The guest agent hook mechanism is enabled.
Use custom migration downtime This check box allows you to specify the maximum number of milliseconds the virtual machine can be down during live migration. Configure different maximum downtimes for each virtual machine according to its workload and SLA requirements. Enter 0 to use the VDSM default value.
Auto Converge migrations

Only activated with the Legacy migration policy. Allows you to set whether auto-convergence is used during live migration of the virtual machine. Large virtual machines with high workloads can dirty memory more quickly than the transfer rate achieved during live migration, and prevent the migration from converging. Auto-convergence capabilities in QEMU allow you to force convergence of virtual machine migrations. QEMU automatically detects a lack of convergence and triggers a throttle-down of the vCPUs on the virtual machine. Auto-convergence is disabled globally by default.

  • Select Inherit from cluster setting to use the auto-convergence setting that is set at the cluster level. This option is selected by default.
  • Select Auto Converge to override the cluster setting or global setting and allow auto-convergence for the virtual machine.
  • Select Don't Auto Converge to override the cluster setting or global setting and prevent auto-convergence for the virtual machine.
Enable migration compression

Only activated with the Legacy migration policy. The option allows you to set whether migration compression is used during live migration of the virtual machine. This feature uses Xor Binary Zero Run-Length-Encoding to reduce virtual machine downtime and total live migration time for virtual machines running memory write-intensive workloads or for any application with a sparse memory update pattern. Migration compression is disabled globally by default.

  • Select Inherit from cluster setting to use the compression setting that is set at the cluster level. This option is selected by default.
  • Select Compress to override the cluster setting or global setting and allow compression for the virtual machine.
  • Select Don't compress to override the cluster setting or global setting and prevent compression for the virtual machine.
Pass-Through Host CPU This check box allows virtual machines to take advantage of the features of the physical CPU of the host on which they are situated. This option can only be enabled when Do not allow migration is selected.
Configure NUMA NUMA Node Count The number of virtual NUMA nodes to assign to the virtual machine. If the Tune Mode is Preferred, this value must be set to 1.
Tune Mode

The method used to allocate memory.

  • Strict: Memory allocation will fail if the memory cannot be allocated on the target node.
  • Preferred: Memory is allocated from a single preferred node. If sufficient memory is not available, memory can be allocated from other nodes.
  • Interleave: Memory is allocated across nodes in a round-robin algorithm.
NUMA Pinning Opens the NUMA Topology window. This window shows the host's total CPUs, memory, and NUMA nodes, and the virtual machine's virtual NUMA nodes. Pin virtual NUMA nodes to host NUMA nodes by clicking and dragging each vNUMA from the box on the right to a NUMA node on the left.

Virtual Machine High Availability Settings Explained

The following table details the options available on the High Availability tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: High Availability Settings

Field Name Description
Highly Available

Select this check box if the virtual machine is to be highly available. For example, in cases of host maintenance, all virtual machines are automatically live migrated to another host. If the host crashed and is in a non-responsive state, only virtual machines with high availability are restarted on another host. If the host is manually shut down by the system administrator, the virtual machine is not automatically live migrated to another host.

Note that this option is unavailable if the Migration Options setting in the Hosts tab is set to either Allow manual migration only or Do not allow migration. For a virtual machine to be highly available, it must be possible for the Engine to migrate the virtual machine to other available hosts as necessary.

Target Storage Domain for VM Lease

Select the storage domain to hold a virtual machine lease, or select **No VM Lease** to disable the functionality. When a storage domain is selected, it will hold a virtual machine lease on a special volume that allows the virtual machine to be started on another host if the original host loses power or becomes unresponsive.

This functionality is only available on storage domain V4 or later.

**Note:** If you define a lease, the only Resume Behavior available is KILL.

Resume Behavior

Defines the desired behavior of a virtual machine that is paused due to storage I/O errors, once a connection with the storage is reestablished. You can define the desired resume behavior even if the virtual machine is not highly available.

The following options are available:

  • **AUTO_RESUME** - The virtual machine is automatically resumed, without requiring user intervention. This is recommended for virtual machines that are not highly available and that do not require user intervention after being in the paused state.
  • **LEAVE_PAUSED** - The virtual machine remains in pause mode until it is manually resumed or restarted.
  • **KILL** - The virtual machine is automatically resumed if the I/O error is remedied within 80 seconds. However, if more than 80 seconds pass, the virtual machine is ungracefully shut down. This is recommended for highly available virtual machines, to allow the Manager to restart them on another host that is not experiencing the storage I/O error.
    **KILL** is the only option available when using virtual machine leases.
Priority for Run/Migration queue Sets the priority level for the virtual machine to be migrated or restarted on another host.
Watchdog

Allows users to attach a watchdog card to a virtual machine. A watchdog is a timer that is used to automatically detect and recover from failures. Once set, a watchdog timer continually counts down to zero while the system is in operation, and is periodically restarted by the system to prevent it from reaching zero. If the timer reaches zero, it signifies that the system has been unable to reset the timer and is therefore experiencing a failure. Corrective actions are then taken to address the failure. This functionality is especially useful for servers that demand high availability.

Watchdog Model: The model of watchdog card to assign to the virtual machine. At current, the only supported model is i6300esb.

Watchdog Action: The action to take if the watchdog timer reaches zero. The following actions are available:

  • none - No action is taken. However, the watchdog event is recorded in the audit log.
  • reset - The virtual machine is reset and the Engine is notified of the reset action.
  • poweroff - The virtual machine is immediately shut down.
  • dump - A dump is performed and the virtual machine is paused.
  • pause - The virtual machine is paused, and can be resumed by users.

Virtual Machine Resource Allocation Settings Explained

The following table details the options available on the Resource Allocation tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: Resource Allocation Settings

Field Name Sub-element Description
CPU Allocation CPU Profile The CPU profile assigned to the virtual machine. CPU profiles define the maximum amount of processing capability a virtual machine can access on the host on which it runs, expressed as a percent of the total processing capability available to that host. CPU profiles are defined on the cluster level based on quality of service entries created for data centers.
CPU Shares

Allows users to set the level of CPU resources a virtual machine can demand relative to other virtual machines.

  • Low - 512
  • Medium - 1024
  • High - 2048
  • Custom - A custom level of CPU shares defined by the user.
CPU Pinning topology

Enables the virtual machine's virtual CPU (vCPU) to run on a specific physical CPU (pCPU) in a specific host. The syntax of CPU pinning is v#p[_ v#p], for example:

  • 0#0 - Pins vCPU 0 to pCPU 0.
  • 0#0_1#3 - Pins vCPU 0 to pCPU 0, and pins vCPU 1 to pCPU 3.
  • 1#1-4,^2 - Pins vCPU 1 to one of the pCPUs in the range of 1 to 4, excluding pCPU 2.

In order to pin a virtual machine to a host, you must also select the following on the Host tab:

  • Start Running On: Specific
  • Migration Options: Do not allow migration
  • Pass-Through Host CPU

If CPU pinning is set and you change **Start Running On: Specific** or **Migration Options: Do not allow migration**, a **CPU pinning topology will be lost** window appears when you click **OK**.

Memory Allocation Physical Memory Guaranteed The amount of physical memory guaranteed for this virtual machine. Should be any number between 0 and the defined memory for this virtual machine.
Memory Balloon Device Enabled Enables the memory balloon device for this virtual machine. Enable this setting to allow memory overcommitment in a cluster. Enable this setting for applications that allocate large amounts of memory suddenly but set the guaranteed memory to the same value as the defined memory.Use ballooning for applications and loads that slowly consume memory, occasionally release memory, or stay dormant for long periods of time, such as virtual desktops.
IO Threads IO Threads Enabled Enables virtio-blk data plane. Select this check box to improve the speed of disks that have a VirtIO interface by pinning them to a thread separate from the virtual machine's other functions. Improved disk performance increases a virtual machine's overall performance. Disks with VirtIO interfaces are pinned to an IO thread using a round-robin algorithm.
Queues Multi Queues Enabled

Enables multiple queues. This check box is selected by default. It creates up to four queues per vNIC, depending on how many vCPUs are available.

It is possible to define a different number of queues per vNIC by creating a custom property as follows:

engine-config -s "CustomDeviceProperties={type=interface;prop={other-nic-properties;queues=[1-9][0-9]\*}}"

where other-nic-properties is a semicolon-separated list of pre-existing NIC custom properties.

Storage Allocation The **Storage Allocation** option is only available when the virtual machine is created from a template.
Thin Provides optimized usage of storage capacity. Disk space is allocated only as it is required.
Clone Optimized for the speed of guest read and write operations. All disk space requested in the template is allocated at the time of the clone operation.
VirtIO-SCSI Enabled Allows users to enable or disable the use of VirtIO-SCSI on the virtual machines.
Disk Allocation The **Disk Allocation** option is only available when you are creating a virtual machine from a template.
Alias An alias for the virtual disk. By default, the alias is set to the same value as that of the template.
Virtual Size The total amount of disk space that the virtual machine based on the template can use. This value cannot be edited, and is provided for reference only.
Format The format of the virtual disk. The available options are **QCOW2** and **Raw**. When **Storage Allocation** is **Thin**, the disk format is **QCOW2**. When Storage Allocation is **Clone**, select **QCOW2** or **Raw**.
Target The storage domain on which the virtual disk is stored. By default, the storage domain is set to the same value as that of the template.
Disk Profile The disk profile to assign to the virtual disk. Disk profiles are created based on storage profiles defined in the data centers.

Virtual Machine Boot Options Settings Explained

The following table details the options available on the Boot Options tab of the New Virtual Machine and Edit Virtual Machine windows

Virtual Machine: Boot Options Settings

Field Name Description
First Device

After installing a new virtual machine, the new virtual machine must go into Boot mode before powering up. Select the first device that the virtual machine must try to boot:

  • Hard Disk
  • CD-ROM
  • Network (PXE)
Second Device Select the second device for the virtual machine to use to boot if the first device is not available. The first device selected in the previous option does not appear in the options.
Attach CD If you have selected CD-ROM as a boot device, tick this check box and select a CD-ROM image from the drop-down menu. The images must be available in the ISO domain.
Enable menu to select boot device Enables a menu to select the boot device. After the virtual machine starts and connects to the console, but before the virtual machine starts booting, a menu displays that allows you to select the boot device. This option should be enabled before the initial boot to allow you to select the required installation media.

Virtual Machine Random Generator Settings Explained

The following table details the options available on the Random Generator tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: Random Generator Settings

Field Name Description
Random Generator enabled Selecting this check box enables a paravirtualized Random Number Generator PCI device (virtio-rng). This device allows entropy to be passed from the host to the virtual machine in order to generate a more sophisticated random number. Note that this check box can only be selected if the RNG device exists on the host and is enabled in the host's cluster.
Period duration (ms) Specifies the duration of a period in milliseconds. If omitted, the libvirt default of 1000 milliseconds (1 second) is used. If this field is filled, Bytes per period must be filled also.
Bytes per period Specifies how many bytes are permitted to be consumed per period.
Device source:

The source of the random number generator. This is automatically selected depending on the source supported by the host's cluster.

  • /dev/random source - The Linux-provided random number generator.
  • /dev/hwrng source - An external hardware generator.

Virtual Machine Custom Properties Settings Explained

The following table details the options available on the Custom Properties tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: Custom Properties Settings

Field Name Description Recommendations and Limitations
sap_agent Enables SAP monitoring on the virtual machine. Set to true or false. -
sndbuf Enter the size of the buffer for sending the virtual machine's outgoing data over the socket. Default value is 0. -
vhost

Disables vhost-net, which is the kernel-based virtio network driver on virtual network interface cards attached to the virtual machine. To disable vhost, the format for this property is:

LogicalNetworkName: false

This will explicitly start the virtual machine without the vhost-net setting on the virtual NIC attached to `LogicalNetworkName`.

vhost-net provides better performance than virtio-net, and if it is present, it is enabled on all virtual machine NICs by default. Disabling this property makes it easier to isolate and diagnose performance issues, or to debug vhost-net errors; for example, if migration fails for virtual machines on which vhost does not exist.
viodiskcache Caching mode for the virtio disk. writethrough writes data to the cache and the disk in parallel, writeback does not copy modifications from the cache to the disk, and none disables caching. If viodiskcache is enabled, the virtual machine cannot be live migrated.

Warning: Increasing the value of the sndbuf custom property results in increased occurrences of communication failure between hosts and unresponsive virtual machines.

Virtual Machine Icon Settings Explained

You can add custom icons to virtual machines and templates. Custom icons can help to differentiate virtual machines in the User Portal. The following table details the options available on the Icon tab of the New Virtual Machine and Edit Virtual Machine windows.

Virtual Machine: Icon Settings

Button Name Description
Upload

Click this button to select a custom image to use as the virtual machine's icon. The following limitations apply:

  • Supported formats: jpg, png, gif
  • Maximum size: 24 KB
  • Maximum dimensions: 150px width, 120px height
Use default Click this button to set the operating system's default image as the virtual machine's icon.

Virtual Machine Foreman/Satellite Settings Explained

The following table details the options available on the Foreman/Satellite tab of the New Virtual Machine and Edit Virtual Machine windows

Virtual Machine:Foreman/Satellite Settings

Field Name Description
Provider If the virtual machine is running Enterprise Linux and the system is configured to work with a Foreman server, select the name of the Foreman from the list. This enables you to use Foreman's content management feature to display the relevant Errata for this virtual machine.

Explanation of Settings in the Run Once Window

The Run Once window defines one-off boot options for a virtual machine. For persistent boot options, use the Boot Options tab in the New Virtual Machine window. The Run Once window contains multiple sections that can be configured.

The standalone Rollback this configuration during reboots check box specifies whether reboots (initiated by the Engine, or from within the guest) will be warm (soft) or cold (hard). Select this check box to configure a cold reboot that restarts the virtual machine with regular (non-Run Once) configuration. Clear this check box to configure a warm reboot that retains the virtual machine’s Run Once configuration.

The Boot Options section defines the virtual machine’s boot sequence, running options, and source images for installing the operating system and required drivers.

Boot Options Section

Field Name Description
Attach Floppy Attaches a diskette image to the virtual machine. Use this option to install Windows drivers. The diskette image must reside in the ISO domain.
Attach CD Attaches an ISO image to the virtual machine. Use this option to install the virtual machine’s operating system and applications. The CD image must reside in the ISO domain.
Enable menu to select boot device Enables a menu to select the boot device. After the virtual machine starts and connects to the console, but before the virtual machine starts booting, a menu displays that allows you to select the boot device. This option should be enabled before the initial boot to allow you to select the required installation media.
Start in Pause Mode Starts then pauses the virtual machine to enable connection to the console, suitable for virtual machines in remote locations.
Predefined Boot Sequence Determines the order in which the boot devices are used to boot the virtual machine. Select Hard Disk, CD-ROM, or Network (PXE), and use Up and Down to move the option up or down in the list.
Run Stateless Deletes all changes to the virtual machine upon shutdown. This option is only available if a virtual disk is attached to the virtual machine.

The Linux Boot Options section contains fields to boot a Linux kernel directly instead of through the BIOS bootloader.

Linux Boot Options Section

Field Name Description
kernel path A fully qualified path to a kernel image to boot the virtual machine. The kernel image must be stored on either the ISO domain (path name in the format of iso://path-to-image) or on the host’s local storage domain (path name in the format of /data/images).
initrd path A fully qualified path to a ramdisk image to be used with the previously specified kernel. The ramdisk image must be stored on the ISO domain (path name in the format of iso://path-to-image) or on the host’s local storage domain (path name in the format of /data/images).
kernel parameters Kernel command line parameter strings to be used with the defined kernel on boot.

The Initial Run section is used to specify whether to use Cloud-Init or Sysprep to initialize the virtual machine. For Linux-based virtual machines, you must select the Use Cloud-Init check box in the Initial Run tab to view the available options. For Windows-based virtual machines, you must attach the [sysprep] floppy by selecting the Attach Floppy check box in the Boot Options tab and selecting the floppy from the list.

The options that are available in the Initial Run section differ depending on the operating system that the virtual machine is based on.

Initial Run Section (Linux-based Virtual Machines)

Field Name Description
VM Hostname The host name of the virtual machine.
Configure Time Zone The time zone for the virtual machine. Select this check box and select a time zone from the Time Zone list.
Authentication The authentication details for the virtual machine. Click the disclosure arrow to display the settings for this option.
Authentication → User Name Creates a new user account on the virtual machine. If this field is not filled in, the default user is root.
Authentication → Use already configured password This check box is automatically selected after you specify an initial root password. You must clear this check box to enable the Password and Verify Password fields and specify a new password.
Authentication → Password The root password for the virtual machine. Enter the password in this text field and the Verify Password text field to verify the password.
Authentication → SSH Authorized Keys SSH keys to be added to the authorized keys file of the virtual machine.
Authentication → Regenerate SSH Keys Regenerates SSH keys for the virtual machine.
Networks Network-related settings for the virtual machine. Click the disclosure arrow to display the settings for this option.
Networks → DNS Servers The DNS servers to be used by the virtual machine.
**Networks → DNS Search Domains ** The DNS search domains to be used by the virtual machine.
Networks → Network Configures network interfaces for the virtual machine. Select this check box and click + or - to add or remove network interfaces to or from the virtual machine. When you click +, a set of fields becomes visible that can specify whether to use DHCP, and configure an IP address, netmask, and gateway, and specify whether the network interface will start on boot.
Custom Script Custom scripts that will be run on the virtual machine when it starts. The scripts entered in this field are custom YAML sections that are added to those produced by the Engine, and allow you to automate tasks such as creating users and files, configuring yum repositories and running commands. For more information on the format of scripts that can be entered in this field, see the Custom Script documentation.

Initial Run Section (Windows-based Virtual Machines)

Field Name Description
VM Hostname The host name of the virtual machine.
Domain The Active Directory domain to which the virtual machine belongs.
Organization Name The name of the organization to which the virtual machine belongs. This option corresponds to the text field for setting the organization name displayed when a machine running Windows is started for the first time.
Active Directory OU The organizational unit in the Active Directory domain to which the virtual machine belongs. The distinguished name must be provided. For example CN=Users,DC=lab,DC=local
Configure Time Zone The time zone for the virtual machine. Select this check box and select a time zone from the Time Zone list.
Admin Password The administrative user password for the virtual machine. Click the disclosure arrow to display the settings for this option.
Admin Password → Use already configured password This check box is automatically selected after you specify an initial administrative user password. You must clear this check box to enable the Admin Password and Verify Admin Password fields and specify a new password.
Admin Password → Admin Password The administrative user password for the virtual machine. Enter the password in this text field and the Verify Admin Password text field to verify the password.
Custom Locale Locales must be in a format such as en-US. Click the disclosure arrow to display the settings for this option.
Custom Locale → Input Locale The locale for user input.
Custom Locale → UI Language The language used for user interface elements such as buttons and menus.
Custom Locale → System Locale The locale for the overall system.
Custom Locale → User Locale The locale for users.
Sysprep A custom Sysprep definition. The definition must be in the format of a complete unattended installation answer file. You can copy and paste the default answer files in the /usr/share/ovirt-engine/conf/sysprep/ directory on the machine on which the oVirt Engine is installed and alter the fields as required. The definition will overwrite any values entered in the Initial Run fields.
Domain The Active Directory domain to which the virtual machine belongs. If left blank, the value of the previous Domain field is used.
Alternate Credentials Selecting this check box allows you to set a User Name and Password as alternative credentials.

The System section enables you to define the supported machine type or CPU type.

System Section

Field Name Description
Custom Emulated Machine This option allows you to specify the machine type. If changed, the virtual machine will only run on hosts that support this machine type. Defaults to the cluster’s default machine type.
Custom CPU Type This option allows you to specify a CPU type. If changed, the virtual machine will only run on hosts that support this CPU type. Defaults to the cluster’s default CPU type.

The Host section is used to define the virtual machine’s host.

Host Section

Field Name Description
Any host in cluster Allocates the virtual machine to any available host.
Specific Specifies a user-defined host for the virtual machine.

The Console section defines the protocol to connect to virtual machines.

Console Section

Field Name Description
Headless Mode Select this option if you do not require a graphical console when running the machine for the first time.
VNC Requires a VNC client to connect to a virtual machine using VNC. Optionally, specify VNC Keyboard Layout from the drop-down list.
SPICE Recommended protocol for Linux and Windows virtual machines. Using SPICE protocol without QXL drivers is supported for Windows 8 and Server 2012 virtual machines; however, support for multiple monitors and graphics acceleration is not available for this configuration.
Enable SPICE file transfer Determines whether you can drag and drop files from an external host into the virtual machine’s SPICE console. This option is only available for virtual machines using the SPICE protocol. This check box is selected by default.
Enable SPICE clipboard copy and paste Defines whether you can copy and paste content from an external host into the virtual machine’s SPICE console. This option is only available for virtual machines using the SPICE protocol. This check box is selected by default.

The Custom Properties section contains additional VDSM options for running virtual machines.

Custom Properties Section

Field Name Description
sndbuf Enter the size of the buffer for sending the virtual machine’s outgoing data over the socket.
vhost Enter the name of the virtual host on which this virtual machine should run. The name can contain any combination of letters and numbers.
viodiskcache Caching mode for the virtio disk. writethrough writes data to the cache and the disk in parallel, writeback does not copy modifications from the cache to the disk, and none disables caching.
sap_agent Enables SAP monitoring on the virtual machine. Set to true or false.

Explanation of Settings in the New Network Interface and Edit Network Interface windows

These settings apply when you are adding or editing a virtual machine network interface. If you have more than one network interface attached to a virtual machine, you can put the virtual machine on more than one logical network.

Network Interface Settings

Field Name Description
Name The name of the network interface. This text field has a 21-character limit and must be a unique name with any combination of uppercase and lowercase letters, numbers, hyphens, and underscores.
Profile The vNIC profile and logical network that the network interface is placed on. By default, all network interfaces are put on the ovirtmgmt management network.
Type

The virtual interface the network interface presents to virtual machines.

  • rtl8139 and e1000 device drivers are included in most operating systems.
  • VirtIO is faster but requires VirtIO drivers. Enterprise Linux 5 and later include VirtIO drivers. Windows does not include VirtIO drivers, but they can be installed from the guest tools ISO or virtual floppy disk.
  • PCI Passthrough enables the vNIC to be directly connected to a virtual function (VF) of an SR-IOV-enabled NIC. The vNIC will then bypass the software network virtualization and connect directly to the VF for direct device assignment. The selected vNIC profile must also have Passthrough enabled.
Custom MAC address Choose this option to set a custom MAC address. The oVirt Engine automatically generates a MAC address that is unique to the environment to identify the network interface. Having two devices with the same MAC address online in the same network causes networking conflicts.
Link State

Whether or not the network interface is connected to the logical network.

  • Up: The network interface is located on its slot.

    • When the Card Status is Plugged, it means the network interface is connected to a network cable, and is active.
    • When the Card Status is Unplugged, the network interface will automatically be connected to the network and become active once plugged.
  • Down: The network interface is located on its slot, but it is not connected to any network. Virtual machines will not be able to run in this state.
Card Status

Whether or not the network interface is defined on the virtual machine.

  • Plugged: The network interface has been defined on the virtual machine.

    • If its Link State is Up, it means the network interface is connected to a network cable, and is active.
    • If its Link State is Down, the network interface is not connected to a network cable.
  • Unplugged: The network interface is only defined on the Manager, and is not associated with a virtual machine.

    • If its Link State is Up, when the network interface is plugged it will automatically be connected to a network and become active.
    • If its Link State is Down, the network interface is not connected to any network until it is defined on a virtual machine.

Explanation of Settings in the New Virtual Disk and Edit Virtual Disk windows

New Virtual Disk and Edit Virtual Disk Settings: Image

Field Name Description
Size(GB) The size of the new virtual disk in GB.
Alias The name of the virtual disk, limited to 40 characters.
Description A description of the virtual disk. This field is recommended but not mandatory.
Interface

The virtual interface the disk presents to virtual machines. VirtIO is faster, but requires drivers. Red Hat Enterprise Linux 5 and later include these drivers. Windows does not include these drivers, but they can be installed from the guest tools ISO or virtual floppy disk. IDE devices do not require special drivers.

The interface type can be updated after stopping all virtual machines that the disk is attached to.

Data Center The data center in which the virtual disk will be available.
Storage Domain The storage domain in which the virtual disk will be stored. The drop-down list shows all storage domains available in the given data center, and also shows the total space and currently available space in the storage domain.
Allocation Policy

The provisioning policy for the new virtual disk.

  • Preallocated allocates the entire size of the disk on the storage domain at the time the virtual disk is created. The virtual size and the actual size of a preallocated disk are the same. Preallocated virtual disks take more time to create than thin provisioned virtual disks, but have better read and write performance. Preallocated virtual disks are recommended for servers and other I/O intensive virtual machines. If a virtual machine is able to write more than 1 GB every four seconds, use preallocated disks where possible.
  • Thin Provision allocates 1 GB at the time the virtual disk is created and sets a maximum limit on the size to which the disk can grow. The virtual size of the disk is the maximum limit; the actual size of the disk is the space that has been allocated so far. Thin provisioned disks are faster to create than preallocated disks and allow for storage over-commitment. Thin provisioned virtual disks are recommended for desktops.
Disk Profile The disk profile assigned to the virtual disk. Disk profiles define the maximum amount of throughput and the maximum level of input and output operations for a virtual disk in a storage domain. Disk profiles are defined on the storage domain level based on storage quality of service entries created for data centers.
Activate Disk(s) Activate the virtual disk immediately after creation. This option is not available when creating a floating disk.
Wipe After Delete Allows you to enable enhanced security for deletion of sensitive material when the virtual disk is deleted.
Bootable Allows you to enable the bootable flag on the virtual disk.
Shareable Allows you to attach the virtual disk to more than one virtual machine at a time.
Read Only Allows you to set the disk as read-only. The same disk can be attached as read-only to one virtual machine, and as rewritable to another. This option is not available when creating a floating disk.
Enable Discard Allows you to shrink a thin provisioned disk while the virtual machine is up. For block storage, the underlying storage device must support discard calls, and the option cannot be used with Wipe After Delete unless the underlying storage supports the discard_zeroes_data property. For file storage, the underlying file system and the block device must support discard calls. If all requirements are met, SCSI UNMAP commands issued from guest virtual machines is passed on by QEMU to the underlying storage to free up the unused space.

The Direct LUN settings can be displayed in either Targets > LUNs or LUNs > Targets. Targets > LUNs sorts available LUNs according to the host on which they are discovered, whereas LUNs > Targets displays a single list of LUNs.

New Virtual Disk and Edit Virtual Disk Settings: Direct LUN

Field Name Description
Alias The name of the virtual disk, limited to 40 characters.
Description

A description of the virtual disk. This field is recommended but not mandatory. By default the last 4 characters of the LUN ID is inserted into the field.

The default behavior can be configured by setting the PopulateDirectLUNDiskDescriptionWithLUNId configuration key to the appropriate value using the engine-config command. The configuration key can be set to -1 for the full LUN ID to be used, or 0 for this feature to be ignored. A positive integer populates the description with the corresponding number of characters of the LUN ID.

Interface

The virtual interface the disk presents to virtual machines. VirtIO is faster, but requires drivers. Red Hat Enterprise Linux 5 and later include these drivers. Windows does not include these drivers, but they can be installed from the guest tools ISO or virtual floppy disk. IDE devices do not require special drivers.

The interface type can be updated after stopping all virtual machines that the disk is attached to.

Data Center The data center in which the virtual disk will be available.
Use Host The host on which the LUN will be mounted. You can select any host in the data center.
Storage Type The type of external LUN to add. You can select from either iSCSI or Fibre Channel.
Discover Targets

This section can be expanded when you are using iSCSI external LUNs and Targets > LUNs is selected.

Address - The host name or IP address of the target server.

Port - The port by which to attempt a connection to the target server. The default port is 3260.

User Authentication - The iSCSI server requires User Authentication. The User Authentication field is visible when you are using iSCSI external LUNs.

CHAP user name - The user name of a user with permission to log in to LUNs. This field is accessible when the User Authentication check box is selected.

CHAP password - The password of a user with permission to log in to LUNs. This field is accessible when the User Authentication check box is selected.

Activate Disk(s) Activate the virtual disk immediately after creation. This option is not available when creating a floating disk.
Bootable Allows you to enable the bootable flag on the virtual disk.
Shareable Allows you to attach the virtual disk to more than one virtual machine at a time.
Read Only Allows you to set the disk as read-only. The same disk can be attached as read-only to one virtual machine, and as rewritable to another. This option is not available when creating a floating disk.
Enable Discard Allows you to shrink a thin provisioned disk while the virtual machine is up. With this option enabled, SCSI UNMAP commands issued from guest virtual machines is passed on by QEMU to the underlying storage to free up the unused space.
Enable SCSI Pass-Through

Available when the Interface is set to VirtIO-SCSI. Selecting this check box enables passthrough of a physical SCSI device to the virtual disk. A VirtIO-SCSI interface with SCSI passthrough enabled automatically includes SCSI discard support. Read Only is not supported when this check box is selected.

When this check box is not selected, the virtual disk uses an emulated SCSI device. Read Only is supported on emulated VirtIO-SCSI disks.

Allow Privileged SCSI I/O Available when the Enable SCSI Pass-Through check box is selected. Selecting this check box enables unfiltered SCSI Generic I/O (SG_IO) access, allowing privileged SG_IO commands on the disk. This is required for persistent reservations.
Using SCSI Reservation Available when the Enable SCSI Pass-Through and Allow Privileged SCSI I/O check boxes are selected. Selecting this check box disables migration for any virtual machine using this disk, to prevent virtual machines that are using SCSI reservation from losing access to the disk.

Fill in the fields in the Discover Targets section and click Discover to discover the target server. You can then click the Login All button to list the available LUNs on the target server and, using the radio buttons next to each LUN, select the LUN to add.

Using LUNs directly as virtual machine hard disk images removes a layer of abstraction between your virtual machines and their data.

The following considerations must be made when using a direct LUN as a virtual machine hard disk image:

  • Live storage migration of direct LUN hard disk images is not supported.

  • Direct LUN disks are not included in virtual machine exports.

  • Direct LUN disks are not included in virtual machine snapshots.

The Cinder settings form will be disabled if there are no available OpenStack Volume storage domains on which you have permissions to create a disk in the relevant Data Center. Cinder disks require access to an instance of OpenStack Volume that has been added to the oVirt environment using the External Providers window.

New Virtual Disk and Edit Virtual Disk Settings: Cinder

Field Name Description
Size(GB) The size of the new virtual disk in GB.
Alias The name of the virtual disk, limited to 40 characters.
Description A description of the virtual disk. This field is recommended but not mandatory.
Interface

The virtual interface the disk presents to virtual machines. VirtIO is faster, but requires drivers. Red Hat Enterprise Linux 5 and later include these drivers. Windows does not include these drivers, but they can be installed from the guest tools ISO or virtual floppy disk. IDE devices do not require special drivers.

The interface type can be updated after stopping all virtual machines that the disk is attached to.

Data Center The data center in which the virtual disk will be available.
Storage Domain The storage domain in which the virtual disk will be stored. The drop-down list shows all storage domains available in the given data center, and also shows the total space and currently available space in the storage domain.
Volume Type The volume type of the virtual disk. The drop-down list shows all available volume types. The volume type will be managed and configured on OpenStack Cinder.
Activate Disk(s) Activate the virtual disk immediately after creation. This option is not available when creating a floating disk.
Bootable Allows you to enable the bootable flag on the virtual disk.
Shareable Allows you to attach the virtual disk to more than one virtual machine at a time.
Read Only Allows you to set the disk as read-only. The same disk can be attached as read-only to one virtual machine, and as rewritable to another. This option is not available when creating a floating disk.

Important: Mounting a journaled file system requires read-write access. Using the Read Only option is not appropriate for virtual disks that contain such file systems (e.g. EXT3, EXT4, or XFS).

Explanation of Settings in the New Template Windows

The following table details the settings for the New Template window.

New Template Settings

Field Description/Action
Name The name of the template. This is the name by which the template is listed in the Templates tab in the Administration Portal and is accessed via the REST API. This text field has a 40-character limit and must be a unique name within the data center with any combination of uppercase and lowercase letters, numbers, hyphens, and underscores. The name can be reused in different data centers in the environment.
Description A description of the template. This field is recommended but not mandatory.
Comment A field for adding plain text, human-readable comments regarding the template.
Cluster The cluster with which the template is associated. This is the same as the original virtual machines by default. You can select any cluster in the data center.
CPU Profile The CPU profile assigned to the template. CPU profiles define the maximum amount of processing capability a virtual machine can access on the host on which it runs, expressed as a percent of the total processing capability available to that host. CPU profiles are defined on the cluster level based on quality of service entries created for data centers.
Create as a Template Sub-Version

Specifies whether the template is created as a new version of an existing template. Select this check box to access the settings for configuring this option.

  • Root Template: The template under which the sub-template is added.
  • Sub-Version Name: The name of the template. This is the name by which the template is accessed when creating a new virtual machine based on the template. If the virtual machine is stateless, the list of sub-versions will contain a latest option rather than the name of the latest sub-version. This option automatically applies the latest template sub-version to the virtual machine upon reboot. Sub-versions are particularly useful when working with pools of stateless virtual machines.
Disks Allocation

Alias - An alias for the virtual disk used by the template. By default, the alias is set to the same value as that of the source virtual machine.

Virtual Size - The total amount of disk space that a virtual machine based on the template can use. This value cannot be edited, and is provided for reference only. This value corresponds with the size, in GB, that was specified when the disk was created or edited.

Format - The format of the virtual disk used by the template. The available options are QCOW2 and Raw. By default, the format is set to Raw.

Target - The storage domain on which the virtual disk used by the template is stored. By default, the storage domain is set to the same value as that of the source virtual machine. You can select any storage domain in the cluster.

Disk Profile - The disk profile to assign to the virtual disk used by the template. Disk profiles are created based on storage profiles defined in the data centers.

Allow all users to access this Template Specifies whether a template is public or private. A public template can be accessed by all users, whereas a private template can only be accessed by users with the TemplateAdmin or SuperUser roles.
Copy VM permissions Copies explicit permissions that have been set on the source virtual machine to the template.
Seal Template (Linux only) Specifies whether a template is sealed. 'Sealing' is an operation that erases all machine-specific configurations from a filesystem, including SSH keys, UDEV rules, MAC addresses, system ID, and hostname. This setting prevents a virtual machine based on this template from inheriting the configuration of the source virtual machine.

Prev: Chapter 7: Templates Next: Appendix B: virt-sysprep Operations

Adapted from RHV 4.2 documentation - CC-BY-SA