You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the version of VirtualBox on the host and the version of the VirtualBox Guest Additions installed on the guest do not match, you'll get a message like this during a vagrant up:
dking@desktop21 ~/Projects/vagrant-drupal (develop) $ vagrant up
[default] Importing base box 'ubuntu-10.04.4-server-amd64'...
[default] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.
Guest Additions Version: 4.1.6
VirtualBox Version: 4.1.16
Currently, we're installing the Guest Additions during the base box build. The version of Guest Additions is determined programmatically by looking at the version of VirtualBox currently installed on the host. As a result, the chances that a user will get this warning message are high.
Would it be impractical to have a base box per VirtualBox version moving forward?
Let's take a look at installing the Guest Additions during the chef-solo run. Perhaps it's own cookbook. Is there an ubuntu package? Not sure how long it would take, but the file would be around 40-50MB just to download.
FWIW, the warning is displayed, but I haven't run into an issue yet with VirtualBox releases in the 4.1.x series.
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. I haven't had time to test vagrant-vbguest yet, but at this point its looking like the solution. I'd rather leverage the community than have to write more custom cookbooks.
If the version of VirtualBox on the host and the version of the VirtualBox Guest Additions installed on the guest do not match, you'll get a message like this during a
vagrant up
:Currently, we're installing the Guest Additions during the base box build. The version of Guest Additions is determined programmatically by looking at the version of VirtualBox currently installed on the host. As a result, the chances that a user will get this warning message are high.
FWIW, the warning is displayed, but I haven't run into an issue yet with VirtualBox releases in the 4.1.x series.
The text was updated successfully, but these errors were encountered: