-
Notifications
You must be signed in to change notification settings - Fork 510
Add support to macOS Virtualization Framework #1757
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
base: main
Are you sure you want to change the base?
Conversation
Download the latest artifacts for this pull request here: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One query and I'm also wondering if you think it's reasonable to default the qemu URIs based on the host OS as well?
Also does user networking have other interpretations? https://wiki.qemu.org/Documentation/Networking suggests it's understood to mean something different to the host port forwarding. If there is a canonical resource referring to this approach as user networking will want to make sure referencing it in the docs.
Btw, thanks so much, it's great to have something here that will allow MacOS users to be able to use this project.
end | ||
if qemu_user_networking | ||
networks = [] | ||
else |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm looking at this on a phone, so I could be missing something, if there can't be any networks for qemu_user_networking seems like could just return an empty list here and the rest of the function doesn't need to be modified at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're correct. Just made the change to return an empty list instead.
The current macOS brew package doesn't seem to offer qemu:///system like Linux.
It is the same thing as mentioned in the wiki page.
Sure. It's great to unblock people who experienced the same issue as I did. :) |
Please be aware that the current latest libvirt version 9.6.0 has some issue on M1 Mac which prevents the volume from being created. You may use libvirt 9.5.0. |
87860b1
to
2d61892
Compare
A docker image containing the code from this plugin to allow testing locally without installing If you need the image with the full dev toolchain, you can instead pull: ghcr.io/vagrant-libvirt/vagrant-libvirt:pr-1757 |
This PR allows vagrant-libvirt to work with brew installed libvirt/QEMU with user networking.
Verified on Apple M2.
Fixes: #1205