Failed to start vboxadd.service (on boot)

[Xorcist]

So I recently installed LL4.0 from the ISO onto an Acer Aspire-E500, and the boot takes way longer than it should.

Referencing the boot.log (see attachment) I see ton of:

  A start job is running for vboxadd.service (1min 39s / 5min 2s)

entries followed by:

  Failed to start vboxadd.service.
    See 'systemctl status vboxadd.service' for details.

Any ideas why this is happening (and or how to rectify it)?

[firenice03]

[member=5406]Xorcist[/member]  You can speed up boot time... From the release notes https://www.freecinema2022.gq/forums/relea...-released/



Performance Tips:


- For start up (boot time) - if you have no plans to run VirtualBox, and you want faster boots, you can remove it's supported additions:

Code:

sudo apt purge virtualbox*
sudo systemctl stop vboxadd.service
sudo systemctl stop vboxadd-service.service
sudo systemctl disable vboxadd.service
sudo systemctl disable vboxadd-service.service

Should speed you right back up 

[Xorcist]

Thanks! That definitely sped up the boot time alot, but any ideas why it would be failing in the first place? Are there common reasons this might occur? I've done quite a few LL 4.0 installs and this was the first to have this issue.

[Xorcist]

Oh wow, I just checked all my other LL 4.0 installs and found they all had the same failure, though the boot times were never that terrible. Removed the VirtualBox startup from all of them and am amazed at how quick these machines can boot up. I assume the reason all of them were failing is because this is something that is used when LL 4.0 is run as a VM in VirtualBox, and therefore unnecessary if run on real hardware (is that a fair assumption)?

[kpanic]

[member=5406]Xorcist[/member] , if you don't need Virtualbox additions, you may as well remove them:

I'm not 100% sure (I forgot the package name, since I removed it already,
but maybe this will do it (in terminal window)

Code:

sudo apt-get purge virtualbox-guest-additions-iso

- kp