Vagrant: Vagrant fails to call VBoxManage

Created on 30 Nov 2020 · 11Comments · Source: hashicorp/vagrant

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.

appimage providevirtualbox

Source

Nohzoh

👍5

Most helpful comment

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

anjuls on 17 Dec 2020

👍2

All 11 comments

I am also facing the issue.

rushikeshkoli on 1 Dec 2020

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

alexanderBendo on 1 Dec 2020

Me too on Ubuntu 20.10, VirtualBox 6.1.16 and Vagrant 2.2.14

darxkies on 1 Dec 2020

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.

qprichard on 3 Dec 2020

👍2

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

rushikeshkoli on 3 Dec 2020

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

Nohzoh on 4 Dec 2020

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

drewbailey on 16 Dec 2020

👍1

same error on ubuntu 20.10

VBoxManage --version
6.1.16r140961

anjuls on 17 Dec 2020

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 😅

drewbailey on 17 Dec 2020

👍1

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

anjuls on 17 Dec 2020

👍2

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