= Proposed Self Contained Change: VirtualBox Guest Integration = https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration
Change owner(s): * Hans de Goede hdegoede@redhat.com
VirtualBox is popular, easy to use virtual-machine software. The purpose of this change is to ship the VirtualBox guest-drivers and -tools by default in the Fedora workstation product.
== Detailed Description == VirtualBox runs on Windows. MacOS and Linux and is used by many users to try it Linux for the first time. As such it is important for Fedora to work well in VirtualBox virtual-machines. Like other virtual-machines VirtualBox virtual-machines can offer an enhanced user-experience when some VirtualBox specific guest-drivers and guest-tools are installed. This change is about adding the guest-drivers to the Fedora kernel package, packaging the userspace-tools (VirtualBox Guest Additions) and adding the VirtualBox Guest Additions package to the default package list for the Workstation product.
== Scope == * Proposal owners:
** Adding the VirtualBox guest drivers to the kernel package. To make this happen work is underway to clean them up and submit them upstream. ** Package VirtualBox Guest Additions userspace parts ** Add VirtualBox Guest Additions package to the default package list for the Workstation product
* Other developers: N/A (not a System Wide Change)
* Release engineering: [1]
* List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
[1] https://pagure.io/releng/issue/6880
Thanks, Jaroslav
On Thu, Jul 06, 2017 at 04:10:29PM +0200, Jaroslav Reznik wrote:
= Proposed Self Contained Change: VirtualBox Guest Integration = https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration
Change owner(s):
- Hans de Goede hdegoede@redhat.com
VirtualBox is popular, easy to use virtual-machine software. The purpose of this change is to ship the VirtualBox guest-drivers and -tools by default in the Fedora workstation product.
Please make sure when running on non-VirtualBox machines the drivers and services are not loaded and there are no warnings emitted. (I know we've had similar problems before — e.g. https://bugzilla.redhat.com/show_bug.cgi?id=999804, and some other bugs I cannot find now, so I'm just saying that this is something worth checking for from the start.) Probably the right solution is to use a udev rule to trigger starting of various services only if the "devices" are found. Something like /usr/lib/udev/rules.d/70-spice-vdagentd.rules in spice-vdagent.rpm.
Zbyszek
Slightly late to the party but please have a look at how open-vm-tools (VMware) works. Some observations:
(1) Anaconda has a special comps group for hypervisors. If Anaconda is able to detect virtualization, it will install extra packages from the hypervisor group automatically. For VMware it's called ‘platform-vmware’.
https://github.com/rhinstaller/anaconda/commit/a475dd0194df7abf0453786fc0147... https://pagure.io/fedora-comps/blob/master/f/comps-f27.xml.in#_4987
(2) In addition to the above, open-vm-tools is protected by ConditionVirtualization=vmware. Despite the other comment in this thread, this works fine and no udev rule is required.
Rich.
Hi,
On 16-07-17 12:51, Richard W.M. Jones wrote:
Slightly late to the party but please have a look at how open-vm-tools (VMware) works. Some observations:
(1) Anaconda has a special comps group for hypervisors. If Anaconda is able to detect virtualization, it will install extra packages from the hypervisor group automatically. For VMware it's called ‘platform-vmware’.
https://github.com/rhinstaller/anaconda/commit/a475dd0194df7abf0453786fc0147... https://pagure.io/fedora-comps/blob/master/f/comps-f27.xml.in#_4987
Thank you for the suggestion I will take this into account when I start working on the actual packaging work, for now I'm focused on cleaning up the kernel drivers.
Regards,
Hans