vagrant-libvirt doesn't start VM F30

Created on 12 Aug 2019 · 33Comments · Source: hashicorp/vagrant

Vagrant version

2.2.5

Host operating system

Fedora 30

Guest operating system

CentOS 7

Debug output

/opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': /opt/vagrant/embedded/lib64/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libssh.so.4) - ~/.vagrant.d/gems/2.4.6/gems/ruby-libvirt-0.7.1/lib/_libvirt.so (LoadError)

Expected behavior

vagrant up server fails

Actual behavior

Should succeed.

Steps to reproduce

Install vagrant-libvirt
Use Fedora 30; updated - uses openssl-1.1.1c
start vagrant up server

hosfedora installer

Source

mbevc1

👍2

Most helpful comment

You can fix this by building libssh.so.* from source using the /opt/vagrant/embedded as the openssl root then installing it into /opt/vagrant/embedded/lib64:

dnf download --source libssh
rpm2cpio libssh-0.9.0-5.fc30.src.rpm | cpio -imdV
tar xf libssh-0.9.0.tar.xz
mkdir build
cd build
cmake ../libssh-0.9.0 -DOPENSSL_ROOT_DIR=/opt/vagrant/embedded/
make
cp lib/libssh* /opt/vagrant/embedded/lib64

that got it working for me. When the libvirt provider is run it picks up libssh.so.4 from the embedded libraries which are now linked to openssl from the same place.

JamesReynolds on 9 Oct 2019

👍19 ❤7 🎉2

All 33 comments

https://github.com/vagrant-libvirt/vagrant-libvirt/issues/1031 Doesn't help

mbevc1 on 12 Aug 2019

@mbevc1 - Please make sure you've installed the official installer and try again. If that doesn't work, does it work if you install the official 2.2.4 package? Additionally, does it work with other providers that are officially supported, or does this only happen with the vagrant-libvirt provider? Thanks!

briancain on 12 Aug 2019

I'm using official package from Hashicorp :+1:
hm, virtualbox provider seems to work okay.

mbevc1 on 12 Aug 2019

@mbevc1 - Does it work with a previously released package of Vagrant? Do you have a full debug log showing the behavior too?

briancain on 12 Aug 2019

Nope, same error using 2.2.4.

 INFO box: box update check is under the interval threshold
 INFO box: Skipping box update check
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x000000000245a810>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x000000000245a798>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x000000000245a748>
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 4 hooks defined.
 INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x0000000001e990c0>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x0000000001e15450>
 INFO warden: Calling IN action: #<VagrantPlugins::ProviderLibvirt::Action::IsCreated:0x0000000001e15428>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x0000000001e152c0>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x0000000001e152c0>
 INFO warden: Calling OUT action: #<VagrantPlugins::ProviderLibvirt::Action::IsCreated:0x0000000001e15428>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x0000000001e15450>
ERROR warden: Error occurred: /opt/vagrant/embedded/lib64/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libssh.so.4) - /home/xxx/.vagrant.d/gems/2.4.6/gems/ruby-libvirt-0.7.1/lib/_libvirt.so
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000000000245a748>
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Released process lock: machine-action-96993d6040bfbf8204caf27e900ef00d
 INFO environment: Running hook: environment_unload
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 3 hooks defined.
 INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x00007f7dd0908210>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x000000000366a1b8>
 INFO warden: Calling IN action: #<VagrantPlugins::Triggers::Action::Trigger:0x000000000366a190>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x00000000022e9828>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x00000000022e97b0>
 INFO warden: Calling IN action: #<VagrantPlugins::Triggers::Action::Trigger:0x00000000022e9788>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x000000000223a7d8>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x000000000223a760>
 INFO warden: Calling IN action: #<VagrantPlugins::Triggers::Action::Trigger:0x000000000223a738>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x000000000230bdb0>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x000000000230bdb0>
 INFO warden: Calling OUT action: #<VagrantPlugins::Triggers::Action::Trigger:0x000000000223a738>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x000000000223a760>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x000000000223a7d8>
 INFO warden: Calling OUT action: #<VagrantPlugins::Triggers::Action::Trigger:0x00000000022e9788>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x00000000022e97b0>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::AfterTriggerAction:0x00000000022e9828>
 INFO warden: Calling OUT action: #<VagrantPlugins::Triggers::Action::Trigger:0x000000000366a190>
 INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::BeforeTriggerAction:0x000000000366a1b8>
/opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': /opt/vagrant/embedded/lib64/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libssh.so.4) - /home/xxx/.vagrant.d/gems/2.4.6/gems/ruby-libvirt-0.7.1/lib/_libvirt.so (LoadError)
    from /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/xxx/.vagrant.d/gems/2.4.6/gems/ruby-libvirt-0.7.1/lib/libvirt.rb:11:in `<top (required)>'
    from /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/xxx/.vagrant.d/gems/2.4.6/gems/fog-libvirt-0.6.0/lib/fog/libvirt.rb:4:in `<top (required)>'
    from /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/xxx/.vagrant.d/gems/2.4.6/gems/vagrant-libvirt-0.0.45/lib/vagrant-libvirt/driver.rb:1:in `<top (required)>'
    from /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /home/xxx/.vagrant.d/gems/2.4.6/gems/vagrant-libvirt-0.0.45/lib/vagrant-libvirt/provider.rb:29:in `driver'
    from /home/xxx/.vagrant.d/gems/2.4.6/gems/vagrant-libvirt-0.0.45/lib/vagrant-libvirt/action/create_networks.rb:26:in `initialize'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:113:in `new'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:113:in `finalize_action'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:36:in `block in initialize'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:36:in `map'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:36:in `initialize'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builder.rb:170:in `new'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builder.rb:170:in `to_app'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/call.rb:52:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/box_check_outdated.rb:84:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /home/xxx/.vagrant.d/gems/2.4.6/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /home/xxx/.vagrant.d/gems/2.4.6/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /home/xxx/.vagrant.d/gems/2.4.6/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/runner.rb:102:in `block in run'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/runner.rb:102:in `run'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/machine.rb:238:in `action_raw'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/machine.rb:209:in `block in action'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/environment.rb:613:in `lock'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/machine.rb:195:in `call'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/machine.rb:195:in `action'
    from /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'

mbevc1 on 12 Aug 2019

@briancain I've tried to look at this from the vagrant-libvirt side, and AFAICT the problem stems from needing ruby-libvirt bindings that require linking to the system installed libvirt library. It turns out on Fedora and RHEL 7, libvirt depends on libssh, and it appears that in turn this uses libssl which is provided via openssl.

As both the distro and embedded ruby in vagrant provide openssl, each time they provide different versions there is the potential for a failure to load. As long as the version on the system that is a dependency of the system libvirt library is close enough to the version bundled with vagrant, the ruby-libvirt bindings can be loaded. However once they diverge, you get an error like the above.

It appears that ubuntu/debian have not been building libvirt using libssh, which is why users of these distros have avoided hitting this issue.

One solution would be to bump the version of openssl bundled with the ruby env in the vagrant packages, however I'm not sure if that would cause other conflicts elsewhere. The other is for fedora users to always have to use the distribution provided package of vagrant as that would ensure consistency between the libraries.

Outside of these, there starts to be some questions about whether it's necessary to bundle the entire libvirt client libraries and dependencies with vagrant-libvirt for some distros or rewrite it to use the client command line rather than the API via fog-libvirt.

electrofelix on 13 Aug 2019

Thanks for you feedback @electrofelix :+1:
@briancain is there anything from your side we can do to rectify this on CentOS/Fedora systems?
Seems like quick fix would be like @electrofelix suggested and rebuild with latest libs, and maybe on the long run try to bundle it without those deps?

mbevc1 on 13 Aug 2019

You can fix this by building libssh.so.* from source using the /opt/vagrant/embedded as the openssl root then installing it into /opt/vagrant/embedded/lib64:

dnf download --source libssh
rpm2cpio libssh-0.9.0-5.fc30.src.rpm | cpio -imdV
tar xf libssh-0.9.0.tar.xz
mkdir build
cd build
cmake ../libssh-0.9.0 -DOPENSSL_ROOT_DIR=/opt/vagrant/embedded/
make
cp lib/libssh* /opt/vagrant/embedded/lib64

that got it working for me. When the libvirt provider is run it picks up libssh.so.4 from the embedded libraries which are now linked to openssl from the same place.

JamesReynolds on 9 Oct 2019

👍19 ❤7 🎉2

@JamesReynolds thanks, that works like charm in fedora 31!

guits on 25 Feb 2020

👍2

The fix mentioned above doesn't work on fedora 32, it can't find the source for libssh

