Hi all,
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! :-(
I don't follow... the entire VirtualBox infrastructure is dead once
you kill VBoxSVC. VBoxHeadless instances may continue to run for some
time, but usually they abort pretty quickly. If they don't, they
nevertheless keep the local domain socket open and thus can
potentially cause trouble.
So whenever this problem occurs I have to shutdown all Headless
instances?
I'm pretty sure that there are not that many people out there who are
haunted by such massive VBoxSVC problems. The number of reports in
that direction is pretty close to zero, and that means your problem
is special. Maybe you could enable core dumps, to see whether the
real cause is actually a VBoxSVC crash before you get into this odd
state.
No core dump is generated. No VirtualBox process crashes. Something
just hangs. It seems this happens whenever a Headless instance is shut
down. We haven't upgraded the VBoxAdditions yet (used VB 2.0.6 before
the upgrade to 3.1.2) . Could that cause this problem?
Thanks,
Andreas
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
