On Fri, Sep 26, 2008 at 10:16 AM, Maurice Batey <[EMAIL PROTECTED]> wrote:
> On Wed, 24 Sep 2008 11:46:01 -0700, Grant McWilliams wrote: > > > What I had to do was delete the xml file and > > create a new VM from the interface and add my disk files to it. > > The offical workaround appears to be (quoting from the VBox site): > > "This is due to the two extra tags added in VBox 2.0 which are not > understood by the VBox 1.6.x versions. You need to close the VBox GUI > and manually edit the XML file to remove the > <HardwareVirtExNestedPaging ... > tag and the <GuestProperties> ... > </GuestProperties> block. You will then be able to open the VM in VBox > 1.6.6." > > -- > /\/\aurice > Linux Mandriva 2.6.22.19-desktop-2mdv 2008.0PP 32-bit > KDE 3.5.7 Virtualbox 2.0.2 > Sorry I wasn't following this thread. Anyway if this works that's fine. What I was talking about was deleting this XML file and just creating a new VM from the gui. For hard disks you'd choose your old disk image that you had associated with the old VM. You have to set up your settings for that vm to match the old one but that's not too hard. Editing the XML file would probably be faster. -- Grant McWilliams Some people, when confronted with a problem, think "I know, I'll use Windows." Now they have two problems.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
