• Cores: Number of CPU cores in the VM.
• Cores per Socket: Number of CPU cores allocated per socket in the VM.
• CPU Mode: Whether to match VM CPU model with host CPU model to inherit host CPU features. Default: None. For more information, see VM CPU
• CPU Resource Priority: For critical VMs, set to High to gain higher CPU contention capability when host is overloaded. For more information, see VM Resource Contention.
• CPU Clock Speed Limit: Set the upper limit of host CPU resources that a VM can occupy. Valid range: 1% to 100%. 100% or blank means no limit.
• CPU NUMA Binding: Bind the virtual machine's CPU (vCPU) to the host's CPU (pCPU) to improve its performance. For more information, see VM Resource Contention.
• CPU Hot Plug: Whether to support online CPU modification. Default: enabled. CPU hot-plugging and memory hot-plugging must be enabled or disabled together.
  Note: Only some operating systems support hot-plugging. You can click View to check supported OS list.
• CPU Hypervisor Tag: Whether to enable the virtualization (hypervisor) flag. If disabled, skips the VM virtualization environment detection by applications. Default: enabled.

• Memory: VM memory capacity.
• Memory Resource Priority: For critical VMs, set to High to gain higher memory contention capability when host is overloaded. For more information, see VM Resource Contention.
• Memory Hot Plug: Whether to support online memory modification. Default: enabled. CPU hot-plugging and memory hot-plugging must be enabled or disabled together.
  Note: Only some operating systems support hot-plugging. You can click View to check supported OS list.

• Storage Location: Data storage location for VM disk. Uses automatic allocation if not specified.
• Capacity: System disk capacity when creating new disk.
  Note:

  • When the capacity unit is set to MB and the automatically assigned storage location is ZBS distributed storage, the disk capacity will be automatically adjusted to 1 GB.
  • If the disk storage location is specified as ZBS distributed storage, the available units are GB and TB.
• System Image: Select a system image when using system image. Supported format: raw and qcow2.
• Bus Type: Specify the bus type for a virtual machine's disk. Options include Virtio, IDE, Virtio SCSI, and SCSI. By default, Disk 1 uses Virtio bus type on Linux systems, and IDE bus type on Windows and Other systems.
• Provision Method: Choose how to allocate disk storage space when using SAN storage. Default: thin provisioning.
  • Thin Provisioning: Allocates storage space based on actual usage, achieving higher storage utilization.
  • Thick Provisioning: Pre-allocates the required storage space when creating the disk, providing sufficient storage capacity and ensuring storage performance.
• Caching Mode: Whether to use host page cache for write operation and if used, whether the data is written to the storage device before returning success. Default: none.
• AIO Acceleration: Whether to enable asynchronous I/O (AIO) acceleration in the VM kernel. Default: disabled.
  Note: To enable AIO acceleration, make sure the cache mode is set to none.
• QoS: Whether to set read/write bandwidth and IOPS limits. Default: no limit. For more information, see VM QoS.

• NIC Model: Set the NIC model. Supported models: e1000, rtl8139, virtio, and SR-IOV.
• Port Group: The port group of the distributed switch for the VM NIC.
• State: Whether to automatically enable NIC when VM powers on.
• NIC Queue Number: Use multiple queues to send and receive network packets to improve network PPS and bandwidth performance.
• MAC Address: Specify a MAC address. Default: Auto Generated.
• Specify IP Address: Specify an IP address. Default: automatically assigned.

  If the selected distributed port group has DHCP service disabled, you can use VMTools to specify an IP address for the virtual machine For more information, see Virtual Machine VMTools.

• Assign DNS: Specify a DNS address. Default: Auto Allocated.
• Security Group: Associate security groups with the VM NIC to control east-west traffic. The smaller the number on the left side of the associated security group, the higher the priority for taking effect. For more information, see Security Group
  Note: Configure carefully to avoid rule conflicts between security groups.
• QoS: Whether to set bandwidth limits on packet transmission for the VM NIC. Default: no limit. For more information, see VM QoS.

Add multiple NICs by clicking Add Hardware > NIC.

• Graphics Card Type: Specify the default graphics card type when powering on a virtual machine. Supports vga, virtio, qxl, and cirrus, providing basic/high-definition/high-performance video functionality experiences. Default: vga for x86 VMs and virtio only for ARM VMs.
• Total Graphics Memory: Fixed at 16 MB for vga or cirrus. Configurable for qxl.
• Audio Card Type: Specify the default audio card type when powering on a virtual machine. Supports HDA (ICH6), HDA (ICH9), and AC97. Default: HDA (ICH6).
• Motherboard Type: Specify the default motherboard type when powering on a virtual machine. Supports i440fx and q35. Default: i440fx.

