Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Mar 2015 20:14:44 -0500
From:      Rusty Nejdl <rnejdl@ringofsaturn.com>
To:        Warren Block <wblock@wonkity.com>
Cc:        freebsd-emulation@freebsd.org, owner-freebsd-emulation@freebsd.org
Subject:   Re: Troubles with VirtualBox 4.3.26
Message-ID:  <assp.05287a8b90.6cd3f48463fb1afe29fc8a6d0e1e4f53@ringofsaturn.com>
In-Reply-To: <alpine.BSF.2.20.1503261521040.20706@wonkity.com>
References:  <alpine.BSF.2.20.1503260925520.29894@wonkity.com> <20150326140429.77be3c5f@Papi> <alpine.BSF.2.20.1503261521040.20706@wonkity.com>

next in thread | previous in thread | raw e-mail | index | archive | help
 

On 2015-03-26 16:24, Warren Block wrote: 

> On Thu, 26 Mar 2015, Mario Lobo wrote:
> On Thu, 26 Mar 2015 10:29:51 -0600 (MDT) Warren Block <wblock@wonkity.com> wrote: Anyone else having trouble with 4.3.26? Seems like I used VirtualBox very recently, but now it does not want to run at all. The GUI sometimes does not start, and VBoxManage is similar. 'VBoxManage list vms' works maybe one in four times, otherwise just hanging: % VBoxManage list vms load: 0.04 cmd: VBoxManage 16522 [select] 7.77r 0.01u 0.00s 0% 15460k load: 0.21 cmd: VBoxManage 16522 [select] 66.05r 0.01u 0.00s 0% 15460k Occasionally, it claims to have started a VM, but the VM does not actually start. The GUI cannot start a VM: Failed to open a session for the virtual machine winxp. The virtual machine 'winxp' has terminated unexpectedly during startup with exit code 1 (0x1). Result Code: NS_ERROR_FAILURE (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048} VirtualBox has been built without the VNC and WEBSERVICE options. Both the main port and -kmod were!
  rebuilt
after updating to -STABLE today: FreeBSD lightning 10.1-STABLE FreeBSD 10.1-STABLE #0 r280696: Thu Mar 26 09:45:29 MDT 2015 root@lightning:/usr/obj/usr/src/sys/LIGHTNING amd64 My hunch is this is something with the latest -STABLE, and the next tests will be to revert to a few days ago. _______________________________________________ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation [1] To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org" I have FreeBSD Papi 10.1-STABLE FreeBSD 10.1-STABLE #0 r278323M: Fri Feb 6 19:34:48 BRT 2015 and pkg info | grep virtual virtualbox-ose-4.3.26 General-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.3.26 VirtualBox kernel module for FreeBSD and no problem whatsoever.

Still have the same problems with r278323 and other revisions between
there and the latest. No idea yet what's causing this.
_______________________________________________
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation [1]
To unsubscribe, send any mail to
"freebsd-emulation-unsubscribe@freebsd.org"

For the record, I have the same issue with a similar system. I cannot
run VM's and VBoxManage list vms just sits there. I am wondering if this
occurred around the time of the openssl patching and I might need to
recompile all my ports. Something isn't right though and I have seen
other reports of similar issues (two others prior) like this one.

Rusty Nejdl

P.S. Hey Mario - Glad to see you still around.

 

Links:
------
[1] http://lists.freebsd.org/mailman/listinfo/freebsd-emulation



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?assp.05287a8b90.6cd3f48463fb1afe29fc8a6d0e1e4f53>