New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vagrant-libvirt load error: /lib64/libssh.so.4: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b #1088
Comments
I dont think this error is related to vagrant-libvirt.
your ruby-libvirt installation expects a symbol EVP_KDV_ctrl which is not included in your installed openssl libssh version. and: |
@abbbi - Wonderful! Worked like a charm! I followed the steps @JamesReynolds provides in hashicorp/vagrant#11020 (comment) adjusting for a slightly newer version of libssh thank you |
Thanks for the info @buckaroogeek seems a bit excessive to have to build the dependency libraries from source though. Still I'll give it a go. Anything to get a working vagrant-libvirt on a more modern base install 👍 |
I completely agree! I can say that after taking these steps I have been
able to do a 'vagrant plugins update' without problem and also update using
the upstream rpm package from 2.2.9 to 2.2.10 also without issue and
continue to start my centos/8 and fedora32 server vms successfully.
brad
…On Thu, Sep 3, 2020 at 7:01 AM adamprice2 ***@***.***> wrote:
Thanks for the info @buckaroogeek <https://github.com/buckaroogeek> seems
a bit excessive to have to build the dependency libraries from source
though. Still I'll give it a go. Anything to get a working vagrant-libvirt
on a more modern base install 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1088 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKDYHR5R6ZB3LVCL7FT7PTSD6OU3ANCNFSM4MEBTGBA>
.
|
OK I got a chance to try the fix from hashicorp/vagrant#11020 (comment) on a clean Centos 8 install this morning and it doesn't work. |
Same issue on F33. I'm amazed that Vagrant has no solid 1st class Libvirt support. I tried to use Vagrant for Libvirt for several times in the past, but always failed at some point. It's 2021 and Vagrant still has out of the box issues with Libvirt. Sorry for little complaining. Just added reminder that issue persists. I tried "vanilla" install, i tried rpm install.. booth have some kind of issues and no human readable errors. Why would i use VirtualBox on the KVM machine? Any reasons? |
I cannot use the libvirt plugin on fedora 31.
Steps to reproduce
Expected behaviour
Vagrant starts vm correctly with libvirt provider
Actual behaviour
System configuration
OS/Distro version:: Fedora 31
Libvirt version:
vagrant-libvirt (0.0.45, global)
Output of
vagrant version; vagrant plugin list
:Installed Version: 2.2.7
vagrant-libvirt (0.0.45, global)
*
Output of
VAGRANT_LOG=debug vagrant ... --provider=libvirt
*A Vagrantfile to reproduce the issue:
Are you using upstream vagrant package or your distros package?
Upstream
The text was updated successfully, but these errors were encountered: