Vagrant fails to call VBoxManage #12088

Nohzoh · 2020-11-30T16:20:04Z

Hello,

OS: Ubuntu 20.10
VirtualBox: 6.1.16
Vagrant: 2.2.14

When I launch any command using VBoxManage, the commands fails with this kind of error:

$ VAGRANT_LOG=info vagrant global-status 
 INFO global: Vagrant version: 2.2.14
 INFO global: Ruby version: 2.6.2
 INFO global: RubyGems version: 3.0.3
 INFO global: VAGRANT_INSTALLER_ENV="1"
 INFO global: VAGRANT_APPIMAGE_LD_LIBRARY_PATH="/tmp/.mount_vagran5UDuNE/usr/lib/:/tmp/.mount_vagran5UDuNE/usr/lib/i386-linux-gnu/:/tmp/.mount_vagran5UDuNE/usr/lib/x86_64-linux-gnu/:/tmp/.mount_vagran5UDuNE/usr/lib32/:/tmp/.mount_vagran5UDuNE/usr/lib64/:/tmp/.mount_vagran5UDuNE/lib/:/tmp/.mount_vagran5UDuNE/lib/i386-linux-gnu/:/tmp/.mount_vagran5UDuNE/lib/x86_64-linux-gnu/:/tmp/.mount_vagran5UDuNE/lib32/:/tmp/.mount_vagran5UDuNE/lib64/:"
 INFO global: VAGRANT_RUBYLIB="/tmp/.mount_vagran5UDuNE/usr/local/lib/site_ruby/2.6.0:/tmp/.mount_vagran5UDuNE/usr/local/lib/x86_64-linux-gnu/site_ruby:/tmp/.mount_vagran5UDuNE/usr/local/lib/site_ruby:/tmp/.mount_vagran5UDuNE/usr/lib/ruby/vendor_ruby/2.6.0:/tmp/.mount_vagran5UDuNE/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.6.0:/tmp/.mount_vagran5UDuNE/usr/lib/ruby/vendor_ruby:/tmp/.mount_vagran5UDuNE/usr/lib/ruby/2.6.0:/tmp/.mount_vagran5UDuNE/usr/lib/x86_64-linux-gnu/ruby/2.6.0"
 INFO global: VAGRANT_USR_DIR="/tmp/.mount_vagran5UDuNE/usr"
 INFO global: VAGRANT_APPIMAGE_HOST_LD_LIBRARY_PATH=":/tmp/.mount_vagran5UDuNE/usr/lib/:/tmp/.mount_vagran5UDuNE/usr/lib/i386-linux-gnu/:/tmp/.mount_vagran5UDuNE/usr/lib/x86_64-linux-gnu/:/tmp/.mount_vagran5UDuNE/usr/lib32/:/tmp/.mount_vagran5UDuNE/usr/lib64/:/tmp/.mount_vagran5UDuNE/lib/:/tmp/.mount_vagran5UDuNE/lib/i386-linux-gnu/:/tmp/.mount_vagran5UDuNE/lib/x86_64-linux-gnu/:/tmp/.mount_vagran5UDuNE/lib32/:/tmp/.mount_vagran5UDuNE/lib64/:"
 INFO global: VAGRANT_ROOT_DIR="/tmp/.mount_vagran5UDuNE"
 INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/tmp/.mount_vagran5UDuNE"
 INFO global: VAGRANT_LOG="info"
 INFO global: VAGRANT_PKG_CONFIG_PATH="/tmp/.mount_vagran5UDuNE/usr/lib/x86_64-linux-gnu/pkgconfig-int::/usr/local/lib/x86_64-linux-gnu/pkgconfig:/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib/x86_64-linux-gnu/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig"
 INFO global: VAGRANT_APPIMAGE="1"
 INFO global: VAGRANT_BIN_DIR="/tmp/.mount_vagran5UDuNE/usr/bin"
 WARN global: resolv replacement has not been enabled!
 INFO manager: Registered plugin: autocomplete command
