Vagrant 2.3.5 unable to install plugins

Vagrant
1

OS: WIndows 10 Pro
Provider: VIrtual Box 7.0.8
Vagrant: 2.3.5

I installed the Vagrant 2.3.5 update, destroyed my current instance, and tried to load plugins to get ready to re-up my Vagrantfile.

I find this doesn’t work due to a missing security certificate:

E:\Vagrant Boxes>vagrant plugin install vagrant-vbguest
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
ERROR:  SSL verification error at depth 3: unable to get local issuer certificate (20)
ERROR:  You must add /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority to your local trusted store
Vagrant failed to load a configured plugin source. This can be caused
by a variety of issues including: transient connectivity issues, proxy
filtering rejecting access to a configured plugin source, or a configured
plugin source not responding correctly. Please review the error message
below to help resolve the issue:

  SSL_connect SYSCALL returned=5 errno=0 peeraddr=99.84.66.26:443 state=error: certificate verify failed (https://gems.hashicorp.com/specs.4.8.gz)

Source: https://gems.hashicorp.com/

I have seen this same error when attempting to use other Vagrant commands. My current workaround is to fall back to Vagrant 2.3.4, until this is resolved.

2023 05 18; 09:22: I used Edge Chat (Gen AI) to carry out the following search:

Using Vagrant 2.3.5 on Windows 10 Pro, how do I resolve this error:  
ERROR: SSL verification error at depth 3: unable to get local issuer certificate (20) ERROR: You must add /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority to your local trusted store Vagrant failed to load a configured plugin source. This can be caused by a variety of issues including: transient connectivity issues, proxy filtering rejecting access to a configured plugin source, or a configured plugin source not responding correctly. Please review the error message below to help resolve the issue: SSL_connect SYSCALL returned=5 errno=0 peeraddr=99.84.66.26:443 state=error: certificate verify failed (https://gems.hashicorp.com/specs.4.8.gz) Source: https://gems.hashicorp.com/

The query resulted in this initial response:

It seems like you are encountering an SSL verification error while trying to load a configured plugin source. This error can be caused by a variety of issues including transient connectivity issues, proxy filtering rejecting access to a configured plugin source, or a configured plugin source not responding correctly ¹.

One possible solution is to add the certificate mentioned in the error message to your local trusted store. You can do this by exporting the certificate and adding it to the `cacert.pem` file located in the embedded Ruby directories within the Vagrant installation ². You may need to contact your IT department for assistance with exporting the correct certificate ¹.

I hope this helps! Let me know if you have any further questions.

Source: Conversation with Bing, 5/18/2023(1) Vagrant: SSL verification error behind corporate proxy. https://superuser.com/questions/1334264/vagrant-ssl-verification-error-behind-corporate-proxy Accessed 5/18/2023.
(2) ruby - Configuring Vagrant CA Certificates - Stack Overflow. https://stackoverflow.com/questions/45475023/configuring-vagrant-ca-certificates Accessed 5/18/2023.
(3) Install | Vagrant | HashiCorp Developer. https://developer.hashicorp.com/vagrant/downloads Accessed 5/18/2023.
(4) How to configure Vagrant to ignore SSL certificate. https://sleeplessbeastie.eu/2020/12/30/how-to-configure-vagrant-to-ignore-ssl-certificate/ Accessed 5/18/2023.

Implementing this suggested solution is beyond my capabilities. If a Hashicorp rep or some more knowledgeable reader can do so, please make it happen.

2

Hi there,

This is due to an issue with the Windows installer build that was fixed here and will be resolved in the next release which will be shipping shortly. One workaround is to modify the sources for the install:

vagrant plugin install --plugin-clean-sources --plugin-source https://rubygems.org vagrant-vbguest

Another option is to use a development build until the next version has been released.

Cheers!

1 Like
3

Thank you for this. Was pulling my hair out for solutions today.

4

@chrisroberts :: Thanks, this is welcome news. Like others, I’ve been stymied in my work and appreciate the fix coming in on a timely basis. DVH

5

No problem. The 2.3.6 release is now available as well.

6

@chrisroberts :: Thanks, I plan to give 2.3.6 a go and will update here with results. DVH

7

@chrisroberts :: I regret to report that 2.3.6 has the same issue as 2.3.5; I am unable to install vagrant-vbguest plugin directly due to the still missing certificate package. DVH

8

@chrisroberts :: I tried the work-around given earlier in this conversation and got further than I had; still not successful, though. Here is the console output I see:

E:\Vagrant Boxes>vagrant init "generic/fedora37" --force
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.

E:\Vagrant Boxes>vagrant plugin install --plugin-clean-sources --plugin-source https://rubygems.org vagrant-vbguest
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
Fetching micromachine-3.0.0.gem
Fetching vagrant-vbguest-0.31.0.gem
Installed the plugin 'vagrant-vbguest (0.31.0)'!

E:\Vagrant Boxes>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'generic/fedora37' version '4.2.16' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.0.0
VBoxService inside the vm claims: 7.0.8
Going on, assuming VBoxService is correct...
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.0.0
VBoxService inside the vm claims: 7.0.8
Going on, assuming VBoxService is correct...
Redirecting to /bin/systemctl start vboxadd.service
Job for vboxadd.service failed because the control process exited with error code.
See "systemctl status vboxadd.service" and "journalctl -xeu vboxadd.service" for details.
Redirecting to /bin/systemctl start vboxadd-service.service
Job for vboxadd-service.service failed because the control process exited with error code.
See "systemctl status vboxadd-service.service" and "journalctl -xeu vboxadd-service.service" for details.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.0.0
VBoxService inside the vm claims: 7.0.8
Going on, assuming VBoxService is correct...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
6.2.15-200.fc37.x86_64.
ValueError: File context for /opt/VBoxGuestAdditions-7.0.8/other/mount.vboxsf already defined
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted or 'rcvboxadd reload' triggered
VirtualBox Guest Additions: reloading kernel modules and services
Cannot reload kernel modules: one or more module(s) is still in use
The log file /var/log/vboxadd-setup.log may contain further information.
==> default: Checking for guest additions in VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/usr/sbin/rcvboxadd setup

Stdout from the command:

VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
6.2.15-200.fc37.x86_64.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted or 'rcvboxadd reload' triggered
VirtualBox Guest Additions: reloading kernel modules and services


Stderr from the command:

ValueError: File context for /opt/VBoxGuestAdditions-7.0.8/other/mount.vboxsf already defined
Cannot reload kernel modules: one or more module(s) is still in use
The log file /var/log/vboxadd-setup.log may contain further information.

E:\Vagrant Boxes>vagrant ssh
Last login: Thu May 18 17:46:35 2023 from 10.0.2.2
[vagrant@fedora37 ~]$ cd /vagrant
-bash: cd: /vagrant: No such file or directory
[vagrant@fedora37 ~]$ ps -ef
UID          PID    PPID  C STIME TTY          TIME CMD
root           1       0  0 05:34 ?        00:00:02 /usr/lib/systemd/systemd --switched-root --system --deseri
root           2       0  0 05:34 ?        00:00:00 [kthreadd]
root           3       2  0 05:34 ?        00:00:00 [rcu_gp]

<redacted ps output>

root         580       1  0 05:34 ?        00:00:00 /usr/lib/systemd/systemd-logind
root         584       1  0 05:34 ?        00:00:00 /usr/sbin/VBoxService -f
chrony       637       1  0 05:34 ?        00:00:00 /usr/sbin/chronyd -F 2
root         929       1  0 05:34 ?        00:00:00 /usr/sbin/NetworkManager --no-daemon
memcach+     981       1  0 05:34 ?        00:00:00 /usr/bin/memcached -p 11211 -u memcached -m 64 -c 1024 -l
root         983       1  0 05:34 ?        00:00:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
root         985       1  0 05:34 ?        00:00:00 /usr/bin/python3 -Es /usr/sbin/tuned -l -P
root         986       1  0 05:34 tty1     00:00:00 /sbin/agetty -o -p -- \u --noclear - linux
polkitd     1021       1  0 05:34 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
root       30442     550  0 05:44 ?        00:00:00 systemd-userwork: waiting...
root       30443     550  0 05:44 ?        00:00:00 systemd-userwork: waiting...
root       30444     550  0 05:44 ?        00:00:00 systemd-userwork: waiting...
root       30446     983  0 05:47 ?        00:00:00 sshd: vagrant [priv]
vagrant    30450       1  0 05:47 ?        00:00:00 /usr/lib/systemd/systemd --user
root       30451       2  0 05:47 ?        00:00:00 [kworker/1:1-events_power_efficient]
vagrant    30453   30450  0 05:47 ?        00:00:00 (sd-pam)
root       30460       2  0 05:47 ?        00:00:00 [kworker/u4:0-events_unbound]
vagrant    30461   30446  0 05:47 ?        00:00:00 sshd: vagrant@pts/0
vagrant    30462   30461  0 05:47 pts/0    00:00:00 -bash
root       30486       2  0 05:48 ?        00:00:00 [kworker/u4:2-events_unbound]
root       30487       2  0 05:48 ?        00:00:00 [kworker/0:0-events]
vagrant    30488   30462  0 05:48 pts/0    00:00:00 ps -ef
[vagrant@fedora37 ~]$

As shown above, I am able to ssh into the running VBox instance. The /vagrant directory does not exist, and VBox guest additions is not present, so the plugin has clearly failed to function properly.

Advice as to next steps would be most helpful. DVH

RYO System Configuration (updated 2023 04 16): SCP: Win10 Pro x64 Version 22H2 OS Build 19045.2604 Experience Windows Feature Experience Pack 120.2212.4190.0; Mobo: ASUS Crosshair IV Formula Rev 1.02G; BIOS: American Megatrends Inc. V3029 2012/10/31; CPU: AMD Phenom II X4 965 C3 BE, 3.4 GHz; RAM: Corsair Dominator DDR3, 16 GB (4 x 4 GB); SATA III SSD: Samsung 860 EVO 0.5TB; SATA III SSD: Samsung 870 EVO 1TB; SATA III HDD: 2 x Seagate 2 TB (Hybrid SSD/HDD), 1 x Seagate 4 TB, 1 x Seagate Backup Plus 3TB USB3 EHDD; 2 x Seagate OneTouch 5TB USB3 EHDD (with Seagate Toolkit SW for automatic backup); ODD: 1 x Plextor SATA DVD RW, 1 x ASUS SATA BlueRay DVD RW; VGA: EVGA GEForce GTX 750, 1 GB; USB3: 7 port PCIe card, PSU: OCZ FirePower Tech 550W; Case: Eagle Tech-Skyhawk Server; Cooling: CPU-stock; 2 case fans.

Vagrant 2.3.6
Oracle VirtualBox: 7.0.8 r156879

9

@chrisroberts :: 2023 05 20; 15:35: I tried removing the offending file listed in the error logs (actually the entire folder), removing the Guest Additions service, and reinstalling the appropriate VBoxGuestAdditions 7.0.8. The effort resulted in a clear indication that the removal succeeded and the reinstall failed. Here is the relevant console log data:

[vagrant@fedora37 mnt]$ sudo ./VBoxLinuxAdditions.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing VirtualBox 7.0.8 Guest Additions for Linux  100%
VirtualBox Guest Additions installer
./install.sh: line 153: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed.  If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it.  If it is not up-to-date, you
should get a notification when you start the system.  If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.

If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.

Do you wish to continue? [yes or no]
n

Cancelling installation.
[vagrant@fedora37 mnt]$ sudo ./VBoxLinuxAdditions.run uninstall
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing VirtualBox 7.0.8 Guest Additions for Linux  100%
VirtualBox Guest Additions installer
./install.sh: line 153: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed.  If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it.  If it is not up-to-date, you
should get a notification when you start the system.  If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.

If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.

Do you wish to continue? [yes or no]
y
[vagrant@fedora37 mnt]$ sudo ./VBoxLinuxAdditions.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing VirtualBox 7.0.8 Guest Additions for Linux  100%
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
6.2.15-200.fc37.x86_64.
ValueError: File context for /opt/VBoxGuestAdditions-7.0.8/other/mount.vboxsf already defined
[vagrant@fedora37 mnt]$ sudo vbox-uninstall-guest-additions
Removing installed version 7.0.8 of VirtualBox Guest Additions...
[vagrant@fedora37 mnt]$ sudo vbox-uninstall-guest-additions
sudo: vbox-uninstall-guest-additions: command not found
[vagrant@fedora37 mnt]$ sudo ./VBoxLinuxAdditions.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing VirtualBox 7.0.8 Guest Additions for Linux  100%
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
6.2.15-200.fc37.x86_64.
ValueError: File context for /opt/VBoxGuestAdditions-7.0.8/other/mount.vboxsf already defined
[vagrant@fedora37 mnt]$

I took one more look at the issue identified at ValueError, above. The file context is relate to SELinux mods to base Fedora, and from what I can read, this is a benign error which should be ignored. The following commands, apparently, remove the file context, and then restore default context, which seems to be what is needed for the script to run successfully:

[vagrant@fedora37 mnt]$ sudo semanage fcontext -d /opt/VBoxGuestAdditions-7.0.8/other/mount.vboxsf
[vagrant@fedora37 mnt]$ sudo restorecon /opt/VBoxGuestAdditions-7.0.8/other/mount.vboxsf

I then used vagrant reload to restart the VBox instance, which wen through normally:

E:\Vagrant Boxes>vagrant reload
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'generic/fedora37' version '4.2.16' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.
Redirecting to /bin/systemctl start vboxadd.service
Redirecting to /bin/systemctl start vboxadd-service.service
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
6.2.15-200.fc37.x86_64.
ValueError: File context for /opt/VBoxGuestAdditions-7.0.8/other/mount.vboxsf already defined
Restarting VM to apply changes...
==> default: Attempting graceful shutdown of VM...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...

I checked the running services and found the desired result:

E:\Vagrant Boxes>vagrant ssh
Last login: Sat May 20 22:07:45 2023 from 10.0.2.2
[vagrant@fedora37 ~]$ systemctl list-units --type=service
  UNIT                               LOAD   ACTIVE SUB     DESCRIPTION                                       >
  auditd.service                     loaded active running Security Auditing Service
  chronyd.service                    loaded active running NTP client/server
  dbus-broker.service                loaded active running D-Bus System Message Bus
  dkms.service                       loaded active exited  Builds and install new kernel modules through DKMS
  dracut-shutdown.service            loaded active exited  Restore /run/initramfs on shutdown
  firewalld.service                  loaded active running firewalld - dynamic firewall daemon
  getty@tty1.service                 loaded active running Getty on tty1
  haveged.service                    loaded active running Entropy Daemon based on the HAVEGE algorithm
  kmod-static-nodes.service          loaded active exited  Create List of Static Device Nodes
  lvm2-monitor.service               loaded active exited  Monitoring of LVM2 mirrors, snapshots etc. using d>
  lvm2-pvscan@8:3.service            loaded active exited  LVM event activation on device 8:3
  memcached.service                  loaded active running memcached daemon
  NetworkManager-wait-online.service loaded active exited  Network Manager Wait Online
  NetworkManager.service             loaded active running Network Manager
  polkit.service                     loaded active running Authorization Manager
  sshd.service                       loaded active running OpenSSH server daemon
  sysstat.service                    loaded active exited  Resets System Activity Logs
  systemd-boot-update.service        loaded active exited  Automatic Boot Loader Update
  systemd-hostnamed.service          loaded active running Hostname Service
  systemd-journal-flush.service      loaded active exited  Flush Journal to Persistent Storage
  systemd-journald.service           loaded active running Journal Service
  systemd-logind.service             loaded active running User Login Management
  systemd-modules-load.service       loaded active exited  Load Kernel Modules
  systemd-network-generator.service  loaded active exited  Generate network units from Kernel command line
  systemd-oomd.service               loaded active running Userspace Out-Of-Memory (OOM) Killer
  systemd-random-seed.service        loaded active exited  Load/Save Random Seed
  systemd-remount-fs.service         loaded active exited  Remount Root and Kernel File Systems
  systemd-resolved.service           loaded active running Network Name Resolution
  systemd-sysctl.service             loaded active exited  Apply Kernel Variables
  systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service     loaded active exited  Create Volatile Files and Directories
  systemd-udev-trigger.service       loaded active exited  Coldplug All udev Devices
  systemd-udevd.service              loaded active running Rule-based Manager for Device Events and Files
  systemd-update-utmp.service        loaded active exited  Record System Boot/Shutdown in UTMP
  systemd-user-sessions.service      loaded active exited  Permit User Sessions
  systemd-userdbd.service            loaded active running User Database Manager
  systemd-zram-setup@zram0.service   loaded active exited  Create swap on /dev/zram0
  tuned.service                      loaded active running Dynamic System Tuning Daemon
  user-runtime-dir@1000.service      loaded active exited  User Runtime Directory /run/user/1000
  user@1000.service                  loaded active running User Manager for UID 1000
  vboxadd-service.service            loaded active exited  vboxadd-service.service
  vboxadd.service                    loaded active exited  vboxadd.service
  vboxservice.service                loaded active running VirtualBox guest services

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
43 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

What I find strange is that the boot process finds that Guest Additions 7.0.8 is already (correctly) loaded but not running. I would seem to me that just starting the service would make sense. Instead, the plugin goes and tries to reinstall the GA again, and reboots the instance. This seems totally unnecessary. My workaround is to remove the plugin, once I’m sure the proper GA is installed. If I have to start it manually, OK, I can do that.

2023 05 20; 18:10: Well, no I can’t. The instance reports that GA 7.0.8 seems to be installed correctly, but when I try to start it manually, I am unable to do so:

E:\Vagrant Boxes>vagrant reload
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'generic/fedora37' version '4.2.16' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.
Redirecting to /bin/systemctl start vboxadd.service
Redirecting to /bin/systemctl start vboxadd-service.service
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
6.2.15-200.fc37.x86_64.
Restarting VM to apply changes...
==> default: Attempting graceful shutdown of VM...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.

E:\Vagrant Boxes>vagrant vbguest --status
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.

E:\Vagrant Boxes>vagrant vbguest --do start
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.
Redirecting to /bin/systemctl start vboxadd.service
Redirecting to /bin/systemctl start vboxadd-service.service

E:\Vagrant Boxes>vagrant vbguest --status
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.

E:\Vagrant Boxes>vagrant vbguest --do rebuild
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
6.2.15-200.fc37.x86_64.
ValueError: File context for /opt/VBoxGuestAdditions-7.0.8/other/mount.vboxsf already defined

E:\Vagrant Boxes>vagrant vbguest --status
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.

E:\Vagrant Boxes>vagrant vbguest --do start
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.
Redirecting to /bin/systemctl start vboxadd.service
Redirecting to /bin/systemctl start vboxadd-service.service

E:\Vagrant Boxes>vagrant vbguest --status
[default] GuestAdditions seems to be installed (7.0.8) correctly, but not running.

That’s all for today.

I’m not sure what you can do to make this easier, I hope that you will find something and fix these problems so I (and others) can be more productive in using Hashicorp apps. DVH

10

You will likely have better luck with the bento/fedora-37 box which includes the vbox guest additions.

11

@chrisroberts :: OK, thanks. I’ll look into that one. DVH
2023 05 22; 22:37: I’ve looked; it works. Thanks.

12

I’ve been using the following workaround to be able to continue using version 2.3.6 but I would prefer a proper fix.

set SSL_CERT_FILE=C:\HashiCorp\Vagrant\embedded\gems\gems\httpclient-2.8.3\lib\httpclient\cacert.pem

13

I was able to install the vagrant-vbguest plugin using the provided workaround:
“vagrant plugin install --plugin-clean-sources --plugin-source https://rubygems.org vagrant-vbguest”

but am curious - will this be resolved in the next release?

14

vagrant plugin install --plugin-clean-sources --plugin-source https://rubygems.org vagrant-hostmanager
try this …

15

this solutions seems to work for me, drop https://curl.se/ca/cacert.pem in “C:\HashiCorp\Vagrant\embedded”, i got from the above github link, you download the cacert.pem from curl and put it in the embedded folder run the plugin again and the error is gone. hope it helps.

16

Vagrant 2.3.7 has been released which resolves this issue.

17

I am on Vagrant 2.3.7 and VB 7.0. I see these errors when trying to install some plugin.

Installing the 'vagrant-disksize' plugin. This can take a few minutes... ERROR: SSL verification error at depth 2: self-signed certificate in certificate chain (19) ERROR: Root certificate is not trusted (/C=US/ST=CA/L=Santa Clara/O=Netskope Inc./OU=certadmin/CN=certadmin/emailAddress=certadmin@netskope.com)

18

I am also still having this issue on 2.3.7 VB 7.0. It fails on an company managed machine with their Root Certificate.

19

On my mac i had to add the .crt/.pem content of the company (root-)certs.
sudo find / -type f -name cacert.pem 2>/dev/null

/System/Volumes/Data/opt/vagrant/embedded/cacert.pem
After adding no more SSL errors