Hi Klaus,
Hi all,
I have VirtualBox 3.1.2 running on a Solaris 10 host. The
VBoxHeadless instances seem to run stable. But the machine always
again runs into a state where neither the control application nor any
further VBoxHeadless instances come up anymore. The last time I
encountered this I did
pkill -9 VBoxSVC
pkill VBoxXPCOMIPCD
pkill VBoxZoneAccess
After that I could normally startup VirtualBox. This did not help
this time. When I enter
VirtualBox
in a terminal session it hands and the application window never comes
up!? Rebooting the whole machines usually solves this problem. But
that's no good solution! Could this be due to a port conflict? If so
which ports must not be used by other processes on the machine to not
disturb VirtualBox? Any other ideas?
It's certainly not a port conflict as such, as VirtualBox uses unix
domain sockets (in /tmp/.vbox-USERNAME-ipc/). It sounds more like
VBoxSVC or VBoxXPCOMIPCD got wedged, and that causes the client apps
(VirtualBox, VBoxHeadless, VBoxManage ...) to hang as well. However if
you terminate everything that should clear the problem.
Thanks for the feedback. It helped the last time, but not now! :-(
The headless instances still run, but they cannot be restarted and the
VirtualBox control application simply does not come up. I wonder
whether I am the only one with this problem! :-(
Regards,
Andreas
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
