I tried to reproduce your problem yesterday by: 1. Installing VirtualBox 4.26 on a system where it was not installed before 2. Upgrading VirtualBox 4.24 to 4.26 on another system running in a production environment. Both systems are FreeBSD 10.1-Release with latest updates (via freebsd-update) 64 bit and without X. VirtualBox runs in headless mode. I succeeded in both cases, both systems are running well and no problems at all. Considering the message by Christoph Moench-Tegeder: https://lists.freebsd.org/pipermail/freebsd-emulation/2015-March/012390.html - I have no OpenSSL from ports built. I hope this might help as VirtualBox is very important for FreeBSD "completeness".
P.S. Sorry, I've messed up with the "reply to list" again... On 27.3.2015 г. 22:50 ч., Rusty Nejdl wrote: > > I have the same here on that as well. VBox is completely dead for me. > > Rusty > > > > > > On 2015-03-27 15:38, Leonard Rucker wrote: > >> I am also having an issue with Virtual Box >> >> FreeBSD FileKeeper 10.1-STABLE FreeBSD 10.1-STABLE #0 r280326: Sat Mar 21 >> 10:35:36 PDT 2015 >> >> virtualbox-ose-4.3.26 >> >> However my error is different if I try to run VBoxManage or VBoxHeadless, >> it will return after about 10 minutes with the following error. >> >> %VBoxManage list vms >> >> VBoxManage: error: Failed to create the VirtualBox object! >> >> VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - >> Class not registered (extended info not available) >> >> VBoxManage: error: Most likely, the VirtualBox COM server is not running or >> failed to start. >> >> I'm not sure if this has a similar cause or not. >> >> >> On Fri, Mar 27, 2015 at 8:18 AM Warren Block <wbl...@wonkity.com >> <mailto:wbl...@wonkity.com>> wrote: >>> On Fri, 27 Mar 2015, Warren Block wrote: >>>> On Fri, 27 Mar 2015, Ivo Karabojkov wrote: >>>>> I usually use VirtualBox with VNC and webservice on headless >>>>> servers. I noticed that after any update if the VMs are not turned >>>>> off but with saved state the new version of VirtualBox is unable >>>>> to start them and the process terminates with an error. To start >>>>> the VMs you should discard their states by running (as vboxusers >>>>> if this is the user who runs VirtualBox services): VBoxManage >>>>> discardstate <vmname> This is always necesarry in my case after >>>>> almost any update of >>> VirtualBox >>>> My VMs were all shut down before the upgrade. At this point, I have >>>> tried multiple versions of the operating system, rebuilding >>>> everything VirtualBox depends on, removing CPUTYPE from >>> make.conf, >>>> and twm rather than xfce. The problem has not changed, though. >>> A diff between the truss output of a failed session of 'VBoxManage >>> list vms' and a working one shows that the problems start here: >>> connect(5,{ AF_UNIX "/tmp/.vbox-wblock-ipc/ipcd" },106) ERR#61 >>> 'Connection refused' When the command works: connect(5,{ AF_UNIX >>> "/tmp/.vbox-wblock-ipc/ipcd" },106) = 0 (0x0) In a new terminal >>> window, 'VBoxManage list vms' fails the first three times, then >>> works. After that, it usually works again in that same terminal. It >>> still can't start a VM. >>> _______________________________________________ >>> freebsd-emulation@freebsd.org <mailto:freebsd-emulation@freebsd.org> >>> mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To >>> unsubscribe, send any mail to "freebsd-emulation- >>> unsubscr...@freebsd.org <mailto:unsubscr...@freebsd.org>" >> _______________________________________________ >> freebsd-emulation@freebsd.org <mailto:freebsd-emulation@freebsd.org> mailing >> list >> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation >> To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org >> <mailto:freebsd-emulation-unsubscr...@freebsd.org>"
signature.asc
Description: OpenPGP digital signature
