Comment 21 for bug 187048

Dustin - Thanks for the script, but unfortunately virt-manager can manage
VMs both locally and remotely - you wouldn't want someone to not be able to
run the app because they're not a memeber of the right group on their desktp
when they're actually intending to manage VMs on the server.

The correct thing, as Soren mentioned earlier, is to check for memberships
of the groups when the connections to domains requiring those groups are
needed. I believe Soren already has a fix for this.

Soren can you explain to me the string freeze? I was under the impression
that bug fixes caused by, or fixable by, string changes were acceptable
during the lifetime. Otherwise how would these bugs get fixed, especially
for an LTS release like Hardy?

Thanks muchly (and sorry if it seems like I'm stalking you!)

Mike

On Fri, Apr 25, 2008 at 2:03 PM, Dustin Kirkland <email address hidden>
wrote:

> Here's one approach to solving the problem, liberally borrowed from
> MythTV.
>
> When running mythfrontend, it runs a script that checks if you're a
> member of the mythtv group, and if not, it warns you about this, and
> offers you the opportunity to enter your password, and it will try to
> use sudo to add you to the appropriate group.
>
> I'm attaching a debdiff that adds just such a script, /usr/bin/virt-
> manager-check-groups. On launching virt-manager, it will loop through
> the groups (kvm, libvirtd, vde2-net), and if the group exists, it will
> check if the current user is a member.
>
> <aside>
> The bulk of the code is trying to figure out if you're running gnome or
> kde, and finding the correct helper applications. Really, it would be nice
> if this entire script were a nice little standalone tool of its own, taking
> any group as an input.
> </aside>
>
> ** Attachment added: "virt-manager-check-groups.debdiff"
> http://launchpadlibrarian.net/13880679/virt-manager-check-groups.debdiff
>
> --
> virDomainCreateLinux() failed Timed out while reading console startup
> output
> https://bugs.launchpad.net/bugs/187048
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>