dnf download --source libssh 

Last metadata expiration check: 0:06:01 ago on Mon 04 May 2020 06:17:03 PM CDT.
No package libssh-0.9.4-2.fc32.src available.
Exiting due to strict setting.
Error: No package libssh-0.9.4-2.fc32.src available.

rmb938 on 5 May 2020

Worked perfectly on F32 here :tada: . Thanks @JamesReynolds !
I needed to use same approach for missing /usr/lib64/libk5crypto.so.3 as well:

dnf download --source krb5-libs
rpm2cpio krb5-1.18-1.fc32.src.rpm | cpio -imdV
tar xf krb5-1.18.tar.gz
cd krb5-1.18/src
./configure
make
cp -a lib/crypto/libk5crypto.* /opt/vagrant/embedded/lib64/

That will ensure to pick those pre-compiled libs in :+1:

mbevc1 on 8 May 2020

👍4 🚀1

@mbevc1 - For some reason I still get the libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL error when running vagrant with libvirt. Is there a step in your instructions to link the kerberos lib compile to the openssl used by vagrant?

buckaroogeek on 8 May 2020

Pre-compilation is dome before building native extensions for the Vagrnat plugin. Then during that it should pick up libs from embedded folder :thinking:

mbevc1 on 8 May 2020

@mbevc1 - thanks Marko. For some reason I was still getting get this error:" /usr/lib64/libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b" which indicates to me that the libk5crypto files in /opt/vagrant/embedded/lib64 are being ignored. But I did a fresh install of vagrant 2.2.9, copied both the ssh and libk5crypto libraries as noted earlier in this thread and 'vagrant plugin install vagrant-libvirt' worked cleanly and the plugin also is running correctly. I do appreciate your help!

buckaroogeek on 8 May 2020

🎉1

dnf download --source krb5-libs
rpm2cpio krb5-1.18-1.fc32.src.rpm | cpio -imdV
tar xf krb5-1.18.tar.gz
cd krb5-1.18/src
./configure
make
cp -a lib/crypto/libk5crypto.* /opt/vagrant/embedded/lib64/

Is there something extra getting built or copied over with this approach compared to the system library? Just wondering if you could simply install the krb5-libs package and copy over the library files instead of recompiling them?

electrofelix on 10 May 2020

I think you could also pick those libs from the system and copy it to embedded folder. I have that package installed and I reckon it's not picking up default lib path on Fedora :thinking:

mbevc1 on 10 May 2020

I can confirm this works on Fedora 32 with the official RPM (not the one in the Fedora repos) once the steps tlisted above to manually build and copy libssh and the libk5 into /opt/vagrant are performed. Thank you!

xyloplax on 16 May 2020

Is anybody having issues running "make"? I get this "yacc: Command not found" error.
btw, I'm on Fedora 32 with the latest vagrant 2.2.9.

yacc getdate.y
make[2]: yacc: Command not found
make[2]: * [: getdate.c] Error 127
make[2]: Leaving directory '/home/fabio/sandbox/krb5/krb5-1.18/src/kadmin/cli'
make[1]: [Makefile:865: all-recurse] Error 1
make[1]: Leaving directory '/home/fabio/sandbox/krb5/krb5-1.18/src/kadmin'
make: ** [Makefile:1546: all-recurse] Error 1

rfm83 on 17 May 2020

Install byacc RPM
~
# sudo dnf install byacc
~

snagoor on 17 May 2020

@snagoor. Thanks, I was able to get past the yacc error after installing byacc.
However, I still have the issue with running vagrant 2.2.9 with the following error:

_opt/vagrant/embedded/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': /usr/lib64/libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b - /home/fabio/.vagrant.d/gems/2.6.6/gems/ruby-libvirt-0.7.1/lib/_libvirt.so (LoadError)_

I have tried re-installing vagrant and the libvirt plugin, but nothing seems to help.

rfm83 on 18 May 2020

@rochafab - did you also try the steps @mbevc1 outlined in https://github.com/hashicorp/vagrant/issues/11020#issuecomment-625801983 above?

dnf download --source krb5-libs
rpm2cpio krb5-1.18-1.fc32.src.rpm | cpio -imdV
tar xf krb5-1.18.tar.gz
cd krb5-1.18/src
./configure
make
cp -a lib/crypto/libk5crypto.* /opt/vagrant/embedded/lib64/

And then install vagrant-libvirt plugin?

