All, I have finally taken the time to dig into the annoying habit of the vboxadd.service systemd service file causing recompilation of the vboxguest modules both on startup and shutdown.
When the kernel is updated, there is no reason for the following to run on shutdown /opt/VBoxGuestAdditions-5.2.34/init/vboxadd start The current service file created for vboxadd.service is: [Unit] SourcePath=/opt/VBoxGuestAdditions-5.2.34/init/vboxadd Description= Before=runlevel2.target runlevel3.target runlevel4.target runlevel5.target shutdown.target display-manager.service display-manager.service After= Conflicts=shutdown.target [Service] Type=oneshot Restart=no TimeoutSec=5min IgnoreSIGPIPE=no KillMode=process GuessMainPID=no RemainAfterExit=yes ExecStart=/opt/VBoxGuestAdditions-5.2.34/init/vboxadd start ExecStop=/opt/VBoxGuestAdditions-5.2.34/init/vboxadd stop [Install] WantedBy=multi-user.target This causes the guest to appear to hang on shutdown while the modules are compiled yet again. The issue is that on new kernel install for the guest, there is no reason to rebuild on shutdown and again on startup (and again on shutdown and again on startup...) Removing the shutdown.target from the Before= line allows the service to be run on reboot a single time with systemctl start vboxadd.service to rebuild the guest kernel modules and then it does not hang again on shutdown. Rather than me patching for my local machine, shouldn't this be solved for everyone?? -- David C. Rankin, J.D.,P.E. _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
