Am 12.12.2013 06:00 (UTC+1) schrieb Kevin Oberman: > On Wed, Dec 11, 2013 at 12:12 PM, Warren Block <[email protected]> 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 _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "[email protected]"
