all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Gottfried <gottfried@posteo.de>, help-guix@gnu.org
Subject: Re: virtualization
Date: Fri, 23 Sep 2022 12:53:59 -0700	[thread overview]
Message-ID: <87o7v5hnoo.fsf@contorta> (raw)
In-Reply-To: <9bd91815-48d4-18e6-8816-8a80447e4bfd@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

On 2022-09-23, gottfried@posteo.de wrote:
> I installed a VM software and I added libvirt and virtualization in my 
> config.scm file (see below)
...
>    (users (cons* (user-account
>                    (name "gfp")
>                    (comment "Gfp")
>                    (group "users")
>                    (home-directory "/home/gfp")
>                    (supplementary-groups
>                      '("wheel" "netdev" "audio" "video")))
>                  %base-user-accounts))
...
>              (service libvirt-service-type
>                       (libvirt-configuration
>                        (unix-sock-group "libvirt")
>                        (tls-port "16555"))))
...
> It seems I don't have the rights to start libvirt.
>
> How can I now solve the problem?
> Any thoughts?

I would add your user the to group you configure libvirt-service-type
with, e.g. "libvirt" ... or configure libvirt-service-type with a
different group that your user is already a part of.

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2022-09-23 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 19:12 virtualization Gottfried
2022-09-23 19:53 ` Vagrant Cascadian [this message]
2022-09-24 21:05   ` virtualization Gottfried
2022-09-25  8:06     ` virtualization Gottfried
2022-09-25  8:14       ` virtualization Chris Keschnat via

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=87o7v5hnoo.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=gottfried@posteo.de \
    --cc=help-guix@gnu.org \
    /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.