Hi Klaus,
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.
I haven't disabled core dumps and get core dumps whenever our own apps
die so I guess it's enabled. I have looked into / for a core file and
found one, but that was generated by one of our own apps. Can I force
the system to write the core dumps for VBoxSVC into a specific
directory so that they are not overwritten by other processes? Usually
core dumps are put into the current directory from which the process
was started but since VBoxSVC is started automatically by the vbox
infrastructure I am not sure how to do that!?
Thanks,
Andreas
_______________________________________________
vbox-users mailing list
vbox-users@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-users