(...)
 INFO vagrant: `vagrant` invoked: ["global-status"]
 INFO environment: Environment initialized (#<Vagrant::Environment:0x0000000002531040>)
 INFO environment:   - cwd: /home/tarnaud/Téléchargements
 INFO environment: Home path: /home/tarnaud/.vagrant.d
 WARN environment: No local data path is set. Local data cannot be stored.
 INFO manager: Plugins:
 INFO manager:   - vagrant-vbguest = [installed: 0.28.0 constraint: > 0]
 INFO manager: Loading plugins...
 INFO manager: Loading plugin `vagrant-vbguest` with default require: `vagrant-vbguest`
 INFO manager: Registered plugin: vagrant-vbguest
 INFO loader: Loading configuration in order: [:home, :root]
 INFO base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
 INFO subprocess: Command not in installer, restoring original environment...
 INFO subprocess: Detected AppImage environment and request to external binary. Updating library path.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write
>
ERROR vagrant: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

ERROR vagrant: /tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/base.rb:440:in `block in execute'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/util/retryable.rb:17:in `retryable'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/base.rb:398:in `execute'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:177:in `block in read_version'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/util/retryable.rb:17:in `retryable'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:176:in `read_version'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:46:in `block in initialize'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:41:in `synchronize'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:41:in `initialize'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/provider.rb:21:in `new'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/provider.rb:21:in `usable?'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:361:in `block in default_provider'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/registry.rb:49:in `block in each'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/registry.rb:48:in `each'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/registry.rb:48:in `each'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:347:in `default_provider'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:943:in `guess_provider'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:955:in `find_configured_plugins'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:983:in `process_configured_plugins'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:178:in `initialize'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/bin/vagrant:168:in `new'
/tmp/.mount_vagran5UDuNE/usr/gembundle/gems/vagrant-2.2.14/bin/vagrant:168:in `<top (required)>'
/tmp/.mount_vagran5UDuNE/usr/gembundle/bin/vagrant:23:in `load'
/tmp/.mount_vagran5UDuNE/usr/gembundle/bin/vagrant:23:in `<main>'
Vagrant failed to initialize at a very early stage:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

Launching VBoxManage --version from the same shell is successful.

The text was updated successfully, but these errors were encountered:

rushikeshkoli · 2020-12-01T10:19:55Z

I am also facing the issue.

alexanderBendo · 2020-12-01T10:49:28Z

I'm having a similar issue. When I try to add a box, it returns the same symbol lookup error

/usr/bin/curl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

Vagrant: 2.2.14
OS: debian 10

darxkies · 2020-12-01T21:28:19Z

Me too on Ubuntu 20.10, VirtualBox 6.1.16 and Vagrant 2.2.14

qprichard · 2020-12-03T12:01:20Z

I'm having a similar issue. When I try to add a box, it returns the same symbol lookup error

/usr/bin/curl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

Vagrant: 2.2.14
OS: debian 10

Installing via .deb file worked for me.

rushikeshkoli · 2020-12-03T12:55:15Z

@qprichard Yep. .deb worked for me as well. Thanks. Now I can learn ansible peacefully

Nohzoh · 2020-12-04T10:05:52Z

Also works for me with .deb under Ubuntu.
Thank you @qprichard !

drewbailey · 2020-12-16T16:44:36Z

Installing via the .deb didn't work for me unfortunately,

VBoxManage --version
6.1.16r140961

output

ERROR vagrant: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

ERROR vagrant: /tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/base.rb:440:in `block in execute'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/util/retryable.rb:17:in `retryable'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/base.rb:398:in `execute'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:177:in `block in read_version'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/util/retryable.rb:17:in `retryable'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:176:in `read_version'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:46:in `block in initialize'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:41:in `synchronize'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/driver/meta.rb:41:in `initialize'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/provider.rb:21:in `new'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/plugins/providers/virtualbox/provider.rb:21:in `usable?'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:361:in `block in default_provider'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/registry.rb:49:in `block in each'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/registry.rb:48:in `each'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/registry.rb:48:in `each'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:347:in `default_provider'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:943:in `guess_provider'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:955:in `find_configured_plugins'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:983:in `process_configured_plugins'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/lib/vagrant/environment.rb:178:in `initialize'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/bin/vagrant:168:in `new'
/tmp/.mount_vagran5FVw9o/usr/gembundle/gems/vagrant-2.2.14/bin/vagrant:168:in `<top (required)>'
/tmp/.mount_vagran5FVw9o/usr/gembundle/bin/vagrant:23:in `load'
/tmp/.mount_vagran5FVw9o/usr/gembundle/bin/vagrant:23:in `<main>'
Vagrant failed to initialize at a very early stage:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

anjuls · 2020-12-17T09:56:59Z

same error on ubuntu 20.10

VBoxManage --version
6.1.16r140961

drewbailey · 2020-12-17T11:11:00Z

My issue is resolved, it was not immediately obvious to me but it's necessary to install vagrant using the .deb, not virtualbox which I had been doing 😅

anjuls · 2020-12-17T12:37:17Z

I am still having the same issue, I have tried installing Vagrant using the .deb file and also the VirtualBox.

vagrant --version
Vagrant 2.2.13

VBoxManage --version
6.1.16r140961

Error:

vagrant up
Vagrant failed to initialize at a very early stage:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

kpanuragh · 2021-01-02T22:03:40Z

try to downgrade the virtualbox version ,I just installed virtualbox 5.1.14r112924 its worked

zigarn · 2021-02-04T16:11:25Z

Same issue here, vagrant installed by extracting the binary from the released zip file:

$ vagrant --version
Vagrant 2.2.14

$ VBoxManage --version
6.1.16_Ubuntur140961

$ vagrant status
Vagrant failed to initialize at a very early stage:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

I can confirm that installing from the Vagrant .deb file solves the issue (but shouldn't be necessary).

brittonhayes · 2021-03-13T01:06:12Z

Confirming same issue on PopOS solved by installing Vagrant .deb

❯ vagrant --version
Vagrant 2.2.14

❯ VBoxManage --version
6.1.16_Ubuntur140961

❯ cat /etc/os-release
NAME="Pop!_OS"
VERSION="20.10"

anjuls · 2021-03-15T08:42:37Z

I had two versions of Vagrant installed, one by directly downloading the executable and another one using *.deb. I have removed the manual installation and it worked after that. Thanks for the guidance.

alexpop · 2021-03-19T07:55:37Z

@anjuls that fixed it for me as well. You are a rockstar 🎸

bcalvim · 2021-03-31T20:24:51Z

I had downloaded the zip file from the official Vagrant website and after unzipping the file and placing Vagrant in Path, I was getting the same error.

❯ vagrant init hashicorp/bionic64
Vagrant failed to initialize at a very early stage:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol: __gmpz_limbs_write

I solved this by removing that version of Vagrant and reinstalling it via apt

sudo apt install vagrant`

After that its working now.

❯ vagrant init hashicorp/bionic64
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.

❯ ls
Vagrantfile

❯ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/bionic64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'hashicorp/bionic64'
    default: URL: https://vagrantcloud.com/hashicorp/bionic64
==> default: Adding box 'hashicorp/bionic64' (v1.0.282) for provider: virtualbox
    default: Downloading: https://vagrantcloud.com/hashicorp/boxes/bionic64/versions/1.0.282/providers/virtualbox.box
Download redirected to host: vagrantcloud-files-production.s3-accelerate.amazonaws.com
==> default: Successfully added box 'hashicorp/bionic64' (v1.0.282) for 'virtualbox'!
==> default: Importing base box 'hashicorp/bionic64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/bionic64' version '1.0.282' is up to date...
==> default: Setting the name of the VM: ambiente_dev_default_1617190635271_29861
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:

  https://www.virtualbox.org/manual/ch04.html#sharedfolders

This option can be disabled globally with an environment variable:

  VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

or on a per folder basis within the Vagrantfile:

  config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
==> 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: 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: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> 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.10
    default: VirtualBox Version: 6.1
==> default: Mounting shared folders...
    default: /vagrant => /home/bruno/Projects/ambiente_dev

❯ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'hashicorp/bionic64' version '1.0.282' is up to date...
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.

❯ vagrant ssh
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-58-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  System information as of Wed Mar 31 20:18:24 UTC 2021

  System load:  0.0               Processes:           89
  Usage of /:   2.5% of 61.80GB   Users logged in:     0
  Memory usage: 11%               IP address for eth0: 10.0.2.15
  Swap usage:   0%

 * Introducing self-healing high availability clusters in MicroK8s.
   Simple, hardened, Kubernetes for production, from RaspberryPi to DC.

     https://microk8s.io/high-availability

0 packages can be updated.
0 updates are security updates.


vagrant@vagrant:~$

soapy1 added appimage provider/virtualbox labels Dec 1, 2020

x-malet mentioned this issue Jun 4, 2021

Fail to lauch vagrant on Linux (Pop-Os) - Vagrant fails to call VBoxManage medmouine/vagrant-k3s-HA-cluster#1

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Vagrant fails to call VBoxManage #12088

Vagrant fails to call VBoxManage #12088

Nohzoh commented Nov 30, 2020 •

edited

rushikeshkoli commented Dec 1, 2020

alexanderBendo commented Dec 1, 2020

darxkies commented Dec 1, 2020

qprichard commented Dec 3, 2020

rushikeshkoli commented Dec 3, 2020

Nohzoh commented Dec 4, 2020

drewbailey commented Dec 16, 2020 •

edited

anjuls commented Dec 17, 2020

drewbailey commented Dec 17, 2020

anjuls commented Dec 17, 2020 •

edited

kpanuragh commented Jan 2, 2021

zigarn commented Feb 4, 2021

brittonhayes commented Mar 13, 2021

anjuls commented Mar 15, 2021

alexpop commented Mar 19, 2021

bcalvim commented Mar 31, 2021

Vagrant fails to call VBoxManage #12088

Vagrant fails to call VBoxManage #12088

Comments

Nohzoh commented Nov 30, 2020 • edited

rushikeshkoli commented Dec 1, 2020

alexanderBendo commented Dec 1, 2020

darxkies commented Dec 1, 2020

qprichard commented Dec 3, 2020

rushikeshkoli commented Dec 3, 2020

Nohzoh commented Dec 4, 2020

drewbailey commented Dec 16, 2020 • edited

anjuls commented Dec 17, 2020

drewbailey commented Dec 17, 2020

anjuls commented Dec 17, 2020 • edited

kpanuragh commented Jan 2, 2021

zigarn commented Feb 4, 2021

brittonhayes commented Mar 13, 2021

anjuls commented Mar 15, 2021

alexpop commented Mar 19, 2021

bcalvim commented Mar 31, 2021

Nohzoh commented Nov 30, 2020 •

edited

drewbailey commented Dec 16, 2020 •

edited

anjuls commented Dec 17, 2020 •

edited