forked from jengelh/virtualbox
d72c0caca1
- Version bump to 6.0.8 (released May 13 2019 by Oracle) This is a maintenance release. The following items were fixed and/or added: Core: fix saved state resume failures (bugs #18265 and #18331) User interface: show full file location in New Medium window. User interface: fix mouse click pass-through problems in multi-screen virtual machines (6.0.6 regression, bug #18567) Graphics: fixed a crash when powering off a VM without graphics controller (bug #18570) API: partial fix for dealing with VM config conflicting with other VMs related to medium UUIDs, now correctly flags VM as inaccessible (bug #17908) Linux hosts: fix kernel module build breakage in non-default build set-ups (bug #18620, thank you Ambroz Bizjak) Linux hosts: fix kernel module build breakage in debug build set-ups (bug #18621, thank you Ambroz Bizjak) Windows guests: notice file size increases in shared folders which were missed in certain cases Linux guests: make shared folders work with Linux 3.16.35 Linux guests: fix incorrectly read-only shared folders (bug #18345) - Modify "fixes_for_qt13.1" for i586 builds qith Qt 5.13 - Limit all architectures to a maxium of 2 jobs. Without this restriction, 32-bit builds run out of memory, and 64-bit builds get strange crashes. - LTO builds still failing. Reset flag to nil. - Changed the way that the spec file limits the 32-bit builds to 2 threads. boo#1133492. If enough memory were allocated so that the full number of workers were allowed, the job would never be scheduled. OBS-URL: https://build.opensuse.org/request/show/705282 OBS-URL: https://build.opensuse.org/package/show/Virtualization/virtualbox?expand=0&rev=488
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