From owner-freebsd-emulation@FreeBSD.ORG Thu Mar 20 12:12:38 2014 Return-Path: Delivered-To: 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 3951EBBC; Thu, 20 Mar 2014 12:12:38 +0000 (UTC) Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D69BDBB6; Thu, 20 Mar 2014 12:12:37 +0000 (UTC) Received: by mail-vc0-f176.google.com with SMTP id lc6so796751vcb.21 for ; Thu, 20 Mar 2014 05:12:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7JqbV5d6DO37DJr6xEFWjUHj/nVLBzU6rnUN5lS50l0=; b=W84lrG172Gk93Ecj3E2vbVV281c70Kk8sMhkCndM00d6GiGMOtJUJ82ohfpLY1ZcKt DJTy6FnEYBYkPOS1zptW4eQZENaUc7jcccnN59miAWxUDyqbel08Cy6BafzD4gGqIrPW UMXVjGHnCGqbjuwOdKqB/ihSuAJ1o1QE/bfywwQ70XUkNkPQzNacDOw2UzVYAapwcWW7 lumpZOIcDKcyHitojCkBq8T2XUt5O6biGjPdJOvijRYHD5itKkvLG239WNR41SYEe4qC 1o7mGRZ1mfCkI4wTKJrr+N1rbFW+IskGQ7n5Tcv7DUW4SCECTzz7Rk9dSU5gGBij374o Nfvw== MIME-Version: 1.0 X-Received: by 10.52.134.136 with SMTP id pk8mr131346vdb.70.1395317557060; Thu, 20 Mar 2014 05:12:37 -0700 (PDT) Received: by 10.220.239.84 with HTTP; Thu, 20 Mar 2014 05:12:36 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Mar 2014 08:12:36 -0400 Message-ID: Subject: Re: VBoxManage errors at boot From: Thomas Hoffmann To: "freebsd-emulation@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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, 20 Mar 2014 12:12:38 -0000 On Thu, Mar 20, 2014 at 8:02 AM, Bernhard Fr=F6hlich wro= te: > On Thu, Mar 20, 2014 at 8:53 AM, Thomas Hoffmann wrote= : > > On Wed, Mar 19, 2014 at 11:25 PM, Thomas Hoffmann > wrote: > > > >> On Wed, Mar 19, 2014 at 10:31 PM, Thomas Hoffmann >wrote: > >> > >>> I'm running emulators/virtualbox-ose-4.3.8 on -CURRENT r263411 amd64. > The > >>> last several boot sequences I have noticed the following errors in th= e > >>> console log: > >>> > >>> Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Failed to create > the > >>> VirtualBox object! > >>> Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Code NS_ERROR_ABO= RT > >>> (0x80004004) - Operation aborted (extended info not available) > >>> Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Most likely, the > >>> VirtualBox COM server is not running or failed to start. > >>> > >>> I'm perplexed by these messages because I do not have any cron jobs > that > >>> invoke VBoxManage @reboot for any purpose whatsoever be it managing o= r > >>> starting a virtual machine. > >>> > >>> I'm thinking these messages appeared after the upgrade to 4.3.8, but = I > >>> cannot be certain. > >>> > >>> Can anyone provide a context for these errors? > >>> > >>> -Tom > >>> > >> > >> I've done a bit of digging and can offer a bit more info. I upgraded > >> virtualbox-ose to 4.3.8 on 3/3 and did not see the errors until 3/11, = so > >> the upgrade itself did not introduce the errors. The 3/3 upgrade was m= y > >> last upgrade of virtualbox-ose and I did not re-install it after that. > >> > >> However, on 3/11 I built a new -CURRENT (r263062). Something in that > build > >> seems to have introduced the errors. My previous -CURRENT (r262295) > built > >> on 3/8 did not have the errors. > >> > >> I'm still looking into this. > >> > >> -Tom > >> > > > > Okay, so I found the source of this error. In /usr/local/etc/rc.d/vboxn= et > > (I have vboxnet_enable in /etc/rc.conf) it attempts to execute the > > following command for vboxnet_start: > > # initialize configured host-only interfaces > > /usr/local/bin/VBoxManage list hostonlyifs >/dev/null > > > > I can run VBoxManage as a normal user without any problems, but when I > run > > VBoxManage as root it results in the same three errors from my original > > post. That is why it errors out during the boot process. I don't know i= f > > that behavior is normal or not. > > > > In any event, don't understand the purpose of the VBoxManage command i= n > > /usr/local/etc/rc.d/vboxnet since, contrary to the immediately precedin= g > > comment, it is only listing (not initializing) hostonly interfaces and > > sending the output to dev/null. It seems pointless. > > > > Anyway my conclusion is that the boot time error messages while annoyin= g, > > are harmless. I'm still not certain why the error messages just started > > showing up in the console log on 3/11. > > It does exactly what the comment says. host-only interfaces need to be > initialized (pretty early for some configurations) and the hostonlyifs > listing > is the least intrusive one which ensures that they are. > > It might be that the error output of vboxmanage has been switched to stde= rr > now and we need to add an 2>/dev/null too. Have you recompiled all vbox > kernel modules after your update to a new current? Sigh. No I did not. I should have thought of that as a probable cause. Thanks. -Tom