-
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
Installation on macOS #818
Comments
Did you actually try the steps in my comment (the one this issue is tied to)? It doesn't look like you did. Give that a shot first. |
Fresh macOS install, no problems following your instructions. Now I don't know how to use QEMU but that's another problem. |
Er, libvirt setup in macOS is still borked. This is the error I get on my machine: $ vagrant up --provider libvirt
==> default: VM not created. Moving on...
Bringing machine 'default' up with 'libvirt' provider...
/opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': incompatible library version - /Users/andrew/.vagrant.d/gems/2.4.2/gems/ruby-libvirt-0.7.0/lib/_libvirt.bundle (LoadError)
from /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /Users/andrew/.vagrant.d/gems/2.4.2/gems/ruby-libvirt-0.7.0/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 /Users/andrew/.vagrant.d/gems/2.4.2/gems/fog-libvirt-0.4.2/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 /Users/andrew/.vagrant.d/gems/2.4.2/gems/vagrant-libvirt-0.0.40/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 /Users/andrew/.vagrant.d/gems/2.4.2/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/provider.rb:29:in `driver'
from /Users/andrew/.vagrant.d/gems/2.4.2/gems/vagrant-libvirt-0.0.40/lib/vagrant-libvirt/action/create_networks.rb:26:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:90:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:90:in `finalize_action'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:20:in `block in initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:20:in `map'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:20:in `initialize'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/builder.rb:170:in `new'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/builder.rb:170:in `to_app'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/builtin/call.rb:52:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:227:in `action_raw'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:202:in `block in action'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:631:in `lock'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:188:in `call'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:188:in `action'
from /opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run' This is AFTER running several convoluted steps just to get ruby-libvirt kinda-sorta installed with native extensions in the ~/.vagrant.d/gems/ directory. Now, I have no idea what is causing the incompatibility error, or how to go about resolving it in macOS. Some Arch users are having luck by forcibly installing the 0.6.0 version of ruby-libvirt. However, when I run I eventually found an old version of the vagrant-libvirt plugin that targets (through fog-libvirt) ruby-libvirt 0.6.0: vagrant-libvirt 0.0.32. Unfortunately, after installing this via I'm using Vagrant 2.0.1, libvirt 3.9.0, qemu 2.5.0_2, Homebrew 1.3.7, macOS High Sierra. |
|
See also: #497 (comment) |
I have a somehow similar issue on Vagrant 2.2.7 (on Mac OS Mojave 10.14.6) using several options (from the basic
Here is the log:
Note that I have reinstalled the missing header files sudo rm -rf /Library/Developer/CommandLineTools
xcode-select --install
cd /Library/Developer/CommandLineTools/Packages/
open macOS_SDK_headers_for_macOS_10.14.pkg I start to be out of options. The many bug reports (for instance nokogiri#1923 do not seem useful... Any hint would be welcome... Of course, a local install of nokogiri works like a charm...
|
Ok, so temporarily disabling
` |
Is this even possible? I want to run a QEMU vm through libvirt using the latest macOS High Sierra.
Some folks managed to get it to work here #497, but mine just won't. Here's what I did so far:
This doesn't work. Libxml2 version installed through Homebrew is 2.9.6. My vagrant version is 2.0.0. Libvirt is 3.8.0.
Then I've tried the rbenv workaround by installing the ruby version Vagrant uses to rbenv ($ rbenv install 2.3.4 && rbenv shell 2.3.4).
The error message is always the same:
And here's the mkmf.log file:
I do not know how to make it use the latest libxml2, if that's the issue.
Anyone tried this?
The text was updated successfully, but these errors were encountered: