VM disk configuration modes and their differences

8

There are three VM disk configuration modes:
Common: The system allocates disk space based on disk capacity. During disk creation, any data remaining on the physical device will be reset to 0. This mode results in better disk performance than the others, but disks take longer to create.

Thin provisioning: In this mode, the system initially only allocates part of a disk's configured capacity. The rest is allocated as needed based on its storage usage, until all of the configured capacity has been allocated.

Thick provisioning lazy zeroed: The system allocates disk space based on disk capacity. Unlike common mode, however, any data remaining on the physical device is only zeroed out on the first data write from the VM. This mode creates disks faster than common mode, and its I/O performance falls between that of the common and thin provisioning modes.

Other related questions:
Steps for scanning VM hard disks
You can scan a hard disk as follows: 1. On the taskbar of the VM OS, select Start and enter compmgmt.msc in Search programs and files to go to the Computer Management window. 2. In the navigation tree on the left, expand Storage. 3. Right-click Disk Management and choose Rescan Disks.

Method used to implement VM encryption (including data disk encryption)
To implement VM disk encryption, deploy encryption and decryption agents on a user VM and use the Intel CPU's AES-IN encryption instructions for hardware acceleration. All user and application data is dynamically encrypted when it is written to the virtual disk (volume) and decrypted when it is read from the virtual disk (volume). The data stored in virtual disk files is in ciphertext, and will not be disclosed even if the physical disk or volume and snapshot files are stolen. Prototype test: About 10% performance compromises.

Methods used to unbind disks from faulty VMs and bind them to new VMs
1. In the FusionCompute, choose VDC Management > VM and Template. The VM and Template page is displayed. 2. In the navigation tree, expand Site, right-click the faulty VM, and choose Forcibly Stop from the shortcut menu. Click VM, and choose More > Forcibly Stop in the Operation column from the row where the faulty VM is located. 3. Click OK. 4. Choose VDC Management > Storage Management. 5. In the Site navigation tree, choose the site where the faulty VM is located. 6. Click the Disk tab. A disk list is displayed. 7. Click the name of the faulty VM, and click Disk on the Hardware tab. 8. Click the name of the data storage to which the disk attached to the faulty VM belongs, and click Disk. 9. Locate the row that contains the system disk (for example, disk 1) of the faulty VM, click MoreOperation, and select Unattach. Detach disk 1 from the faulty VM as prompted. 10. Locate the row that contains disk 1, click MoreOperation, and select Attach. The Attach dialog box is displayed. 11. Select user disk as the binding mode, and select the VM (for example, VM B) to which the disk is attached. 12. Click OK. 13. Attach disk 1 to VM B as prompted. 14. Log in to VM B using VNC. 15. Right-click My Computer, and choose Manage from the shortcut menu. The Server Manager window is displayed. 16. Choose Storage > Disk Management. Right-click disk 1, and choose Change Drive Letter and Paths from the shortcut menu. The Change Drive Letter and Paths dialog box is displayed. 17. Click Change, and set a drive letter, for example, E. Click OK. A confirmation dialog box is displayed. 18. Click OK. The Computer Management page is displayed. The data on drive E: is the data on disk 1. 19. Restore system files on drive E, and back up user data.

Necessity of configuring RAID arrays for a RAID controller card
If the LSISAS1078, LSISAS2208, or LSISAS3108 RAID controller card is used, the disks can be recognized by the system only when they are in RAID arrays. If the LSISAS1068, LSISAS2308, or LSISAS3008 RAID controller card is used, the disks can be used as individual disks for OS installation, if they are not in RAID arrays.

Difference between the subcard mode and board mode
The subboard mode refers to the current working mode of a subboard. The board mode refers to the current working mode of a board. Different types of boards and subboards support different types of working modes. Many commands are used to switch the subboard mode and board mode. These commands start with set service-mode. To set the subboard mode, you can run the set service-mode card or set service-mode slot card command in the system view. To set the board mode, you can run the set service-mode slot command in the system view.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top