>>> Install virtualbox-guest-additions-3.0.0 into /var/tmp/portage/app-emulation/virtualbox-guest-additions-3.0.0/image/ category app-emulation * Installing vboxadd module * Installing vboxvfs module install: cannot stat `vboxadd-service': No such file or directory !!! doins: vboxadd-service does not exist chmod: cannot access `/var/tmp/portage/app-emulation/virtualbox-guest-additions-3.0.0/image//usr/sbin/vboxadd-service': No such file or directory same in 3.0.2 in /var/tmp/portage/app-emulation/virtualbox-guest-additions-3.0.2/work/VirtualBox-3.0.2_OSE/src/VBox/Additions/linux/Makefile.kmk I found the following line $(QUIET)$(VBOX_LNX_ADD_BIN_COPY) $(PATH_BIN)/additions/VBoxService $(VBOX_LNX_ADD_INS_OUT_DIR)/vboxadd-service thus, it appears vboxadd-service was originally termed VBoxService and VBoxService is present in out/linux.x86/release/bin/additions/ I'll attach a working patch for the ebuild in a moment Reproducible: Always
Created attachment 197673 [details, diff] patch for the ebuild to install VBoxService as vboxadd-service
(In reply to comment #0) [..] Fixed in overlay, thanks!
The same here with the app-emulation/virtualbox-guest-additions-3.1.0 ebuild.
(In reply to comment #3) > The same here with the app-emulation/virtualbox-guest-additions-3.1.0 ebuild. In version 3.1.0 the kernel module is called vboxguest.ko and the installed service in /usr/sbin/ is vboxguest-service instead of vboxadd-service. I believe the init script used to start the daemon should be fixed by replacing the string vboxadd for vboxguest.
I confirm comment #4 is a working solution to starting service.
This however has not been implemented yet and the bug should be reopened.