VM Configurations

On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. On the VM Instance page, click on the name of a VM instance. Then, the details page of the VM instance is displayed. Click on the Configuration Info tab page. Then, the Configuration Info tab page is displayed.

The Configuration Info tab page displays the configuration information about the VM instance in the form of a list.

Volume

This section displays a list of root volumes and data volumes attached to the VM instance. You can perform operations on these volumes as needed.

NIC

This section displays a list of NICs attached to the VM instance. You can perform operations on these NICs as needed. The following table lists the actions that you can perform on a NIC.
Action Description VM State
Attach NIC Attach a NIC to the VM instance.
  • You can set a default network for the VM instance.
  • You can enable SR-IOV for the VM instance. If enabled, the VM instance will have a VF NIC attached. If not enabled, the VM instance will have a vNIC attached.
  • You can set an IPv4 or an IPv6 address for the NIC.
Note:
  • To enable SR-IOV, note the following:
    • Only IPv4 networks support SR-IOV. IPv6 and IPv4+IPv6 networks do not support SR-IOV.
    • Make sure that SR-IOV is enabled on the L2 network corresponding to the selected L3 network. Otherwise, you cannot enable SR-IOV here.
    • Make sure that the physical NICs on the corresponding L3 network have available VF NICs. Otherwise, you might fail to enable SR-IOV.
    • If the VM instance is using a public network or flat network, the VM NIC does not support security groups and elastic IP addresses after SR-IOV is enabled.
    • If the VM instance is using a VPC network, the VM NIC does not support security groups after SR-IOV is enabled.
  • If the DHCP service is not enabled on the selected network, stop the VM instance and assign an IP address. Otherwise, the IP address might loss after the VM instance reboots.
 Running/Stopped
Detach NIC Detach a NIC from the VM instance.
Note: Detaching a NIC affects the network connectivity of the VM instance and disassociates other associated network services. Please exercise caution.
 Running/Stopped
Set NIC Type Change the NIC type from a VF NIC to a vNIC.
Note:
  • Before you can set the NIC type, stop the VM instance.
  • Only VF NICs can be changed to vNICs.
 Stopped
Set MAC Set a MAC address the VM NIC.
  • Before you set a MAC address, stop the VM instance.
 Stopped
Set the NIC Model Set the NIC model for the VM instance. supported VM NIC models: virtio, rtl8139, and e1000.
Note:
  • After the NIC model is set, reboot the VM instance to take effect.
  • Make sure that you installed a NIC driver that matches the NIC model.
  • Creating VM images and V2V migrations do not inherit configurations associated with the NIC model.
  • Only Linux and Paravirtualization operating systems are supported.
 Running/Stopped
Set NIC QoS Set the upstream bandwidth and downstream bandwidth of the VM NIC.
  • To set the NIC QoS, either the upstream bandwidth or downstream bandwidth is required. Bandwidth range: 8 Kbps – 60 Gbps. Unit: Kbps, Mbps, and Gbps.
  • If not set, both the upstream and downstream bandwidth is not limited.
 Running/Stopped
Set IP Address Set an IP address for the VM NIC.
  • If you choose to assign an IP address, enter an IP address in the selected network range.
  • If you choose random allocation, the system will automatically allocate an IP address from the selected network range.
Note:
  • Before you can set the IP address, stop the VM instance.
  • Make sure that the IP address does not conflict with other IP addresses.
 Stopped
Set Default Network Set a default network for the VM instance if the VM instance has multiple NICs.
Note: Reboot the VM instance to take effect.
 Running/Stopped

vDrive

This section displays a list of virtual drives (vDrives) attached to the VM instance. You can perform operations on these vDrives as needed. The following table lists the actions that you can perform on a vDrive.
Action Description VM State
Create vDrive Create a vDrive for the VM instance.
Note:
  • Before you create vDrive, stop the VM instance first.
  • A VM instance can have up to three vDrives. You can change the maximum of vDrives that can be created for a VM instance globally. Method: In the Global Setting, modify Maximum Virtual Drive. Valid values: 1, 2, and 3.
 Stopped
Set as Default Drive Set a vDrive for the VM instance if the VM instance has multiple vDrives.
Note:
  • Reboot the VM instance to take effect.
  • If you change the default drive, note that:
    • The serial number of the vDrive will be changed, thus affecting the mapping between the device name and ISO.
    • For example, assume that you have three vDrives: CDROM-1, CDROM-2, and CDROM-3. If you make CDROM-2 default, CDROM-2 and the loaded ISO become CDROM-1, and the original CDROM-1 becomes CDROM-2.
 Running/Stopped
