Update README with FAQs

This commit is contained in:
Jeffrey Wildman 2016-04-09 17:43:24 -04:00
parent 0889cdb1d5
commit 6a47082113

View file

@ -1,18 +1,39 @@
homebrew-virt-manager
=====================
Updated/new formulae to build `virt-manager` and `virt-viewer` on Mac OSX.
A set of [homebrew][homebrew] formulae to build [`virt-manager`][virt-manager] and [`virt-viewer`][virt-viewer] on Mac OSX.
# Usage
## Usage
brew tap jeffreywildman/homebrew-virt-manager
brew install virt-manager virt-viewer
# Notes
## FAQs
* For remote URIs, the `libvirt` socket location may need to be overridden to prevent socket hangups, see [www.jedi.be](http://www.jedi.be/blog/2011/09/13/libvirt-fog-provider/#macosx-remote-libvirt-client-).
#### Why can't I connect to a remote URI?
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
When connecting to remote URIs, you probably need to override the `libvirt` socket location, see [www.jedi.be][jedi].
* SSH passwords for connecting to remote URIs are not prompted unless `--debug` or `--no-fork` is used to start `virt-manager`.
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).
[homebrew]: http://brew.sh/
[virt-manager]: https://virt-manager.org/
[virt-viewer]: https://virt-manager.org/
[jedi]: http://www.jedi.be/blog/2011/09/13/libvirt-fog-provider/#macosx-remote-libvirt-client-