Hello,
On Mon, 07 May 2007 14:23:29 +0200
"Dmitry A. Kuminov" <[EMAIL PROTECTED]> wrote:
> Clayton Dukes wrote:
>
> > All I did was move the ISO's that I had previously mounted in the vbox
> > (the XP CD and Office 2007) to a different directory.
> > Now I can't open my Virtualbox?
>
> What does this mean that you "can't open" your "Virtualbox"? Moving
> registered ISO images somewhere (or making them inaccessible in some
> other way, e.g. deleting) will not prevent the VirtualBox application
> from functioning. It will only prevent a particular VM an ISO file is
> attached to from being started because it's hard to read information
> from the ISO file that is not available at the expected location (stored
> in the VM configuration data). The same relates to moving/deleting hard
> disk images outside VirtualBox, btw.
I've had this problem before and it has just happened again (using Ubuntu
Feisty). The problem came about after i deleted an .iso from my hard drive that
i had finished with, but i had forgotten it was still mounted to a VM. So in
VirtualBox i removed the .iso in the CD/DVD section, assuming this would
unmount it from any VMs still using it, but the VM is still marked as
inaccessible with the "Could not find a registered CD/DVD image with UUID ..."
message. Starting the VM with VBoxSDL gives the less helpful error:
Could not open VirtualBox session! Error info:
The object functonality is limited
(component Machine).
I also tried modifyvm with -dvd none on the VM but that gives:
[!] FAILED calling virtualBox->OpenSession(session, uuid) at line 3011!
[!] Primary RC = 0x8000FFFF
[!] Full error info present: true , basic error info present: true
[!] Result Code = 0x8000FFFF
[!] Text = The object functonality is limited
[!] Component = Machine, Interface: IMachine,
{fd443ec1-0009-4f5b-9282-d72760a66916}
[!] Callee = IVirtualBox, {e1d95593-f579-4f47-b489-0b67181014e1}
Another thing i tried was adding the .iso again in VirtualBox, but the UUID
does not match up with the one that VirtualBox is saying is not registered. I
do not know if the UUID is a function of its path but that is the only thing
that differs between it being mounted now and it being mounted earlier (before
deleting it from the hard drive i backed it up and MD5ed it so i know this is
an exact copy of the previously working .iso). Rather forgetfully i cannot
remember in which folder the .iso was previously located so copying it back to
the same folder is not feasible, assuming that would affect the UUID in any
case.
When this same problem happened before i used clonevdi to clone it which worked
fine but unfortunately this is a large VM and i do not quite have enough free
space left to try that on this occasion.
So finally i edited the VM's .xml file and changed the DVD part (removing the
UUID of the mounted .iso) to:
<DVDDrive passthrough="false"/>
And it worked! So this leaves me with lots of questions (sorry!):
Why didn't removing the .iso from within VirtualBox automatically unmount it
from all VMs?
Why couldn't i start the VM even when the .iso was not found (but with it
unmounted of course)?
Why didn't modifyvm work as expected?
Why did the VBoxSDL error not match the VirtualBox error?
Why did the UUID appear different when i mounted the same .iso?
Sorry for all the questions but i hope this at least explains the problem i
faced and possibly a workaround solution for anyone else in the same boat :-)
Cheers,
Matt
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
