I THINK, it happened to me once (long time ago :P).
The problem, IIRC, is that the VM has a saved state, and, in that
saved state the cd-rom is mounted. If you want to give the vm the same
state back you need to have EVERYTHING in the exact same way it was
when the VM was stopped. So, if not everything it on place, you can't
restart the VM.
For example, if you are installing a program from a cdrom, and decide
to suspend the VM. No problem, last time you resume the VM is will
keep the installation running without any problem. This is what
"suspend" means.
Now imagine you want to restart the VM, BUT the cdrom isn't there any
more, but the guest isn't aware of it. The guest will simply resume
and try to continue the install, what, of course, will not succeed.
The guys at Innotek probably did this to avoid losing data on some cases.
The solution for this is to discard the saved state, and THEN detach
the DVD. Course you will loose your saved stated in this way, but the
VM will still be fully functional.
Hope this sheds some light on the issue.
Cheers,
KM
On 5/10/07, Clayton Dukes <[EMAIL PROTECTED]> wrote:
> Yeah, wish I knew about the clone option -- I would have certainly tried it
> :-)
>
>
>
> On 5/10/07, Matt Cheddar <[EMAIL PROTECTED] > wrote:
> > On Thu, 10 May 2007 16:58:11 -0400
> > "Clayton Dukes" < [EMAIL PROTECTED]> wrote:
> >
> > > That's exactly what happened to me, except when I tried editing the .xml
> and
> > > setting it to "false/" it didn't fix the problem.
> > > I ended up going back to vmware, sadly :-(
> >
> > Sorry to hear that. Maybe cloning the VM might have helped. The first time
> i had this problem occurred after an upgrade of VirtualBox. The guest
> additions were mounted to a VM and i uninstalled the previous version of
> VirtualBox and installed the new version. I think the guest additions were
> installed to a new folder and i was getting the "Could not find a registered
> CD/DVD image with UUID ..." message. Nothing would let me unmount the (now
> no longer installed) guest additions from the previous version and i could
> not start the VM. I don't remember the exact details on that occassion but
> somehow cloning the VM fixed it (maybe i did some other stuff too!). Anyway,
> as a last ditch attempt i'm sure it is worth a try.
> >
> > Kind regards,
> > Matt
> >
> > >
> > >
> > > On 5/10/07, Matt Cheddar <[EMAIL PROTECTED]> wrote:
> > > >
> > > > 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
> > > >
> > >
> > >
> > >
> >
> > _______________________________________________
> > vbox-users mailing list
> > [email protected]
> > http://vbox.innotek.de/mailman/listinfo/vbox-users
> >
>
>
>
> --
> ______________________________________________________________
> C I S C O S Y S T E M S
> Clayton Dukes
> Network Management Consulting Engineer
> Advanced Services - Central Engineering
> Phone :+1 919.392.6122
> Mobile :+1 813-545-7373
> Fax :+1 919-869-1580
> 7025-3 Kitt Creek Road RTP, NC 27709-4987
> ______________________________________________________________
> _______________________________________________
> vbox-users mailing list
> [email protected]
> http://vbox.innotek.de/mailman/listinfo/vbox-users
>
>
--
As coisas são como elas são porque é assim que as fizemos ser.
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
