

OS X’s hdituil can mount the images natively. Third, make sure the virtual host the VDI image is attached to, is NOT running! How To Second, you will most likely only want to use this with statically sized VDI files, and not the dynamically sized ones – especially if you are going to write to the image! If you are not comfortable using the Mac OS X command line, do not attempt! When in doubt, make a backup of the original VDI image first. No additional software is required.įirst, a standard disclaimer! By following this procedure your data is at risk! You accept ALL risk by following this procedure. To do this, I will use the Mac OS X utility hdiutil. With some creativity you could also create a backup of the files inside the VDI image, rather than just the image itself. Why? It’s a convenient way to add and remove files in the VDI image. mpack Site Moderator Posts: 37092 Joined: 4.This will demonstrate how to mount a VirtualBox VDI hard disk image natively in Mac OS X. This does mean that you can't mount the copied VM on your own PC, but I assume you really don't need to. That way all UUIDs are retained and grub will be happy.

I'm not au fait with Linux, but I believe the device name would look something like "/dev/sda".Īnother possibility is not to clone the VM at all, simply copy the VM folder to the student PC. So, one solution is to modify the grub script so that the drive is identified by device name rather than id. However the drive UUID changes when a clone is created, otherwise it would not be possible to mount the clone on the same host - it would conflict. This is quite common in Linux boot scripts. Ok, given that you have a clone of the VM, your problem is most likely that you have a grub boot script that references the boot drive using its UUID. The fact that VDIs are large doesn't make them the only important file.

You do not clone PCs by copying the hard disk, you must clone the entire VM, i.e. I dont know if this problem is related to windows or my VDI file.įirst, can we please emphasise that a VDI is a hard disk. Pachequin wrote:error: invalid arch-independent ELF magic.
