Hyper Converged Infrastructure (HCI/aSV)

Sangfor HCI and aSV provide a unified infrastructure combining compute, storage, networking, and built-in security to simplify deployment, operations, and services.
{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.1R1
{{sendMatomoQuery("Hyper Converged Infrastructure (HCI/aSV)","Advanced Configuration")}}

Advanced Configuration

{{ $t('productDocDetail.updateTime') }}: 2026-01-05

Description

This section instructs the administrator to configure the virtual machine's advanced options when or after the virtual machine is created.

Precautions

Supports editing the Advanced configurations of powered-on VMs, including Boot Order, Lifecycle, Hostname, Others, and Debugging. It is not recommended to modify Debugging by users. The following items require a VM restart to take effect: Boot Order, Enable disk encryption, Memory reclaiming, Support VirtIO, Filter page files, Disable Pause-Loop Exiting, Disable kvmclock, and Enable L3 cache.

Prerequisites

Some functions need to be adjusted, and the virtual machine needs to be shut down.

Steps

  1. Click the virtual machine name in the virtual machine list on the Compute page to enter the virtual machine information page.

  1. Click Edit to enter the Edit Virtual Machine page, and then click Advanced to enter the advanced configuration page of the virtual machine.

  1. Configure the following information

Boot Order: Specify the boot order for the virtual machine. You can choose an item (disk or CD/DVD) from the pull-down list.

Lifecycle: Specify the virtual machine’s lifecycle. It can be immortal or a specified expiration date. A powered-on virtual machine will occupy CPU and memory resources if it has not been used for a long period, while a powered-off virtual machine will occupy disk space if it has not been used for a long period. You can specify the Expiration Date for Lifecycle so that you may delete the expired virtual machine when the end of its lifecycle is reached.

Hostname: you can use the default hostname of the system or manually specify the hostname on this page. However, the virtual machine must install the vmTools to use this function. Before use, you need to check whether the operating system supports it on the page. After setting, you need to wait about a minute for it to take effect.

Power on at node startup: Once selected, the virtual machine will be automatically powered on once the node starts up.

Reboot if fault occurs: Once selected, the virtual machine will be automatically restarted in case of a stuck, blue screen. To make this option take effect, vmTools should be installed.

Enable UUID generator: Every time a UUID generator is enabled, a new UUID will be generated. Universally Unique Identifier, UUID in short, is an identifier of a virtual machine. Certain software running on the VM needs the UUID to work properly. Please do not change this since changes of UUID may cause some functionalities to be invalid. You may choose to re-generate UUID for the new virtual machine while cloning the virtual machines or to deploy the virtual machines from a template.

Enable network affinity: Enable NUMA node affinity for scenarios sensitive to network forwarding performance, such as latency and throughput. After this option is enabled, VMs are preferentially scheduled to the NUMA node to which the network forwarding core belongs, improving the VM network performance. This feature needs to work with the NUMA scheduler or exclusive CPU feature.

Regularly sync guest time with node: By default, the VM time is synchronized with the cluster time when the VM is powered on. If this option is selected, the synchronization will be scheduled at the specified interval. For details about the time synchronization setting, see section 10.14 "Modify Platform Date and Time." Note: This feature can be enabled only after vmTools is installed.

Enable TPM 2.0: For a VM running Windows 11, TPM 2.0 is enabled by default. UEFI is also enabled because enabling TPM requires UEFI firmware. You can enable or disable the vTPM feature when creating, editing, cloning VMs, and deploying VMs from templates.

Debugging: Users are not recommended to modify it by themselves. You can select Enable Turbo Mode when creating a VM running a Linux system. To enable and edit Turbo mode, refer to Section 5.1.1 Enable Turbo Service.

Go to the Tasks page of the VM to view the change details.