VirtualBox

Opened 11 years ago

Last modified 10 years ago

#12262 closed defect

vboxautostart-service is not executed correctly on startup in Debian — at Version 1

Reported by: _Thomas_ Owned by:
Component: host support Version: VirtualBox 4.3.0
Keywords: Cc:
Guest type: all Host type: Linux

Description (last modified by Frank Mehnert)

Somehow the startup script in the Debian dist does not auto start configured auto start engines. To fix this it is necessary to tweak the vboxautostart-service script not to exit when the modules are not detected. I don't know why but somehow the checking of loaded modules fails, probably it is because of some background startup. However the modules are loaded after start and also auto startup works when simply disabled the checking. Of course it breaks handling of real problems.

Please see following discussion for some users haveing this issue: https://forums.virtualbox.org/viewtopic.php?f=11&t=51529

*** vboxautostart-service.orig	2013-10-26 22:28:25.000000000 +0200
--- vboxautostart-service	2013-10-26 22:09:13.000000000 +0200
*************** start() {
*** 271,277 ****
      begin_msg "Starting VirtualBox VMs configured for autostart";
      vboxdrvrunning || {
          fail_msg "VirtualBox kernel module not loaded!"
!         exit 0
      }
      PARAMS="--background --start --config $VBOXAUTOSTART_CONFIG"
  
--- 271,277 ----
      begin_msg "Starting VirtualBox VMs configured for autostart";
      vboxdrvrunning || {
          fail_msg "VirtualBox kernel module not loaded!"
!     ##    exit 0
      }
      PARAMS="--background --start --config $VBOXAUTOSTART_CONFIG"
  

Change History (1)

comment:1 by Frank Mehnert, 11 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use