VirtualBox Ejecting External on Which vdi Resides

[loukingjr]

Okay...so I noticed on my clone directory that there are several other files than my vdi - some vbox and others. None of these were present on my previous external directory. Are those necessary, and can I simply copy the files from my clone and rename them the original machine name to get it to work?

FWIW, it seems based on a few different things you've described you have a completely fouled up VirtualBox directory setup. It seems you have created this situation by moving, guests, .vdi files etc., incorrectly. A guest should have its own folder with a Logs Folder, a Snapshot folder, (if you ever used a Snapshot), the *.vdi file, the *.vbox file, and the *.vbox-prev file. None should be outside of a guest folder.

The other problem is of course as socratis mentioned, is trying to run a guest on a OSX host from a Windows partition. Unless you have as he also mentioned, OSXFUSE, NTFS-3G,(commercial or Freeware version), or or Paragon NTFS installed on your Mac, the guest can't save any changes or shutdown correctly. They also have to be the most recent versions for OSX 10.11 compatibility.

It is difficult to tell exactly what you are doing/have done and therefore extremely difficult to help straighten it out.

[jt643]

So I got it to work...

Here is what I did:

1. Cloned my vdi on WINDOWS to my desktop (Windows vm\windows 10\). It created a new folder (username\vm machines\) where my logs, .vbox, and .vbox-prev files resided. All were assigned "clone" on the file names. I was able to boot up my machine (the clone) with that configuration. So...
2. Copied the vdi and all the files from the vm machines directory to the external folder and took the "clone" off. Deleted all the other files, created a new machine using an existing image and voila!

I need to change my volume names to not be in conflict. I think that may have been some of the cause. I do remember when the initial errors happened there was a message about WINDOWS 1 vs WINDOWS.