From: Catonano <catonano@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: libvirt
Date: Sun, 31 Dec 2017 18:40:45 +0100 [thread overview]
Message-ID: <CAJ98PDywsWRwY0LkJ5NsiDyiU5opQHZsKT_JLATMM8VdG9rOkg@mail.gmail.com> (raw)
In-Reply-To: <87k1x2ajfw.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
2017-12-31 18:36 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:
>
> Catonano <catonano@gmail.com> writes:
>
> > In fact, when launching virt-manager, var/run/libvirt/libvirt-sock should
> > be accessible and it's readable/writable by users in the root group,
> others
> > can't access it
> >
> > So your user needs to be in the root group too !
>
> That doesn’t seem right. This smells like a bug to me. Users shouldn’t
> ever need to be in the root group.
>
Souldn't they ?
I don't know
All I can suggest is you reproduce the issue.
Reconfigure your system with libvirt, install virt-manager in you profile,
launch your virt-manager and see what happens
[-- Attachment #2: Type: text/html, Size: 1142 bytes --]
next prev parent reply other threads:[~2017-12-31 17:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 8:03 libvirt Catonano
2017-12-12 14:56 ` libvirt Ricardo Wurmus
2017-12-12 16:46 ` libvirt Catonano
2017-12-12 17:51 ` libvirt Catonano
2017-12-12 17:59 ` libvirt Catonano
2017-12-18 18:48 ` libvirt Christopher Baines
2017-12-18 22:13 ` libvirt Catonano
2017-12-31 8:51 ` libvirt Catonano
2017-12-31 17:36 ` libvirt Ricardo Wurmus
2017-12-31 17:40 ` Catonano [this message]
2018-02-06 3:02 ` libvirt myglc2
-- strict thread matches above, loose matches on Subject: below --
2018-05-30 11:34 libvirt Catonano
2018-05-30 11:35 ` libvirt Catonano
2018-05-30 11:56 ` libvirt Catonano
2018-05-30 14:06 ` libvirt Ricardo Wurmus
2018-05-30 14:26 ` libvirt Catonano
2018-05-30 19:52 ` libvirt Ricardo Wurmus
2018-05-31 6:26 ` libvirt Catonano
2018-05-31 6:59 ` libvirt Catonano
2018-06-03 8:51 ` libvirt Christopher Baines
2018-06-04 14:45 ` libvirt Catonano
2018-06-04 19:56 ` libvirt Christopher Baines
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ98PDywsWRwY0LkJ5NsiDyiU5opQHZsKT_JLATMM8VdG9rOkg@mail.gmail.com \
--to=catonano@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.