Troubles with VirtualBox 4.3.26

[Mario Lobo]

On Thu, 26 Mar 2015 15:24:29 -0600 (MDT)
Warren Block <wblock at wonkity.com> wrote:

> On Thu, 26 Mar 2015, Mario Lobo wrote:
> 
> > On Thu, 26 Mar 2015 10:29:51 -0600 (MDT)
> > Warren Block <wblock at 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 at 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 at freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> >> To unsubscribe, send any mail to
> >> "freebsd-emulation-unsubscribe at 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.

Your very same command and completion time:

# Papi/root [19:57:15]
[~]>VBoxManage list vms
"Spyket" {ce95fb65-bbfa-41a6-88da-535c7787992e}
"WinXP" {a85af28a-f8f8-4843-aa4a-b3bd92548407}
"Mac-OSx" {80e1a550-c820-4634-a08b-7b5d4820baa0}
"Snow" {40e03b2c-0c09-46f3-8474-ae642b05525b}
"OS-2" {40af0724-31b7-44da-93c8-995e921b01e3}
"LAB-AMD" {8612946c-a246-471d-96da-c97f53a08f5d}
"LAB-APM" {a908923f-4bf8-43b1-ad1a-6411191582b4}
"LAB-BNT" {4bcd6031-f690-4534-bc82-f45547555c37}
"LAB-BSM" {0582c0d8-2262-4f8f-bb84-4cdc80edfde3}
"LAB-ROBO" {37a24b05-1dbb-4d75-81c6-a224cb16012c}
"LAB-VSM" {77e5748c-57fa-4fd2-a252-9e05a36f84ed}
"LAB-VSM101" {6a907348-04a4-4a84-936e-0403b9f9dfd4}
"Debian" {376bd25c-c366-476b-9ca3-c7236c3376c4}
"Windows 7 Allen" {ea84135a-9228-47b3-ac45-f8ccc1235646}
"Win7" {d5d585b6-b327-4c8c-9e90-c004614e5c9e}
"Novell-5" {22b6df7a-a0a0-4b50-aade-44e4953d753a}
"Wn98-Novell" {f1bfbe87-0ab0-4432-aa33-0d9c39e2a337}
"Praieira Server" {a94d0c31-4eb2-4904-8853-e6fce8aaa709}
"Praieira Client" {cca0b54c-27ff-42a9-a840-4de1c779caaf}
"Win8" {15e27358-8d9a-4068-beaa-0cbbecdacac0}
"Dynatrace" {c132cf27-4c6e-4866-aa36-cf227a8e660b}

# Papi/root [19:57:21]

All of these machines run perfectly, started in any way possible
(VBoxManage headless, VBox SDL or the GUI)

My build options:

DBUS - GUESTADDITIONS - NLS - PULSEAUDIO - PYTHON
QT4 - UDPTUNNEL (I run some labs) - VDE - VNC
X11



-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winblows FREE)
 
"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."