I there, I updated my VB from 4.1.18 to 4.1.22, and the virtual machine disapeared. Then I selected "Machine" -> "add" -> and slected the "xml file", and I got this:



Failed to open virtual machine located in C:/Users/Javito/.VirtualBox/Machines/Debian/Debian.xml.

Could not find an open hard disk with UUID {1b978737-2dfd-4e12-ba28-cd0c49657cc8}.

Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Component: VirtualBox
Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}


I have updated several times my VB and I never have had this problem before. Now I don't know what to do. Any help would be really appreciated.
Thanks in advance.
Joc

I haven't experienced an issue like this when updating the vbox version. It should be recoverable.

Check the File > Virtual Media Manager. Is the hard drive for that vm listed (all the drives, if you have more than one attached)?

Out of interest do you have a lot of vms and hard drives?

Wonder if some permission is causing this?

I checked the File > Virtual Media Manager and there's nothing there, however in the folder .VirtualBox, there are two folders: one is named HardDisks and the other is Machines.

Any ideas?

I downgrade the VirtualBox to 4.1.18 and then 4.1.14 but the virtual machine doesn't appear there anymore.

Any ideas?

I don't think I have time to look at this today, but can you look at the properties of the virtual machine (in the gui) and see what hard drive it has, and where on the disk you think it should be - then add that into the virtual media manager?

It may be something else but this should be a start

Was the kernel module compiled and restarted for your actual kernel?

I haven't compiled the kernel in this VB.

Sorry, I thought the VirtualBox application on its own wouldn’t start up (VirtualBox uses a kernel module on its own and usually it’s recompiled when you install the RPM). But I realized now, that only the VM definition is missing.

With some versions Oracle split the settings file and VirtualBox images into “~/.VirtualBox” and “~/VirtualBox VMs”.

Do you still have the image in “~/.VirtualBox/HardDisks”? You could also create a new VM, copy (for safety reasons) the image you had before to “~/VirtualBox VMs/<created during definition of the VM>/” and attach it to the new VM.

OK!, I'm not sure if I understand, I have debian. Does it mean that I have to create a new Virtual machine, install a new version of debian and once that is working properly, attach the old /hard disk?, is that how it works? or what would be the steps?... I'm sorry, it sounds like a silly question, but I have no idea how to proceed.

Thanks in advance.

No, there is no need to reinstall the OS in the VM – at least if the disk image used in the VM isn’t broken.

Normally it should work without recreating a new VM and attaching the old disk image. But maybe something got screwed up, so it’s worth to test it. And as I suggested to use a copy of the image, nothing bad should happen.

I have a prepared image of a VM and each time I want to have it on a new (physical) machine I define a new VM there, transfer the image thereto, and select “Use existing hard disk” while defining the new VM (3rd step after defining the granted memory).

1 members found this post helpful.

Thank you!, that worked!