virtualbox 4.0 - using earlier VMs?

[NoOp]

On 12/23/2010 06:51 PM, Karl Auer wrote:
> On Thu, 2010-12-23 at 16:30 -0800, NoOp wrote:
>> You'd probably be better served by asking on the VBox mailing list:
>> http://www.virtualbox.org/wiki/Community
> 
> Will do.

You didn't answer the question below:
> 
>> 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.
> 
> Why? The HDD images all have UUIDs in them already, and I've no desire
> to change them.

Answer the base question please.

In the past when I moved vmdk's over to a new machine partition without
first exporting I recall having to adjust the uuid's in the xml. Now I
export the appliance instead, so I've not run across this recently.

> 
>> 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.
> 
> Er - the whole point here is to avoid creating new VMs! I want to use
> the old ones, with the HDDs that are attached to them. The path you
> describe begins with "New" - which is specifically what I am trying to
> avoid. Perhaps I've misunderstood you - what exact steps are you
> suggesting?

Just please try as I've suggested - use new & give the machine a new
name & use the old vmdk. If it doesn't work then you can delete later.

> 
>> 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.
> 
> "Picking up" - what does that mean?

It means that when I installed virtualbox-4.0 it uninstalled my existing
3.12 and automatically picked up my previous VM's and when I opened Vbox
they appeared & run.

> 
> I've read the manual some more, and will try simply pointing VB4 at the
> old directory instead of at its default.
> 
> Regards, K.
> 
>