Delete vDrive Delete a vDrive.
Note:
  • Before you can delete a vDrive, stop the VM instance.
  • After you delete a vDrive, the serial number of the remaining vDrives will be updated in order.
    • For example, assume that you have three vDrives: CDROM-1, CDROM-2, and CDROM-3. If you delete CDROM-2, CDROM-3 and the loaded ISO becomes CDROM-2.
 Stopped

LUN

This section displays a list of LUNs passed through from SAN storages to the VM instance. You can perform operations on these LUNs as needed. The following table lists the actions that you can perform on a LUN.
Action Description VM State
Attach LUN Pass through a LUN to the VM instance directly as a storage medium.
Note:
  • One VM instance can attach multiple LUNs.
  • One LUN can also be attached to multiple VM instances.
 Running/Stopped
Detach LUN Detach a LUN from the VM instance.
Note: This operation interrupts the data reads/writes and may affect the business continuity. Please exercise caution.
 Running/Stopped

pGPU Device

This section displays a list of physical GPU (pGPU) devices passed through from hosts to the VM instance. You can perform operations on these pGPU devices as needed. The following table lists the actions that you can perform on a pGPU device.
Action Description VM State
Attach pGPU Device Pass through a pGPU device to a VM instance directly.
Note:
  • One VM instance can attach multiple pGPU devices.
  • Currently, you cannot attach pGPU devices and vGPU devices to the same VM instance at the same time.
 Running/Stopped
Detach pGPU Device Detach a pGPU device from the VM instance.
Note: This operation might affect the business continuity. Please exercise caution.
 Running/Stopped

vGPU Device

This section displays a list of vGPU devices passed through from hosts to the VM instance. You can perform operations on these vGPU devices as needed. The following table lists the actions that you can perform on a vGPU device.
Action Description VM State
Attach vGPU Device Pass through a vGPU device to a VM instance directly.
Note:
  • Before you can attach a vGPU device to a VM instance, stop the VM instance first.
  • A VM instance can only attach one vGPU device at a time.
  • Currently, you cannot attach pGPU devices and vGPU devices to the same VM instance at the same time.
 Stopped
Detach vGPU Device Detach a vGPU device from the VM instance.
Note: Before you detach a vGPU device from a VM instance, stop the VM instance first.
 Stopped

USB Device

This section displays a list of USB devices passed through from hosts to the VM instance. You can perform operations on these USB devices as needed. The following table lists the actions that you can perform on a USB device.
Action Description VM State
Attach USB Device Pass through a USB device to a VM instance directly. The following two attach modes are supported:
  • Passthrough: Attach a USB device from the host where the VM instance is located to the VM instance. If you want to migrate the VM instance, detach the USB device first.
  • Forward: Attach a USB device from the host that is in the same as the VM instance to the VM instance. If you want to migrate the VM instance, do not detach the USB device.
Note: To attach a USB device to a VM instance, note the following:
  • You can attach a USB device to only one VM instance.
  • A VM instance can have a maximum of 1 USB 1.x device, 6 USB 2.x devices, and 4 USB 3.x devices attached.
  • For VM instances in the running state or VM instances using LocalStorages and are in the stopped state, you can attach only available USB devices on the hosts where these VM instances are located. In this case, you cannot attach USB devices across hosts.
  • For VM instances using shared storages and are in the stopped state, you can attach multiple USB devices on a host in the same cluster with the VM instance.
 Running/Stopped
Detach USB Device Detach a USB device from the VM instance.
Note: This operation interrupts the data reads/writes on the USB device. Please exercise caution.
 Running/Stopped

Other Device

This section displays a list of other PCI devices, such as Ali-NPU cards, IB cards (PCI mode), and FPGA cards, passed through from hosts to the VM instance. You can perform operations on these PCI devices as needed. The following table lists the actions that you can perform on a PCI device.
Action Description VM State
Attach Other Device Pass through a PCI device to the VM instance.
Note: To attach a PCI device to a VM instance, note the following:
  • You need to edit the allowlist of PCI devices and then add the target device to the allowlist.
  • After you edit the allowlist, reconnect to the host to take effect.
  • For details about how to customize the allowlist for other devices and how to pass through them, consult the official technical support.
 Running/Stopped
Detach Other Device Detach a PCI device from the VM instance.
Note: This operation might affect the business continuity. Please exercise caution.
 Running/Stopped