On Wed, Mar 19, 2014 at 10:31 PM, Thomas Hoffmann <[email protected]> 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 _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "[email protected]"