buckaroogeek on 18 May 2020

@buckaroogeek - Yes, I did install the krb5-libs and then the vagrant-libvirt plugin as mentioned above, but I still get that error.
I was successfully running vagrant and libvirt with the distro version 2.2.6 and libvirt 0.0.45, but I had issues trying to assign static IPs to the vms. Somebody mentioned downgrading to libvirt 0.0.40 fixes that issue, but I was unsuccessful. Then I decided to pick up the latest upstream vagrant version 2.2.9 and libvirt 0.1.2, but now I get this libk5crypto.so.3: error and can't even run vagrant.

rfm83 on 18 May 2020

@rochafab, I was having the same issue you mentioned on Fedora Workstation 32. Tried all the steps mentioned here. But none worked.

So, finally I tried this https://github.com/vagrant-libvirt/vagrant-libvirt/issues/1031#issuecomment-517578903 and it worked.

It throws few deprecated warnings, which is still fine for me until I'm able to bring up some hosts using vagrant.

snagoor on 18 May 2020

@snagoor - which part specifically did you try that worked?

rfm83 on 18 May 2020

Remove HashiCorp package:
~~~

sudo dnf remove vagrant

~
Install Fedora vagrant package:
~

sudo dnf install vagrant

~
Remove vagrant-libvirt package from Fedora:
~

sudo dnf remove vagrant-libvirt

sudo dnf remove rubygem-fog-core (conflict with plugin building)

~~~

Build the upstream vagrant-libvirt:
~~~

vagrant plugin install vagrant-libvirt

~~~

and then
~~~

vagrant up

~~~

snagoor on 18 May 2020

👍1

@snagoor - No luck. Did you have to set the environment variable in order to install the libvirt plugin?

_export CONFIGURE_ARGS="with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib64"_

I get errors when I try to install the plugin before setting the env variable above. After that, I'm able to install the plugin, but I'm still stuck with the _libk5crypto.so.3_ error.
I'm suspecting the environment variable needs to be changed to reflect the correct ruby version in my case.

rfm83 on 19 May 2020

I have same problem with vagrant-libvirt plugin

[jhnidek@localhost candlepin]$ vagrant status
/opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': /usr/lib64/libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b - /home/jhnidek/.vagrant.d/gems/2.4.9/gems/ruby-libvirt-0.7.1/lib/_libvirt.so (LoadError)

I suspect that problem is with ruby-libvirt gem, because it is not compiled, but it is simply (including _libvirt.so) downloaded as you can see here:

[jhnidek@localhost candlepin]$ vagrant plugin install vagrant-libvirt
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
Fetching: excon-0.73.0.gem (100%)
Fetching: formatador-0.2.5.gem (100%)
Fetching: fog-core-2.2.0.gem (100%)
Fetching: fog-json-1.2.0.gem (100%)
Fetching: mini_portile2-2.4.0.gem (100%)
Fetching: nokogiri-1.10.9.gem (100%)
Building native extensions.  This could take a while...
Fetching: fog-xml-0.1.3.gem (100%)
Fetching: ruby-libvirt-0.7.1.gem (100%)
Building native extensions.  This could take a while...
Fetching: fog-libvirt-0.7.0.gem (100%)
Fetching: vagrant-libvirt-0.1.2.gem (100%)
Installed the plugin 'vagrant-libvirt (0.1.2)'!

BTW: setting environment variable LD_LIBRARY_PATH to /opt/vagrant/embedded/lib64 didn't solve this issue either.

jirihnidek on 25 May 2020

@jirihnidek can you try the instructions mentioned in https://github.com/hashicorp/vagrant/issues/11020#issuecomment-540043472.

ruby-libvirt is compiling, the file /home/jhnidek/.vagrant.d/gems/2.4.9/gems/ruby-libvirt-0.7.1/lib/_libvirt.so is what it compiles against the system libvirt and the ruby embedded with vagrant.

/home/jhnidek/.vagrant.d/gems/2.4.9/gems/ruby-libvirt-0.7.1/lib/_libvirt.so is loading likely loading openssl, but it's the version from under /opt/vagrant/embedded/lib64, and it is also loading to load /usr/lib64/libk5crypto.so.3 which requires some symbols that are not present in the version bundled with vagrant. If you build the libssh package and add the resulting files to the vagrant lib directory, it should allow everything to load correctly.

