Page 1 of 1

Could not find and open hard disk with UUID

Posted: 4. Mar 2015, 00:00
by jeebc
Copying an image from another machine, into a VirtualBox that - currently - has no images at all, getting:

Failed to open virtual machine located in ...\..vbox
Could not find and open hard disk with UUID



Host : Windows 7, 64bit
VBox 4.3.23
Client is a Linux 64 bit

From what I read on "the internet" I should mess with the VBOX file itself (which is an XML file really), but I don't fancy that. Is there a proper solution for this ?
That same image was already imported into VBox before. But, by means of deleting it, all references should be gone.
Hence, importing a new one should not make reference to something that should not be there, like a disk reference of some kind.

Re: Could not find and open hard disk with UUID

Posted: 4. Mar 2015, 11:48
by mpack

Re: Could not find and open hard disk with UUID

Posted: 5. Mar 2015, 17:47
by jeebc
mpack wrote:Howto: Move a VM.
The exact action as described there, is what caused the issue of this thread.

Re: Could not find and open hard disk with UUID

Posted: 5. Mar 2015, 19:35
by mpack
The procedure described in the link does not tell you to copy images into another VM.

Also, the procedure described in the link is known to always work, which is why it is there as a FAQ.

Re: Could not find and open hard disk with UUID

Posted: 5. Mar 2015, 21:02
by jeebc
mpack wrote:The procedure described in the link does not tell you to copy images into another VM.
"copy the VM folder (with contents) to your preferred location."

Re: Could not find and open hard disk with UUID

Posted: 5. Mar 2015, 21:04
by jeebc
mpack wrote:Also, the procedure described in the link is known to always work, which is why it is there as a FAQ.
Well, the fact it didn't for me, makes that statement false.

Re: Could not find and open hard disk with UUID

Posted: 5. Mar 2015, 21:12
by jeebc
Oh, I know what the issue was .. No, it wasn't restarting Windows.

Re: Could not find and open hard disk with UUID

Posted: 6. Mar 2015, 12:16
by mpack
Nobody except you mentioned restarting Windows.

So, explain where the FAQ was wrong?