Go to file
2019-01-06 15:51:51 -05:00
libvirt-glib.rb libvirt-glib: convert patch to inreplace, add test, update dependencies 2019-01-06 15:47:48 -05:00
osinfo-db-tools.rb osinfo-db-tools: update runtime dependencies 2019-01-06 15:48:28 -05:00
osinfo-db.rb osinfo-db: 20181214 2018-12-25 15:04:09 -06:00
README.md virt-manager: 2.0.0 2019-01-05 17:51:11 -05:00
spice-gtk.rb spice-gtk: update deps, add test, remove patch in favor of CFLAGS with -ObjC 2019-01-06 15:51:51 -05:00
spice-protocol.rb spice-protocol: add test 2019-01-06 15:48:53 -05:00
usbredir.rb usbredir: add test 2019-01-06 15:49:30 -05:00
virt-manager.rb virt-manager: 2.0.0 2019-01-05 17:51:11 -05:00
virt-viewer.rb virt-viewer: 7.0 2018-08-18 14:45:14 -04:00

homebrew-virt-manager

A set of homebrew formulae to install virt-manager and virt-viewer on Mac OSX.

Usage

brew tap jeffreywildman/homebrew-virt-manager
brew install virt-manager virt-viewer
virt-manager -c test:///default

FAQs

Why can't I connect to a remote URI?

When connecting to remote URIs, you probably need to override the libvirt socket location, see www.jedi.be.

virt-manager -c 'qemu+ssh://user@libvirthost/system?socket=/var/run/libvirt/libvirt-sock'
virt-viewer -c 'qemu+ssh://user@libvirthost/system?socket=/var/run/libvirt/libvirt-sock'

I still can't connect to a remote URI, why?

This formula for virt-manager does not include the openssh-askpass dependency and does not prompt for passwords in a popup window. Here are two workarounds:

  1. Run virt-manager with either the --debug or --no-fork option to get password prompt via the CLI.

  2. Set up SSH keys between your local and remote system to avoid the prompt.

Why can't I connect to a local URI (e.g., qemu:///system)?

I've not yet tested virt-manager against any local URIs/hypervisors. If you get virt-manager working with a local hypervisor and needed to take any special steps, feel free to share the details.

Everything was working yesterday, but it's not working today, can you help?

If virt-manager or its dependencies have been upgraded recently (brew upgrade), it's possible that a reinstall may fix the issue (see #39).