qemu:///system is hard to discover

Bug #226899 reported by Soren Hansen
6
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Fix Released
Undecided
Soren Hansen
Hardy
Fix Released
Undecided
Unassigned
Intrepid
Fix Released
Undecided
Soren Hansen

Bug Description

Binary package hint: virt-manager

Even if you manage to figure out that you need to add yourself to the libvirtd group, you still need the command line to discover qemu:///system

If you're in the libvirtd group (and hence have access to the qemu:///system UNIX socket), it should just show up in virt-manager.

Revision history for this message
Soren Hansen (soren) wrote :
Revision history for this message
Soren Hansen (soren) wrote :

Included in SRU: 0.5.3-0ubuntu10

Changed in virt-manager:
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into -proposed, please test and give feedback here

Changed in virt-manager:
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Verified. With hardy-final, after gconftool-2 --recursive-unset /apps/virt-manager, I do not have any default connections. With hardy-proposed, I have the system and session instances by default.

Revision history for this message
Martin Pitt (pitti) wrote :

Copied to hardy-updates. Please upload to intrepid ASAP.

Changed in virt-manager:
status: Fix Committed → Fix Released
assignee: nobody → soren
Changed in virt-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.