1. What are the different types of VHD files?
VHD files are divided into three types, which can be created using the Hyper-V Manager or using Windows Disk Management Tools in Windows 7. :
1. Fixed VHD. The virtual disk size to which a fixed VHD file is allocated is the virtual disk size specified when the VHD was created. For example, if you create a virtual hard disk that is 2 GB in size, the system creates a file that is approximately 2 GB in size, some of which is used for the internal VHD structure. The size of a fixed VHD does not change as data is written to the virtual hard disk.
2. Scalable or dynamic VHD. At any given time, the size of an extensible or dynamic VHD file is the same as the actual data size written to the file. As more data is written, the file is dynamically increased. For example, a file that supports a 2 GB virtual hard disk is initially about 2 MB in the host file system. As data is continuously written to this virtual hard disk, the file grows until it reaches the 2 GB capacity limit.
3. Difference VHD. The difference VHD is similar to a dynamic VHD, but only contains modified virtual disk blocks for the associated parent virtual disk. Differences VHDs are linked to a specific parent VHD, called a child VHD. The parent VHD file is read-only; all modifications are made to the child VHD. The VHD file type of the parent VHD can be any of these three VHD types, including another differential VHD. Multiple sub-VHD files can form a differential chain.
Second, why is it recommended to use fixed VHD files for production?
The reason for recommending fixed VHD files for production is as follows:
" Since there is no need to dynamically expand VHD files, I/O performance is The highest of the three VHD disk types. At the same time, if a write to a fixed VHD file does not cause the underlying host volume of the VHD file to run out of available disk space because the dynamic VHD requires expansion.
" Dynamic and Differential VHD files depend on multiple data write operations and internal block allocation information if all I/O operations on VHD files on the host and physical disks are not completed and are not saved on the physical disk This information may become inconsistent. This can happen when the underlying disk is completely powered down or the system suddenly loses power.
3. When is it suitable for using dynamic or extended VHD files?
Dynamic VHD is useful when using Windows images in the following non-production environments: low storage requirements and reliability compared to data access in VHDs The convenience of replacing VHD files is even more advantageous. For example, a test environment can store many dynamic VHDs on a network share to save space, without the need to allocate a fixed VHD format to the storage space required for unused portions of the image. Typically, the test environment can be easily rebuilt or the VHD image used for testing can be regenerated. Copying smaller dynamic VHD files from a network share to a local disk is faster than transferring a fixed VHD file of the same maximum size. If you can regenerate the entire contents of a dynamic VHD from other sources and the critical data is stored in a volume other than the dynamic VHD, consider using a dynamic VHD in a production environment.
Fourth, when the child difference VHD's parent VHD changes what happens?
Child difference VHD contains the modified data block in a specific parent VHD. If the parent VHD is changed or replaced with another VHD file with the same file name, the block structure between the parent VHD and the child VHD will no longer match and the contents of the child VHD will also be destroyed.
5. Can the parent of the difference VHD be located on a different volume or remote share than the child?
For native VHD boot, the link between the child difference VHD and the parent VHD file requires that the two files be in the same In a volume. Even if the parent and child disks reside on the same local disk, they cannot reside on different volumes. When a VHD other than the native VHD boot (such as an image management operation) is attached, the parent of the differencing disk can be in another volume or even a remote share.
Six, "Create VHD" and "Additional VHD" What are the features?
Disk management tools (DiskPart command line tools and disk management consoles) support creation, attaching, and detaching operations. "Create VHD" Ability to create a new .vhd file of the type and size specified by the option. The newly created .vhd file can be thought of as similar to the original disk. The "additional VHD" operation requires the storage system to use the VHD as a disk attached to the system. After performing the "Additional VHD" operation, you can use the Disk Management tool to create one or more disk partitions within the VHD and format the NTFS file system within the VHD. If the VHD already has a disk partition and a file system volume during the "additional VHD" operation, the system will assign a drive letter to the volume within the VHD and the volume will be available, which is in your connection to the USB connector. The same happens when you plug in a USB disk drive. "Additional VHD" is sometimes called "display VHD", because the file system in the VHD is assigned a drive letter and is displayed and available for use. (Perhaps you can compare the display VHD to a submarine that can be seen and seen.)
Execute "Add VHD", the system will assign a drive letter to all volumes in the VHD and make it in the global namespace Visible in the middle. Whether you can see the attached VHD volume is not limited to the current user context. All users can see the attached VHD just like viewing a physical disk. VHDs can only be attached by users who have volume management privileges (by default only to administrators) because attaching a disk is equivalent to bringing a disk or volume online.
[1] [2] Next Page<7>Which file systems can VHD use?
If you already have a .vhd file, you can save the .vhd file in any FAT, ExFAT, NTFS Or in a UDFS volume. However, you can only attach a VHD that is located on an NTFS volume. Performing an additional operation on a VHD on a non-NTFS volume will fail.
When creating a VHD, you can create one or more partitions in the VHD and format them with FAT, ExFAT, or NTFS. Additional operations make one or more volumes in the VHD available.
8. Can Windows 7 attach a VHD located in a remote share? Yes, you can attach a VHD file located on a remote SMB share, and the VHD file will appear as a local disk. Other remote file systems such as NFS or FTP are not supported. Drives are assigned to volumes contained in the VHD, and these volumes are accessible to all users on the local system, depending on the security permissions of the data in the VHD volume. Remote VHD add-on support for remote image management.
Nine, can I use NTFS compression or encryption for VHD files?
VHD files compressed with NTFS on the host volume will not be attached as virtual hard disks. VHD files encrypted with Encrypting File System (EFS) on the host volume are also not attached as virtual hard disks. VHD files compressed or encrypted on the host volume will not be available for VHD native boot. However, if additional support is provided, the volumes within the VHD can use compression and encryption.
10. Can I use BitLocker to encrypt the entire VHD?
VHD files can be saved on a BitLocker-protected host volume, but VHD files located on BitLocker protected volumes cannot be used for local boot. Enabling BitLocker for volumes contained within a VHD is not a supported configuration.
11. What are nested VHDs and what are nesting restrictions?
VHD is a file on the host volume. For example, the VHD file c:vhdExampleFixed.vhd represents a fixed VHD file located in the vhd directory on the c: volume. In ExampleFixed.vhd, you can create a partition, initialize the NTFS file system volume, and then temporarily assign the drive letter m:. You can also create a new VHD file under m:vhdAnestedFixed.vhd. The second vhd file is created on the file system volume in the first vhd file. This is the nested VHD. Executing the "additional VHD" operation on c:vhdExampleFixed.vhd will make the m: volume available. Executing the "additional VHD" operation on m:vhdAnestedFixed.vhd will make another volume (such as "n:") available. You can only attach up to 2 levels of nested VHDs. This means that you can attach a VHD to another additional VHD. However, if you attach a VHD to another add-on VHD that is already another add-on VHD, it will fail.
12.Can I configure two additional VHDs as dynamic disks?
A dynamic disk is a disk that is initialized for dynamic storage and contains dynamic volumes such as simple volumes, spanned volumes, striped volumes, Mirrored or RAID-5 volume. Additional VHDs cannot be configured as dynamic disks.