Closed PauloLaScience closed 3 years ago
Looking at the paths in the error, that doesn't look like it's the distro provided vagrant as I'd expect to see the same paths as appearing in https://fedora.pkgs.org/33/fedora-x86_64/vagrant-2.2.9-3.fc33.noarch.rpm.html. It looks more like an AppImage install when the paths contain /tmp/.mount_vagrankZJYLl/usr/lib/ruby/2.6.0/rubygems/
because it suggests it's temporarily mounting something rather than using the rpm.
Please make sure you are using the distro provided rpm for vagrant as otherwise you'll experience issues due to the need for library linking between system provided libraries (libvirt + dependencies) and the ruby used to execute vagrant.
Once you are using the distro provided vagrant, uninstall the current vagrant-libvirt plugin, install ruby-libvirt without weak dependencies and then reinstall vagrant-libvirt.
vagrant plugin uninstall vagrant-libvirt
dnf --setopt=install_weak_deps=False --best install ruby-libvirt
vagrant plugin install vagrant-libvirt
This will mean that the ruby-libvirt, which provides ruby bindings for libvirt will be the one pre-compiled by the distro to use the same ruby as the packaged vagrant as well as linked against the same libraries as the distro provided libvirt. The subsequent install of vagrant-libvirt
should be very quick as it won't need to try and compile ruby-libvirt.
vagrant was in /usr/local/bin in current version. I delete it after uninstall vagrant-libvirt. Now I'm using packaged vagrant and vagrant-libvirt . It's working now.