#10 Auto start en stop does not work anymore in Ubuntu Jaunty

[Mark Baaijens]

Automatic stopping (on system halt) and starting (on system boot) does not work anymore in Jaunty. This is confirmed on updated systems, as well as a fresh install. The log file (~/.VirtualBox/vboxtool.log) does show some activity, so the mechanism in which /etc/init.d/vboxtoolinit makes calls to the vboxtool script is working, but these actions are not effective.

Manually stopping and starting through 'sudo /etc/init.d/vboxtoolinit stop | start' works fine.

Modified /etc/rc.local to call (vboxtool) routines directly, manually save sessions and reboot:
1: su - <session user> -c "vboxtool start '<session name>'"
-> log shows the start command, but session is in aborted (!) state

2: su - user -c "VBoxManage startvm 'Ubuntu JeOS'" > /home/user/vboxtool-error.log
-> vboxtool-error.log shows
Waiting for the remote session to open...
ERROR: Virtual machine 'Ubuntu JeOS' has terminated unexpectedly during startup
Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee <NULL>

VBox.log shows no errors or warnings, but the last message was this:
00:00:15.545 Changing the VM state from 'DESTROYING' to 'TERMINATED'.

Executing the rc.local commands manually, works as expected. Apparently, starting VBox-sessions within a system context, whether rc.local or init.d, is a problem in Jaunty.

[Mark Baaijens]

[Mark Baaijens]

The init system is changed in Ubuntu, so that processes don't wait for each other (hence faster boot). The workaround, is using 'nohup' in vboxtoolinit.

Reported bug in Ubuntu: https://bugs.launchpad.net/ubuntu/+bug/372633
Solution found in forum thread: http://ubuntuforums.org/showthread.php?t=1144800

After the mentioned bug is solved, maybe the workaround must be reverted, depending on the solution.

[Mark Baaijens]

Solved in SVN version 53.