Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38689 - [virtualbox] module loading for vboxservice unit file

Attached to Project: Community Packages
Opened by Christian Hesse (eworm) - Monday, 27 January 2014, 14:29 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 05 August 2014, 00:01 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The systemd unit file vboxservice.service has race conditions and/or does not load modules. Starting the service on boot results in the service to fail. Module vboxguest is loaded later on automatically, restarting the servive afterwards succeeds. Though it still misses some functionallity: Shared folders are not mounted as vboxsf does not get loaded at all.

I want to use this on live media, so adding the modules to autoload from /etc/modules.load.d/ is not an option. This would give errors on every system except virtualbox. I would suggest to add modprobe commands to the service file:

ExecStartPre=/usr/bin/modprobe vboxguest
ExecStartPre=/usr/bin/modprobe vboxvideo
ExecStartPre=/usr/bin/modprobe vboxsf

Additional info:
virtualbox-guest-utils 4.3.6-3
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 05 August 2014, 00:01 GMT
Reason for closing:  Implemented
Additional comments about closing:  4.3.14-3
Comment by Doug Newgard (Scimmia) - Monday, 03 February 2014, 15:45 GMT
If you can start the service on boot, why can't you use modules.load.d?
Comment by Christian Hesse (eworm) - Monday, 03 February 2014, 15:51 GMT
The service has a condition to only start if virtualization is 'oracle'. That's fine.

Adding the modules to modules.load.d makes them load always - even if the system is not a virtualbox virtual machine. Loading the modules in this case failes.

So the easiest way to load the modules only if needed is to add the modprobe calls to the service.
Comment by Doug Newgard (Scimmia) - Monday, 03 February 2014, 16:00 GMT
So the service is always enabled? OK, I was just confused by what seemed like a conflict, able to set the service to load but not able to set modules.load.d.
Comment by Sébastien Luttringer (seblu) - Monday, 04 August 2014, 23:17 GMT
I will make the execution not mandatory, to prevent breakage of users config who load modules via dkms.

Loading...