From owner-freebsd-emulation@FreeBSD.ORG Thu Mar 20 07:53: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 4C2161B0 for ; Thu, 20 Mar 2014 07:53: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 087C3F62 for ; Thu, 20 Mar 2014 07:53:37 +0000 (UTC) Received: by mail-vc0-f176.google.com with SMTP id lc6so496939vcb.21 for ; Thu, 20 Mar 2014 00:53:36 -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=pmtORxKF3yGsSYHWhh5WBqFZrFFGMMr8k6UK0DSvi3c=; b=lOoAWXeuYLO7cPfQR0x/BdOBBSyIYYApbnH32kYoOVZs0W6epAYJsZceVWAxnXS5Vt xjz9fEI6mBoL0Ywv0L/qtmtwWkk48j5leeP5R1QasKDpXZr3VNFwJJ/v/89E163EtF6f uYGH+IJ7xXTt8WWIwQ+oN3frh6iJ/TQPYRMzK2C6NZ6modpon6JxLMELGuzPCASUsDv9 js/TW9cJUJ72R6H4/SprSPwG/dXrJK3GenXVeGhDpiJ2XLmJDUOEvJZK1UySw/w6nTGa /p2drdXljpa5HbuIlNOWaYXlCcZTr2CaeSWyqJGP1vgk5f55OsbleMtghpM2mpdwkdDO Qdng== MIME-Version: 1.0 X-Received: by 10.220.188.10 with SMTP id cy10mr3070784vcb.36.1395302016865; Thu, 20 Mar 2014 00:53:36 -0700 (PDT) Received: by 10.220.239.84 with HTTP; Thu, 20 Mar 2014 00:53:36 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Mar 2014 03:53: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 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 07:53:38 -0000 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 the >> 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_ABORT >> (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 or >> 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 my > 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/vboxnet (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 if that behavior is normal or not. In any event, don't understand the purpose of the VBoxManage command in /usr/local/etc/rc.d/vboxnet since, contrary to the immediately preceding 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 annoying, are harmless. I'm still not certain why the error messages just started showing up in the console log on 3/11. -Tom