--- ./emulators/virtualbox-ose/files/XXXpatch-src-VBox-Additions-x11-Installer-98vboxadd-xclient.ORIG	2015-02-19 20:22:36.079499835 +0100
+++ ./emulators/virtualbox-ose/files/patch-src-VBox-Additions-x11-Installer-98vboxadd-xclient	2015-04-04 09:23:57.000000000 +0200
@@ -1,6 +1,15 @@
---- src/VBox/Additions/x11/Installer/98vboxadd-xclient.orig	2015-02-12 11:08:13.000000000 -0500
-+++ src/VBox/Additions/x11/Installer/98vboxadd-xclient	2015-02-12 14:38:40.689104000 -0500
-@@ -28,9 +28,9 @@
+--- src/VBox/Additions/x11/Installer/98vboxadd-xclient.orig	2015-03-16 18:00:34.000000000 +0100
++++ src/VBox/Additions/x11/Installer/98vboxadd-xclient	2015-04-04 09:22:20.000000000 +0200
+@@ -21,16 +21,16 @@
+     test -w $i || rm -f $i
+ done
+ 
+-if test -f /proc/modules && ! grep -q vboxguest /proc/modules 2>/dev/null; then
++if [ "X`/bin/kenv smbios.system.product 2>/dev/null`" != XVirtualBox ] ; then
+    # Do not start if the kernel module is not present.
+-   notify-send "VBoxClient: the VirtualBox kernel service is not running.  Exiting."
++   : notify-send "VBoxClient: the VirtualBox kernel service is not running.  Exiting."
+ elif test -z "${SSH_CONNECTION}"; then
     # This script can also be triggered by a connection over SSH, which is not
     # what we had in mind, so we do not start VBoxClient in that case.  We do
     # not use "exit" here as this script is "source"d, not executed.