unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: calcium <calcium@disroot.org>
Cc: 34611@debbugs.gnu.org, "brettg@posteo.net" <brettg@posteo.net>,
	Efraim Flashner <efraim@flashner.co.il>
Subject: bug#34611: virt-manager is not recognizing libvirtd service
Date: Fri, 29 Dec 2023 23:12:36 -0500	[thread overview]
Message-ID: <875y0gs4zv.fsf@gmail.com> (raw)
In-Reply-To: <541b1f8b-72b1-26ae-ce1d-49ed7b97cb95@disroot.org> (calcium@disroot.org's message of "Wed, 5 Jan 2022 19:42:30 +0100")

Hello,

calcium <calcium@disroot.org> writes:

> Same problem still present as of start of 2022. Virt-manager can't connect to libvirt service
>
>
> ...
>
> (users ...
>        (supplementary-groups '("kvm" ...)
>        ...)
>
>
> (services ...
>           (service libvirt-service-type (libvirt-configuartion (unix-sock-group "kvm")))
>           ...)
>
> ...

Does it work when you run virt-manager as root?  My configuration looks
like:

--8<---------------cut here---------------start------------->8---
(users ...
       (supplementary-groups '("libvirt" ...))
       ...)

[...]

(services ...)
          (service libvirt-service-type
                   (libvirt-configuration
                    (unix-sock-group "libvirt")))
--8<---------------cut here---------------end--------------->8---

And virt-manager is able to connect as my unprivileged user.

-- 
Thanks,
Maxim




  reply	other threads:[~2023-12-30  4:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22  5:06 bug#34611: virt-manager is not recognizing libvirtd service Brett Gilio
2019-02-22 22:57 ` brettg
2019-03-30 19:46 ` Efraim Flashner
2022-01-05 18:42 ` calcium via Bug reports for GNU Guix
2023-12-30  4:12   ` Maxim Cournoyer [this message]
2023-12-30  5:30   ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875y0gs4zv.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=34611@debbugs.gnu.org \
    --cc=brettg@posteo.net \
    --cc=calcium@disroot.org \
    --cc=efraim@flashner.co.il \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).