on first run of vmm it installed libvirt for me and then popped up this message:
Libvirt was just installed, so the 'libvirtd' service will
will need to be started. This can be done with one
of the following:
- From GNOME menus: System->Administration->Services
- From the terminal: su -c 'service libvirtd restart'
- Restart your computer
virt-manager will connect to libvirt on the next application
the first two options are out of date. i'm not sure if it's possible to do the first at all with gnome shell. the second should probably be systemctl restart libvirtd.service
it'd probably be nice to note in the last sentence that double-clicking on 'localhost (QEMU)' in the app window will cause vmm to connect - there's no need to close and reopen the app.
Hmm, and actually systemd exposes a dbus interface for polling services which we can probably use to get better info here, and even offer to start if it isn't running.
*** Bug 800896 has been marked as a duplicate of this bug. ***
*** Bug 825611 has been marked as a duplicate of this bug. ***
Requires system-config-services installed to actually work, so we get nice policykit integration.
virt-manager-0.9.3-1.fc16 has been submitted as an update for Fedora 16.
virt-manager-0.9.3-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-0.9.3-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
virt-manager-0.9.4-1.fc17 has been submitted as an update for Fedora 17.
virt-manager-0.9.4-1.fc16 has been submitted as an update for Fedora 16.
virt-manager-0.9.4-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
virt-manager-0.9.4-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.