Comment # 5 on bug 1201730 from Dan ������erm������k

(In reply to Markus Zimmermann from comment #4)
> I fully understand taking a long time to reply. No worries. Thanks for
> taking a look!
> 
> We are currently in the process of finally upgrading to LEAP 15.4 and i can
> take another look at this. Unfortunately the situation is not much better.
> 
> The problem (then and now) is that one cannot compile vagrant-libvirt or use
> it with that LEAP provides, at all. So if someone wants to use it, the
> latest version i mean, they have to specifically find out which packages
> need to be recompiled.
> 
> E.g. i cannot simple run `vagrant plugin install --local` which installs the
> plugins of the Vagrantfile. Because then it does not find libvirt library.
> So the first thing i have to do by hand is run the following:
> 
> `CONFIGURE_ARGS='with-libvirt-lib=/usr/lib64
> with-libvirt-include=/usr/include/libvirt' vagrant plugin install --local`
> 
> Now i can compile but when i do now a `vagrant up` I receive a trace with
> the following error
> 
> ```
> /opt/vagrant/embedded/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:
> in `require': /usr/lib64/libssh.so.4: undefined symbol: EVP_KDF_CTX_new_id,
> version OPENSSL_1_1_1d -
> /home/zimmski/symflower/.vagrant/plugins/gems/2.7.6/gems/ruby-libvirt-0.8.0/
> lib/_libvirt.so (LoadError)
> ```

My guess is that you are running into version conflicts here: vagrant is
pulling down an incompatible version of ruby-libvirt and your local libssh. You
could try to somehow pin the ruby-libvirt version, but afaik vagrant is
notoriously bad at resolving dependcies for plugins correctly.

> So libssh.so.4 is missing that symbol i have never heard of and now as a
> user i need to compile OpenSSL/LibSSH just to get a package running for
> Vagrant so i can use KVM VMs over libvirt instead of VirtualBox VMs. That is
> what bugs me. I am happy to not have the Vagrant packages in the repository.
> But i cannot even install them out of the box. I have to compile notoriously
> hard to compile base projects to get there.
> 
> I appreciate any help, even if it is just pinpointing me to the script on
> how you are compiling. Because i am out of ideas. This is really frustrating
> because we cannot upgrade to 15.4 (we now have to) so i have to either find
> a new way of dealing what Vagrant does (impossible) or recompile everything
> until i am there.

The only help that I can offer is to suggest that you try to use the rpm
packages from Virtualization:vagrant. That's the only packages that are build
for your distribution and which I can reasonably influence. If you want to use
the upstream binaries, then please ask in the vagrant support forums.