When you snapshot a VM it stops writing to the base vmdk and starts writing changes to the snapshot delta file. You can tell which flat.vmdk file it is associated with by opening the file and looking at the Extent Description field.ĭelta.vmdk file - This is the differential file created when you take a snapshot of a VM (also known as REDO log). One of these files will exist for each virtual hard drive that is assigned to your virtual machine. This file is in text format and contains the name of the flat.vmdk file for which it is associated with and also the hard drive adapter type, drive sectors, heads and cylinders, etc. Instead it is the disk descriptor file which describes the size and geometry of the virtual disk file. vmdk file - This isn't the file containing the raw data anymore.
This file will be roughly the same size as your virtual hard drive. vmdk file's content is the virtual machine's data, with a small portion allotted to virtual machine overhead. There are typically 3 different types of files that use the vmdk extension, they are:įlat.vmdk file - This is the actual raw disk file that is created for each virtual hard drive. These are the disk files that are created for each virtual hard drive in your VM.
This file is usually less then 10K in size and is not in a text format (binary). Any changes made to the BIOS via the Setup program (F2 at boot) will be saved in this file. If the NVRAM file is deleted or missing it will automatically be re-created when the VM is powered on. The BIOS is based off the PhoenixBIOS 4.0 Release 6 and is one of the most successful and widely used BIOS and is compliant with all the major standards, including USB, PCI, ACPI, 1394, WfM and PC2001. This file contains the CMOS/BIOS for the VM. Here's a detailed list of all the files that make up a Virtual Machine :
0 kommentar(er)
