Ticket #7837 (new enhancement)
Feature Request: Option to hide Additions mismatch warning
|Reported by:||TwistedLincoln||Owned by:|
Currently, if the "guest properties" feature is used, VirtualBox will check a guest to see what version of the Guest Additions are installed. If the version of the additions that are currently loaded in the guest do not exactly match the version of VirtualBox that you are running, a warning dialog is presented in the guest indicating that you may want to update the Additions.
This is a bit irritating, as there are several legitimate reasons to run mis-matched versions. For example, if you compile your own OSE version, Guest Additions will only be generated for the platform you compiled on. So if you don't have access to a build environment for the other platforms, the only choice is to use the official Additions ISO. Up until 4.0, there was a distinction made between the OSE version and the PUEL, so even if you were running the same version of the Additions, you would get a warning if one was OSE and the other PUEL. I assume that won't be an issue anymore with the move to the open core, but the same can easily be said for testing SVN versions, or making customized versions, etc.
Also, there a a few GNU/Linux distros that ship with Guest Additions pre-installed, and since most of the time the core functionality still works, there is no compelling need to upgrade. And there are still other distros that ship older versions of VirtualBox in their repositories, and you may be sharing Virtual Machines with multiple distros across a LAN -- since each distro may have a different version of VirtualBox installed, the error will pop up on some distros but not others.
In any event, I've currently worked around this issue by disabling the guest properties feature at compile time, but that disables an entire feature set that is otherwise useful.
I admit this is a bit of a specialized request, but it would be great to be able to be able to either disable this warning message alone at compile time, or be able to suppress it somewhere within the VirtualBox settings.