• Tag: Attach tags to identify VMs. For more information, see Tag Management.
• Hostname: VM hostname.
• VM Scheduling Group: Join a VM scheduling group for host allocation based on scheduling policies associated with the scheduling group. For more information, see VM Scheduling Policy.
• Sync with Host BIOS: Whether to synchronize the Windows VM BIOS clock with the host's BIOS clock. Default: disabled. For more information, see VM Time Synchronization.
• User Data: User-defined data. Upload custom parameters or scripts to perform custom configurations or specific tasks on the virtual machine. For more information, see VM User Data.

• Console Mode: VM console mode. Options include VNC (default), SPICE, VNC+SPICE.
• Console Password: VM console password. Supports manual input or random generation. Allowed characters: letters, numbers, and the following special characters: -`=[];',./~!@#$%^&*()_+|{}:"<>?

  You can specify whether to enforce setting a console password and password strength through VNC Console Password in the security settings. If enabled, you need to set the console password according to the specified strength requirements when creating a virtual machine.

• USB Redirection: Redirects USB devices from the VDI client to the VM. Default: disabled.

• None: Do not set login password or SSH key.
• Password: System login password for Linux VM (root) or Windows VM (administrator). Supports manual input or random generation. Allowed characters: letters, numbers, and the following special characters: -`=[];',./~!@#$%^&*()_+|{}:"<>?
  Note: Before setting the password, ensure that the virtual machine image has cloud-init installed.
• SSH Key: Inject SSH Key for password-free login to Linux VM.
  Note: Before injecting the SSH Key, ensure that the virtual machine image has cloud-init installed.

• Failure Response Policy: Set an automatic response action for VM failures (Windows BSOD or Linux guest hang). Options include No Action, Reboot, and Shut Down.
• Time Synchronization: Whether to automatically synchronize VM time with host system time. Default: enabled.

• Boot Order: OS boot priority sequence. Options include hard disk, CD-ROM, and network. By default, the BIOS boots from the hard disk, and if no boot device is found, it cannot load the system.
• BIOS Mode: The BIOS boot mode supports Legacy and UEFI. Legacy is the default in x86 clusters, while UEFI is the default in ARM clusters.
• BIOS Post Delay: BIOS screen timeout duration. Default: 10 seconds.

• Hide KVM Virtualization Flag: Controls CPU virtualization flag. When enabled, inserts <hidden state="on"> into the <kvm> element in the newly started VM XML. Default: disabled.
• VMware I/O Port Simulation: Whether to allow a KVM virtual machine to emulate the I/O ports in a VMware virtualization environment, making the KVM virtual machine compatible with VMware I/O port standards. Default: disabled.
  The main purposes of this option:

  • Migration and Compatibility: Allows migrating virtual machines from a VMware environment to a KVM environment, or running both VMware and KVM virtual machines in a mixed environment without significant configuration changes.
  • Testing and Development: Developers and testers can use KVM virtual machines to simulate a VMware environment to test applications or configurations in a VMware-like environment without requiring actual VMware licenses.
• Anti-Spoofing Mode: Whether to enable anti-IP/MAC spoofing and ARP deception features. When enabled, the virtual machine can only communicate with the outside world using the IP/MAC address allocated by the platform. Default: disabled.
• Cross-Cluster HA Policy: Whether VM HA migration supports cross-cluster.
  Note: This policy only affects automatic VM migrations in shared storage scenarios (distributed storage, NFS storage, SAN storage), such as VM migration in host maintenance or host replacement. This policy does not affect other actions such as manual hot migration of virtual machines (changing the host), specifying a host to start a VM, or dynamic resource scheduling (DRS) strategies that change the host.
• Hyper-V: Whether to enable Hyper-V emulation for the VM for nested virtualization scenarios in Windows systems. Default: disabled.
• EmulatorPin: Whether to assign all other threads than vCPU threads and IO threads of a VM to host physical CPUs (pCPUs). You can assign by NUMA nodes. Default: unassigned, which is virtual machine-related threads run on corresponding pCPUs according to system scheduling.
• Auto-Converge: Whether to enable auto-convergence mode for KVM virtual machine hot migrations. Default: disabled.

  If the virtual machine remains under high business load for a long time and the application is moderately sensitive to performance, it is recommended to enable auto-convergence mode to improve migration success rates.

• PCI Hot Plug: Whether to allow hot plugging of PCI devices in the virtual machine. Default: enabled.
  Note: If hardware compatibility errors occur during hot plugging or if the hardware device is not supported, you can disable this switch.
• CPU Vendor ID: If the virtual machine is running on a host with Hygon CPUs, it is recommended to set the VM's CPU vendor ID to AuthenticAMD to ensure compatibility with various operating systems and maintain normal VM operation. If set to None, certain operating systems may experience compatibility issues.
  Note: This parameter is hidden when the location of the virtual machine is set to either cluster or auto-allocated.