Date: Thu, 12 Dec 2013 06:50:07 +0100 From: Rainer Hurling <rhurlin@gwdg.de> To: Kevin Oberman <rkoberman@gmail.com>, Warren Block <wblock@wonkity.com> Cc: freebsd-emulation@freebsd.org Subject: Re: VirtualBox bridged network and 10.0 Message-ID: <52A94E8F.6030309@gwdg.de> In-Reply-To: <CAN6yY1trRE6D4D_EqMgLuXkSO_mZnqi_Zx0cn%2B1Or-mUmgZg_g@mail.gmail.com> References: <alpine.BSF.2.00.1312111306460.4003@wonkity.com> <CAN6yY1trRE6D4D_EqMgLuXkSO_mZnqi_Zx0cn%2B1Or-mUmgZg_g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 12.12.2013 06:00 (UTC+1) schrieb Kevin Oberman: > On Wed, Dec 11, 2013 at 12:12 PM, Warren Block <wblock@wonkity.com> wrote: > >> VirtualBox 4.2.20 does not like the vboxnet service: >> >> # service vboxnet start >> VBoxManage: error: Failed to create the VirtualBox object! >> VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted >> (extended info not available) >> VBoxManage: error: Most likely, the VirtualBox COM server is not running >> or failed to start. >> >> NAT networking that does not need the vboxnet service seems to work. Does >> something need to be done differently on 10.0? This is amd64, >> 10.0-PRERELEASE. >> > > To ask the obvious, did you reboot or unload the old kernel modules and > load the new ones? I can say it is working fine for me with 9-Stable > (r256657) on amd64, but I ave not tried 10 yet as there have been a LOT of > discussions of VB breakage on 10. > I built and installed VirtualBox 4.2.20 successfully on recent HEAD (11.0-CURRENT r259216). After rebooting, I get the same messages like wblock@. NAT service works so far. Regards, Rainer Hurling
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52A94E8F.6030309>