Date: Wed, 9 Sep 2009 14:03:52 -0500 (CDT) From: "Sean C. Farley" <scf@FreeBSD.org> To: Alexander Best <alexbestms@math.uni-muenster.de> Cc: freebsd-emulation@FreeBSD.org Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 6 Message-ID: <alpine.BSF.2.00.0909091400070.20300@thor.farley.org> In-Reply-To: <permail-2009090918261580e26a0b000017c7-a_best01@message-id.uni-muenster.de> References: <permail-2009090918261580e26a0b000017c7-a_best01@message-id.uni-muenster.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 9 Sep 2009, Alexander Best wrote:
> just updated to virtualbox-3.0.51.r22683. all my virtual machines are
> now marked as "inaccessable". all machines have the same problem.
> here's an example:
>
> Error reading /home/arundel/.VirtualBox/Machines/slackware/slackware.xml (line
> 23) -- Invalid value '0' in Boot/Order/@position: must be greater than 0 and
> less than 5.
> /usr/local/src/virtualbox/work/virtualbox-3.0.51r22683/src/VBox/Main/MachineImpl.cpp[4810]
> (nsresult Machine::loadSettings(bool)).
> Result Code:
> NS_ERROR_FAILURE (0x80004005)
> Component:
> VirtualBox
> Interface:
> IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8}
>
> i'm running 9.0-CURRENT (r196879).
I had that with a few machines, but I thought I had done something wrong
since I had been hand editing them. The fix is easy: edit the
machine's XML file and renumber the elements under the Boot element to
have positions greater than zero. Also, for each snapshot in the XML
file, there will be a separate Boot element to fix.
Sean
--
scf@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0909091400070.20300>