Verr_vd_dmg_invalid_header

Posted on by



Oracle VM VirtualBox is a program that allows you to create operating systems on virtual machines, i.e. To use Windows programs on Linux. If a program doesn't work under WINE, for example, it will probably work in its native environment, Windows.

Some DMG cannot be mounted in a VM with a ' VERRVDDMGINVALIDHEADER ' error. Example XQuartz-2.7.11.dmg, but there are actually the majority. I had tried to install an OS named Veos with virtual box,but when I had finished the installation,I can not open the wirtual machine Veos,and I had this output: Failed to open image 'C:UsersTakfarinasVirtualBox VMsAristaFilesvEOS-lab-4.16.6M.vmdk' for writing due to wrong permissions (VERRVDIMAGEREADONLY). Download file:-PowerISO: Mac OS X downloads: http://osx.vn/threads/tong-hop-link-download-mac-os-x-10-4-10-11-3-orginal-tu-mac-a. I am running 5.0.10Ubuntur104061 on Ubuntu 15.10 x64. My guest OS is Windows 7 x64 with all patches. Maybe it's relevant: I just added discard='True' to my harddisk. After this, I had running the.

Verr_vd_dmg_invalid_header opening image file

Error:

Cannot register the hard disk ‘*.vdi’ {UUID_UUID_SAME} because a hard disk ‘*.vdi’ with UUID {UUID_SAME} already exists.

Cause:

OIM VirtualBox Hard Disk (.vdi file) with UUID {92957aa4-0f2b-4b4b-be1e-23db8e47393c} already exists, and trying to add another OPAM or OAM VirtualBox Hard Disk (.vdi file) with the same UUID {92957aa4-0f2b-4b4b-be1e-23db8e47393c}.

It is due to the fact that OIM VDI file was cloned or copied to be used as OPAM or OAM VDI.

Verr_vd_dmg_invalid_header

Solution:

Verr_vd_dmg_invalid_header

Verr_vd_dmg_invalid_header

  1. Open ‘Command Prompt’ run as ‘Administrator’
  2. cd C:Program FilesOracleVirtualBox
  3. run the command: VBoxManage.exe internalcommands sethduuid “<Location of Existing Hard Disk>.vdi
  4. Copy the newly changed UUID – 635c3815-d489-47fb-90ab-9b0400a323be
  5. Open the .vbox file located at C:UsersrajesVirtualBox VMsOIMVBImage11.1.2.3
  6. Replace old UUID with new UUID (from step 4) – <HardDisk uuid=”{635c3815-d489-47fb-90ab-9b0400a323be}”
  7. Close the VirtualBox and open again, so that it can refer the new VDI UUID.
  8. Add new VDI file, there will not be any error, as the conflict got resolved once you changed the UUID to new one.