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
I've run into a situation where Vagrant seems to incorrectly detect the Virtualbox Guest Additions (GA) version. When I start the VM I get the warning that the GA version does not match the Virtualbox version.
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 6.0.0 r127566
default: VirtualBox Version: 7.0
Which is very strange because if I check the version of VBoxControl from inside the VM I do get the correct version:
# VBoxControl --version
7.0.20r163906
This is a custom image which I build with packer so for debug purposes I kept the .vbox_version and the ISO (VBoxGuestAdditions.iso) around and those both show the correct version.
# cat .vbox_version
7.0.20
VBoxLinuxAdditions.run has
label="VirtualBox 7.0.20 Guest Additions for Linux"
Which make me wonder how Vagrant determines the version of Guest Additions.
Vagrant version
Vagrant 2.4.1
Host operating system
Ubuntu 24.04.1 LTS
Guest operating system
Debian GNU/Linux 12 (bookworm)
Steps to reproduce
Hard to do without my image but let me know if I need to check some additional things.
Hi,
I've run into a situation where Vagrant seems to incorrectly detect the Virtualbox Guest Additions (GA) version. When I start the VM I get the warning that the GA version does not match the Virtualbox version.
Which is very strange because if I check the version of VBoxControl from inside the VM I do get the correct version:
This is a custom image which I build with packer so for debug purposes I kept the
.vbox_version
and the ISO (VBoxGuestAdditions.iso
) around and those both show the correct version.VBoxLinuxAdditions.run
hasWhich make me wonder how Vagrant determines the version of Guest Additions.
Vagrant version
Host operating system
Guest operating system
Steps to reproduce
Hard to do without my image but let me know if I need to check some additional things.
Vagrantfile
The text was updated successfully, but these errors were encountered: