-
Notifications
You must be signed in to change notification settings - Fork 499
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
fail to install with error: "No working libvirt installation found" #1671
Comments
The vagrant package installed is for x86_64 architecture When you brew install libvirt it will be for the m1 arm64 architecture, so it's not possible to link between the x86_64 ruby in vagrant and the arm64 libraries such as libvirt. The only option is to do brew install of ruby and then a bundle install of vagrant until such stage as either vagrant-libvirt doesn't need ruby-libvirt or hashicorp supply an arm64 binary package of vagrant. |
first of all thank you @electrofelix for replying so quickly
I though rosetta would take care of this, how do I install the arm version for vagrant, |
AFAIK, there is no pre built vagrant package for Mac arm64. I believe the interface to both VMWare and QEMU is by calling the CLI directly with specific arguments. This avoids issues around architecture because they are not directly needing to access the libraries of the other application. Unfortunately, since this project depends on fog-libvirt and ruby-libvirt (which made sense to not have to model everything) it requires being able to link against libvirt and that has caused quite a few problems over time. While some progress is being made, it'll take a while to resolve fully. The options effectively become limited to using brew to install ruby and libvirt, and then using However it's not necessarily going to work because vagrant-libvirt currently has a dependency on being able to create a management network, and I'm not sure that libvirt on Mac supports that capability yet. https://gitlab.com/libvirt/libvirt/-/issues/75 suggests it's not yet there. I am hopeful over the next couple of months to work on using qemu/libvirt's port forwarding capabilities to remove the need for the dedicated management network, though if you need a network for something else, that won't help much. |
Going to close this in favour of tracking all the issues with installing on arm64 for MacOS under #1205, a comment on that issue suggests a possible workaround for now #1205 (comment) and there is another issue #1703 covers using vmnet to create networks, which should be possible to be reference now due to the addition of the |
I'm encountering the error below when running
vagrant plugin install vagrant-libvirt
setup
install homebrew
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
install in homebrew
brew install --cask vagrant && \ brew install make gcc qemu libiconv libvirt
double check libvirt path
update path
error
info
logs
mkmf.log
gem_make.out.zip
related issues:
#497
#818
#1017
#1461 (my own) cc @electrofelix
mirror:
stackoverflow
The text was updated successfully, but these errors were encountered: