Vagrant runs the virtualbox guest additions installer everytime if --provision is used.

I noticed I get the error below every time I use the --provision flag with vagrant up.

[virtualbox] GuestAdditions seems to be installed (6.1.32) correctly, but not running.

Then vagrant runs the guest addtions: VirtualBox Guest Additions: Starting.

I am still trying to figure out how it all works, but if I run:
$sudo systemctl disable vboxadd.service, this behavior quits and I get:
[virtualbox] GuestAdditions 6.1.32 running --- OK.

I do have the vagrant vagrant-vbguest plugin installed and I don't know what will happen when I upgrade my virtualbox to the next version.

If this is the right way to fix the issue, I was thinking you might want to add it to your role that installs the vbguest addtions.

Reproduce the behavior with `vagrant up --provision` and inspect the role that installs the VirtualBox Guest Additions, focusing on the `vboxadd.service` state mentioned in the report. Confirm the intended behavior across provisioning and a VirtualBox upgrade before defining the change; done means provisioning no longer reruns the installer unnecessarily.

Written by the indexing model from the issue text.