I will try to get to merging the correct instructions for vagrant-libvirt on Fedora 30+ along with alternative suggestion to consider using the distro bundled version to avoid the issues with libraries mismatching.

electrofelix on 25 May 2020

👍1

If you are switching back and forth between upstream vagrant and the fedora package, it might be helpful to remove or rename ~/.vagrant.d after a 'dnf erase vagrant' is executed.

buckaroogeek on 25 May 2020

@jirihnidek - I finally was able to work around this problem and I believe what fixed the issue in the end was to install both the libssh and krb5-libs from source. Just make sure you match the libssh version accordingly so you don't get errors.

_dnf download --source libssh
rpm2cpio libssh-0.9.0-5.fc30.src.rpm | cpio -imdV
tar xf libssh-0.9.0.tar.xz
mkdir build
cd build
cmake ../libssh-0.9.0 -DOPENSSL_ROOT_DIR=/opt/vagrant/embedded/
make
cp lib/libssh* /opt/vagrant/embedded/lib64_

_dnf download --source krb5-libs
rpm2cpio krb5-1.18-1.fc32.src.rpm | cpio -imdV
tar xf krb5-1.18.tar.gz
cd krb5-1.18/src
./configure
make
cp -a lib/crypto/libk5crypto.* /opt/vagrant/embedded/lib64/_

rfm83 on 26 May 2020

👍1

On a RHEL8 systems building libssh using the steps above caused me the following error:

[ 60%] Linking CXX executable libsshpp_noexcept
/usr/lib64/libk5crypto.so: undefined reference to `EVP_KDF_derive@OPENSSL_1_1_1b'
/usr/lib64/libk5crypto.so: undefined reference to `EVP_KDF_ctrl@OPENSSL_1_1_1b'

to build libssh successfully, I disabled the GSSAPI / Kerberos support in libssh since I don't plan to use it.

Before executing cmake from the commands above:

sed -i 's/WITH_GSSAPI "Build with GSSAPI support" ON/WITH_GSSAPI "Build with GSSAPI support" OFF/' ../libssh-0.9.0/DefineOptions.cmake

After copying the libraries, I had to build the plugin with the following command, to make sure the embedded libraries where picked:

CONFIGURE_ARGS='with-ldflags=-L/opt/vagrant/embedded/lib with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib'  vagrant plugin install vagrant-libvirt

And no more run time error :

vagrant status 
Current machine states:
default                   running (libvirt)

I suppose everybody in this thread now understand the value of Linux distributions doing that tedious packaging work :)

EmmanuelKasper on 21 Jun 2020

👍2

So would it be the solution to include libssh with disabled GSSAPI support in Vagrant? Anybody care to submit PR?

voxik on 18 Aug 2020

I'm unable to get it working on F32 as of 2020-08-27. Can someone confirm the following steps are what's needed?

Uninstall all distro packages
Install all build deps
Install CentOS rpm from https://www.vagrantup.com/downloads.html
Build libssh without fedora patches and copy to vagrant folder

dnf download --source libssh
rpm2cpio libssh-*.src.rpm | cpio -imdV
tar xf libssh-*.tar.xz
mkdir build
cd build
cmake ../libssh-* -DOPENSSL_ROOT_DIR=/opt/vagrant/embedded/
make
sudo cp lib/libssh* /opt/vagrant/embedded/lib64

Build krb5-libs without fedora patches and copy to vagrant folder

dnf download --source krb5-libs
rpm2cpio krb5-*.src.rpm | cpio -imdV
tar xf krb5-*.tar.gz
cd krb5-*/src
./configure
make
sudo cp -a lib/crypto/libk5crypto.* /opt/vagrant/embedded/lib64/

Build plugin with configure arguments telling vagrant where to look for libvirt headers/libs:

CONFIGURE_ARGS="with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib64" \
  vagrant plugin install vagrant-libvirt

squarebracket on 28 Aug 2020

👍1

Was this page helpful?

0 / 5 - 0 ratings

Related issues

Vagrantfile and insecure option (certificate issue)

jsirex · 3Comments

'vagrant up' causes 'ip_parts' error

tomhking · 3Comments

Mounting NFS on Ubuntu 16.04 host - systemd output issues

luispabon · 3Comments

Windows: unable to install plugin using local gem file

rrzaripov · 3Comments

Force destroy vagrant instance that "was not found configured for this Vagrant environment"

gwagner · 3Comments