all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ruijie Yu via <help-guix@gnu.org>
To: Robby Zambito <contact@robbyzambito.me>
Cc: help-guix@gnu.org
Subject: Re: Cannot run virt-manager as my user
Date: Mon, 29 May 2023 12:40:33 +0800	[thread overview]
Message-ID: <87597D5E-2441-4A09-A287-EE7AC11C7DBC@netyu.xyz> (raw)
In-Reply-To: <87a5xndf9t.fsf@robbyzambito.me>

On May 29, 2023, at 10:49, Robby Zambito <contact@robbyzambito.me> wrote:
> 
> Hi,
> 
> I am trying to set up virt-manager on my system in order to set up some
> virtual machines. I added the libvirtd service to my system by adding
> the following service to my system configuration:
> 
> ```
> (service libvirt-service-type)
> ```
> 
> and I've added myself to the libvirt group.
> 
> I can see the service running when I do:
> 
> ```
> robby@lambda ~$ sudo herd status libvirtd
> Status of libvirtd:
>  It is running since 10:34:29 PM (5 minutes ago).
>  Running value is 256.
>  It is enabled.
>  Provides (libvirtd).
>  Requires ().
>  Will be respawned.
> ```
> 
> I can see the libvirt-sock file that I should be able to use:
> 
> ```
> robby@lambda ~$ groups
> users libvirt netdev audio video dialout wheel
> robby@lambda ~$ ll /var/run/libvirt/libvirt-sock
> srwxrwx--- 1 root libvirt 0 May 28 22:34 /var/run/libvirt/libvirt-sock
> ```
> 
> But I cannot use virt-manager or virsh as my user. I see the following
> behavior using virsh:
> 
> ```
> robby@lambda ~$ virsh -c qemu:///system
> error: failed to connect to the hypervisor
> error: internal error: Unable to get system bus connection: Could not connect: No such file or directory
> robby@lambda ~$ sudo virsh -c qemu:///system
> Welcome to virsh, the virtualization interactive terminal.
> 
> Type:  'help' for help with commands
>       'quit' to quit
> 
> virsh #
> ```
> 
> So I can use virsh while running as root - but I should also be able to
> use it when running as my user...
> 
> When I try to connect using virt-manager, I see the following similar error:
> 
> ```
> Unable to connect to libvirt qemu:///system.
> 
> internal error: Unable to get system bus connection: Could not connect: No such file or directory
> 
> Libvirt URI is: qemu:///system
> 
> Traceback (most recent call last):
>  File "/gnu/store/sa4wwfmvlrry69gyilhb961gpbbamayf-virt-manager-4.1.0/share/virt-manager/virtManager/connection.py", line 923, in _do_open
>    self._backend.open(cb, data)
>  File "/gnu/store/sa4wwfmvlrry69gyilhb961gpbbamayf-virt-manager-4.1.0/share/virt-manager/virtinst/connection.py", line 171, in open
>    conn = libvirt.openAuth(self._open_uri,
>  File "/gnu/store/nb6yaafwa44jqfg9s5fbr5nbsa46panm-python-libvirt-8.6.0/lib/python3.10/site-packages/libvirt.py", line 147, in openAuth
>    raise libvirtError('virConnectOpenAuth() failed')
> libvirt.libvirtError: internal error: Unable to get system bus
>  connection: Could not connect: No such file or directory
> ```
> 
> Since this seems to be an issue relating to dbus, here are the following
> services I have running related to that:
> 
> At a system level:
> ```
> (service dbus-root-service-type)
> (service elogind-service-type)
> ```
> 
> As my user:
> ```
> (service home-dbus-service-type)
> ```
> 
> Maybe there is some conflict between running dbus as my user and as
> root?
> 
> Any advice for getting virt-manager working would be greatly
> appreciated!
> 
> Thanks,
> Robby
> 

Does it work on a new tty, or if you explicitly run `sg libvirt …`?  If so, the only thing you need is a new terminal window with you on the libvirt group.  If that doesn’t work, try rebooting as well. 


  reply	other threads:[~2023-05-29 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29  2:35 Cannot run virt-manager as my user Robby Zambito
2023-05-29  4:40 ` Ruijie Yu via [this message]
2023-05-29 13:14   ` Robby Zambito
2023-05-29 15:01     ` David Conner
2023-05-29 17:06       ` Robby Zambito

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=87597D5E-2441-4A09-A287-EE7AC11C7DBC@netyu.xyz \
    --to=help-guix@gnu.org \
    --cc=contact@robbyzambito.me \
    --cc=ruijie@netyu.xyz \
    /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.