- Merge host kmp and guest kmp into a single kmp. The existence of two different kernel module
packages is believed to be the reason that it is possible for a new kernel not to include
the necessary kernel modules (boo#1142955).
Files "virtualbox-host-kmp-files" and "virtualbox-guest-kmp-files" are deleted.
File "virtualbox-kmp-files" is added.
Files "virtualbox-host-preamble" and virtualbox-guest-preamble" are deleted.
File "virtualbox-kmp-preamble" is added.
File "fix_conflict_between_host_and_guest.patch" is added.
- Script vboxdrv.sh, which is called from the systemd service file, incorrectly called a routine
that does not exist when the kernel modules were not available. This call is changed to /sbin/vboxconfig
that will build the modules if the requisite packages are available. If that is not true, the
systemctl status vboxdrv will list the command needed to load the missing packages. This change
address part of boo#1142995.
OBS-URL: https://build.opensuse.org/request/show/719647
OBS-URL: https://build.opensuse.org/package/show/Virtualization/virtualbox?expand=0&rev=498
Prerequisites
=============
Users, that want to use the VirtualBox autostart feature, have to be
members of the vboxusers group.
E.g.:
sudo usermod -aG vboxusers USERNAME
Preparation
===========
For each autostart user, add a section in /etc/vbox/autostart.cfg:
USERNAME = {
allow = true
}
Users work
==========
The *first* time a user configures autostart, the command:
VBoxManage setproperty autostartdbpath /etc/vbox
needs to be run.
Note: The autostart options are stored in the /etc/vbox file, and in the
VM itself. If moving a VM, these options may need to be set again.
Prepare a VM to start automatically:
VBoxManage modifyvm <uuid|vmname> --autostart-enabled <on|off>
Choose a shut down mode:
VBoxManage modifyvm <uuid|vmname> --autostop-type <disabled|savestate|poweroff|acpishutdown>
Restart the vboxdrv service to start the VMs in question
sudo service vboxdrv restart
06c8f73ab1