information into the disk’s metadata sections. Note that write access is required for all typical hard disk usage in VirtualBox, since VirtualBox may need to write metadata such as a UUID into the image WindowsBasicData Windows Basic data partition WindowsLDMMeta Windows Logical Disk Manager (LDM) metadata partition. WindowsLDMData Windows Logical Disk Manager data partition. WindowsRecovery Windows Android x86 recovery partition. AndroidX86Misc Android x86 misc partition. AndroidX86Metadata Android x86 metadata partition. AndroidX86System Android x86 system partition. AndroidX86Cache Android x86

information into the disk’s metadata sections. Note that write access is required for all typical hard disk usage in VirtualBox, since VirtualBox may need to write metadata such as a UUID into the image WindowsBasicData Windows Basic data partition WindowsLDMMeta Windows Logical Disk Manager (LDM) metadata partition. WindowsLDMData Windows Logical Disk Manager data partition. WindowsRecovery Windows Android x86 recovery partition. AndroidX86Misc Android x86 misc partition. AndroidX86Metadata Android x86 metadata partition. AndroidX86System Android x86 system partition. AndroidX86Cache Android x86

information into the disk’s metadata sections. Note that write access is required for all typical hard disk usage in VirtualBox, since VirtualBox may need to write metadata such as a UUID into the image WindowsBasicData Windows Basic data partition WindowsLDMMeta Windows Logical Disk Manager (LDM) metadata partition. WindowsLDMData Windows Logical Disk Manager data partition. WindowsRecovery Windows Android x86 recovery partition. AndroidX86Misc Android x86 misc partition. AndroidX86Metadata Android x86 metadata partition. AndroidX86System Android x86 system partition. AndroidX86Cache Android x86

information into the disk’s metadata sections. Note that write access is required for all typical hard disk usage in VirtualBox, since VirtualBox may need to write metadata such as a UUID into the image WindowsBasicData Windows Basic data partition WindowsLDMMeta Windows Logical Disk Manager (LDM) metadata partition. WindowsLDMData Windows Logical Disk Manager data partition. WindowsRecovery Windows Android x86 recovery partition. AndroidX86Misc Android x86 misc partition. AndroidX86Metadata Android x86 metadata partition. AndroidX86System Android x86 system partition. AndroidX86Cache Android x86

information into the disk’s metadata sections. Note that write access is required for all typical hard disk usage in VirtualBox, since VirtualBox may need to write metadata such as a UUID into the image WindowsBasicData Windows Basic data partition WindowsLDMMeta Windows Logical Disk Manager (LDM) metadata partition. WindowsLDMData Windows Logical Disk Manager data partition. WindowsRecovery Windows Android x86 recovery partition. AndroidX86Misc Android x86 misc partition. AndroidX86Metadata Android x86 metadata partition. AndroidX86System Android x86 system partition. AndroidX86Cache Android x86

archive which contains a boot volume of the instance in QCOW2 format and a JSON file containing metadata related to the instance. • The boot volume of the instance is extracted from the archive and a a TAR archive which contains a bootable instance image in QCOW2 format and a JSON file with some metadata related to the imported instance. The downloaded file is deleted after a successful import. If import currently not possible to check for metadata integrity of the disk image. Attackers might destroy data by removing or changing blocks of data in the image or change metadata items such as the disk size. •

archive which contains a boot volume of the instance in QCOW2 format and a JSON file containing metadata related to the instance. • The boot volume of the instance is extracted from the archive and a a TAR archive which contains a bootable instance image in QCOW2 format and a JSON file with some metadata related to the imported instance. The downloaded file is deleted after a successful import. If import currently not possible to check for metadata integrity of the disk image. Attackers might destroy data by removing or changing blocks of data in the image or change metadata items such as the disk size. •

archive which contains a boot volume of the instance in QCOW2 format and a JSON file containing metadata related to the instance. • The boot volume of the instance is extracted from the archive and a a TAR archive which contains a bootable instance image in QCOW2 format and a JSON file with some metadata related to the imported instance. The downloaded file is deleted after a successful import. If import currently not possible to check for metadata integrity of the disk image. Attackers might destroy data by removing or changing blocks of data in the image or change metadata items such as the disk size. •

archive which contains a boot volume of the instance in QCOW2 format and a JSON file containing metadata related to the instance. • The boot volume of the instance is extracted from the archive and a a TAR archive which contains a bootable instance image in QCOW2 format and a JSON file with some metadata related to the imported instance. The downloaded file is deleted after a successful import. If import currently not possible to check for metadata integrity of the disk image. Attackers might destroy data by removing or changing blocks of data in the image or change metadata items such as the disk size. •

archive which contains a boot volume of the instance in QCOW2 format and a JSON file containing metadata related to the instance. • The boot volume of the instance is extracted from the archive and a a TAR archive which contains a bootable instance image in QCOW2 format and a JSON file with some metadata related to the imported instance. The downloaded file is deleted after a successful import. If import currently not possible to check for metadata integrity of the disk image. Attackers might destroy data by removing or changing blocks of data in the image or change metadata items such as the disk size. •