Couldn't run virtual machine please help to save info

[mpack]

Despite their proclamation, it will not mount .vdi files for me. Not on OSX 10.11.2 at any rate.

For the longest time I saw a slew of similar claims, but somewhere in the small print it always said that it supports fixed disks only: i.e. it doesn't really understand VDI, it just supports a configurable header size to jump over to get to a flat image. I wouldn't be surprised if that's the case with this tool.

At least your tool checks the header first, which the old Linux tools I'm thinking of didn't do!

[loukingjr]

I sent a support request. It does mount .vmdk files.

[socratis]

Hmm... I was able to install VMDK_MOUNTER_2014 from the Paragon website on a 10.9 and a 10.11 VMs (up to date both). I was able to mount VDI files, as long as the OSX could understand the filesystem. Read-write access. For filesystems that OSX couldn't understand, I was given the option to initialize the filesystem, which it did. Bizarre...

[loukingjr]

yep. I could "initialize" a .vdi as well. Makes sense I suppose it only works with FS's OSX understands. I have Paragon's exFS and NTFS apps installed. Unfortunately they do not work the same way as they used to since OSX 10.11.

[loukingjr]

Geez. I have to take everything (almost) back. VMDK Mounter will mount a .vdi as long as the guest .vdi as socratis mentioned is from hfs+/OSX guests, or ntfs/Windows guests. It will not mount ext*'s/Linux guests' .vdi's.

[mpack]

That's the same as the VDI mounters I have for Windows hosts - except of course substitute "filesystems supported by Windows", i.e. not HFS.

[loukingjr]

Well before OSX 10.11, if you had Paragon's extFS installed, Macs could read and write to extFS volumes. Unfortunately because of changes made to OSX, that is no longer the case. You can still work with ext* volumes, just not in a way that VMDK Mounter can mount ext* .vdi's.

Such is life.