Date: Mon, 30 Mar 2015 23:05:40 +0300 From: Ivo Karabojkov <karabojkov@kit.bg> To: rnejdl@ringofsaturn.com, Leonard Rucker <leonard.rucker@gmail.com> Cc: freebsd-emulation@freebsd.org, owner-freebsd-emulation@freebsd.org Subject: Re: Troubles with VirtualBox 4.3.26 Message-ID: <5519AC94.1030803@kit.bg> In-Reply-To: <assp.0528c65d08.8daebf7cd09cbcc97d20e3384dcd580c@ringofsaturn.com> References: <alpine.BSF.2.20.1503260925520.29894@wonkity.com> <20150326140429.77be3c5f@Papi> <55150605.9030202@kit.bg> <alpine.BSF.2.20.1503270849300.75841@wonkity.com> <alpine.BSF.2.20.1503270910520.79253@wonkity.com> <CANeRTV9je-WLXfX7fMegwyeSUcuuhYTt1LtVxe-scbVapYd_mg@mail.gmail.com> <assp.0528c65d08.8daebf7cd09cbcc97d20e3384dcd580c@ringofsaturn.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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 <wblock@wonkity.com <mailto:wblock@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- >>> unsubscribe@freebsd.org <mailto:unsubscribe@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-unsubscribe@freebsd.org <mailto:freebsd-emulation-unsubscribe@freebsd.org>" [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJVGayVAAoJEO+MRErbUwwKuYMP/iXf0S4kr8dT7iSjqLIt52U+ pXvvKgYvYxyWqpIwIv6O0bII7ltGG6/ioeKaqNDG2ViAZOOk4KotDXtqRgFl/nkc ooBwheDHHm9XgHuxeb2iBbGfCOph83okI1iB5aKHBvZsTwP744DZk8HYkeerRNVh JieFvKmtVOlCv/d1VBcNY1Ycl6hEOgwyualunrg10ldFL5x4NTWoVy5JEaO5VO5Q v8/s84XAUNXLBLk9prZY4GBTmeD6yOi/6HEs8s2W7ixvj8hQ+4WJ+nciM8YGjG6r IaSWrKpAAAfv3hCs25PxCxHZE+VJgQjR5bPEzUH95511kLEZTPrSSBdvwgx1sR7v 4QlEDosOHjtAOPWTEF8oP25uGkCOGxAiE23nhlUjiJa5tLqNXmIYtGKBGEKV9O0/ KCng7dQ6LWO3r7h+1TlLFdrZfB24HCZEKwYSF0uPkoRvjR22phgQOqNd6G2JwZnC Rzz/+rTW70+FoHR2NNDeof+XNaVImMUFOPDb8s/q/IhutUTPVAeUwpetJFCrTWAJ 5kXuGeUdLelLk1BdAsR/wiB24SRKXsPT5PsgYiJeHYgrxqF+abeKpNJS5iMhg9eY rcXiueBXmuWdQpDtKDCr6Ltc2gX6hbr+ZrPKiNKoeZraBAMt5ECabwAiKovcWMdD R8/YaRhJwbqQBCRj5EcN =v/Yw -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5519AC94.1030803>