From owner-freebsd-emulation@FreeBSD.ORG Thu Dec 12 05:50:26 2013 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC02864B for ; Thu, 12 Dec 2013 05:50:26 +0000 (UTC) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B3811E45 for ; Thu, 12 Dec 2013 05:50:26 +0000 (UTC) Received: from gate.nw-fva.de ([134.76.242.1] helo=pc028.nfv) by mailer.gwdg.de with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from ) id 1VqzA3-0008GI-Gu; Thu, 12 Dec 2013 06:50:11 +0100 Message-ID: <52A94E8F.6030309@gwdg.de> Date: Thu, 12 Dec 2013 06:50:07 +0100 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Kevin Oberman , Warren Block Subject: Re: VirtualBox bridged network and 10.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: freebsd-emulation@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2013 05:50:26 -0000 Am 12.12.2013 06:00 (UTC+1) schrieb Kevin Oberman: > On Wed, Dec 11, 2013 at 12:12 PM, Warren Block 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