virtualbox 4.0 - using earlier VMs?

[NoOp]

On 12/23/2010 02:34 PM, Karl Auer wrote:
> Hi all.
> 
> I justinstalled maverick, and it hs been remarkably painless. However,
> I'm having difficulties with my old Virtualbox VMs. I can't seem to get
> them into VirtualBox 4.0!
> 
> I have a directory that has all the old VMs in it, and I have a working
> VB 4.0 install. When I go to "Machine -> Add" ("add an existing virtual
> machine") I  browse through to where the old machines are, then into the
> Machines subdirectory and select <machinename>.xml. Whereupon VirtualBox
> 4.0 tells me
> 
>    Failed to open virtual machine located
>    in /home/kauer/.VirtualBox/Machines/WINXP_SP3/WINXP_SP3.xml.
> 
>    Could not find an open hard disk with UUID
>    {7e895d6e-e8b5-4f54-8445-4aab6776e005}.
> 
> Clicking on "Details" shows me this:
> 
>    Result Code:VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
>    Component: VirtualBox
>    Interface:IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}
> 
> Not sure waht "open" means, but I tried to at least register the disk.
> But the 4.0 Virtual Media manager has no way to register a disk!
> 
> Does this mean I will have to re-create all my VMs? That would make me
> sad :-(
> 
> A quick read of the 4.0 doco does not reveal an upgrade path as such,
> but does strongly imply (in the section on old vs new storage locations)
> that 4.0 can use earlier VMs. Question is, how?

You'd probably be better served by asking on the VBox mailing list:
http://www.virtualbox.org/wiki/Community

However, when you say you just installed maverick, did you install on a
new partion and then move your VBox folder over to the new partition? If
so, then you'll likely need to modify the xml and the UUID in the file.

But... you don't add an xml, you add a vmdk. File|New|VM
Name...|Memory|'Use existing hard disk' -
/home/kauer/.VirtualBox/HardDisks/WINXP_SP3/WINXP_SP3.vmdk.

Note: I've just upgraded to 4.0 on both maverick & lucid, and had no
issues in 4.0 picking up my 3.x VM's.