From: Gottfried <gottfried@posteo.de>
To: Vagrant Cascadian <vagrant@debian.org>, help-guix@gnu.org
Subject: Re: virtualization
Date: Sun, 25 Sep 2022 08:06:06 +0000 [thread overview]
Message-ID: <15d14aff-2668-0dad-ceb6-5117fa79547e@posteo.de> (raw)
In-Reply-To: <6e7dac7f-4773-2035-b09a-0b49ba614438@posteo.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 1871 bytes --]
Am 24.09.22 um 23:05 schrieb Gottfried:
> Am 23.09.22 um 21:53 schrieb Vagrant Cascadian:
>> 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
>
> Hi,
> I added my user to the group "libvirt", but it didn't help. It gives the
> same error message.
> May be something else?
> Gottfried
Hi,
it is very strange.
I added my user"gfp" to the group "libvirt" and checked it yesterday,
and I was added into that group.
It was through the command:
sudo usermod -a -G libvirt gfp
But today, when I checked it again,
I was not in the group "libvirt"
How can that be?
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-09-25 8:06 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 ` virtualization Vagrant Cascadian
2022-09-24 21:05 ` virtualization Gottfried
2022-09-25 8:06 ` Gottfried [this message]
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
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=15d14aff-2668-0dad-ceb6-5117fa79547e@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=vagrant@debian.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.
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).