Opened 8 years ago
Closed 7 years ago
#15847 closed defect (fixed)
VBoxService is not started on CentOS 6 after running guest extensions installer -> partially fixed in releases greater than 5.1
| Reported by: | James Brown | Owned by: | |
|---|---|---|---|
| Component: | guest additions | Version: | VirtualBox 5.1.4 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Mac OS X |
Description
VBoxService (a.k.a. vboxadd-service) is not started after the guest extensions installer (VBoxLinuxAdditions.run) finishes running. My guest in this case is a minimal CentOS 6 install. It appears that (as of 5.1.x?) vboxadd-service is required for guest IP reporting to work.
This seems undesirable; it means that certain VM features don't work properly until the host is rebooted after installing guest additions (since vboxadd-service is set to start on boot), and completely breaks running Vagrant guests under VirtualBox 5.1.x.
I modified VBoxLinuxAdditions.run to self-execute under /bin/sh -x to get some debugging output; it's at https://gist.github.com/Roguelazer/0db8863bfc328881a16f1e3fb07904e5.
The normal guest additions installer log (VBoxGuestAdditions.log) is attached.
Attachments (1)
Change History (3)
by , 8 years ago
| Attachment: | VBoxGuestAdditions.log added |
|---|
comment:1 by , 8 years ago
| Summary: | VBoxService is not started on CentOS 6 after running guest extensions installer → VBoxService is not started on CentOS 6 after running guest extensions installer -> partially fixed in releases greater than 5.1 |
|---|
This will be fixed to some extent in future major releases. It required slightly more script changes than seemed justified for a minor release. However, newly installed Additions will not always be functional before a guest reboot (for example because old drivers cannot be unloaded).
comment:2 by , 7 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
VBoxGuestAdditions.log