* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
@ 2023-01-01 20:04 ` classabbyamp
2023-01-01 21:06 ` realcharmer
` (17 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: classabbyamp @ 2023-01-01 20:04 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368523296
Comment:
`ls -l /var/service`? are the virt* services running?
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
2023-01-01 20:04 ` classabbyamp
@ 2023-01-01 21:06 ` realcharmer
2023-01-01 21:06 ` realcharmer
` (16 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: realcharmer @ 2023-01-01 21:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368536699
Comment:
f you are trying to use libvirt as non-root user, install `polkit` as well and and you user to the `libvirt` group and relogin or reboot. This is probably your issue judging by the error message. Also make sure you have the following services enabled and/or running:
- dbus
- libvirtd
- virtlockd
- virtlogd
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
2023-01-01 20:04 ` classabbyamp
2023-01-01 21:06 ` realcharmer
@ 2023-01-01 21:06 ` realcharmer
2023-01-01 21:06 ` realcharmer
` (15 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: realcharmer @ 2023-01-01 21:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368536699
Comment:
If you are trying to use libvirt as non-root user, install `polkit` as well and and you user to the `libvirt` group and relogin or reboot. This is probably your issue judging by the error message. Also make sure you have the following services enabled and/or running:
- dbus
- libvirtd
- virtlockd
- virtlogd
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (2 preceding siblings ...)
2023-01-01 21:06 ` realcharmer
@ 2023-01-01 21:06 ` realcharmer
2023-01-01 21:07 ` realcharmer
` (14 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: realcharmer @ 2023-01-01 21:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368536699
Comment:
If you are trying to use libvirt as non-root user, install `polkit` as well and add your user to the `libvirt` group and relogin or reboot. This is probably your issue judging by the error message. Also make sure you have the following services enabled and/or running:
- dbus
- libvirtd
- virtlockd
- virtlogd
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (3 preceding siblings ...)
2023-01-01 21:06 ` realcharmer
@ 2023-01-01 21:07 ` realcharmer
2023-01-01 22:00 ` mrtuxa
` (13 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: realcharmer @ 2023-01-01 21:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368536699
Comment:
If you are trying to use libvirt as non-root user, install `polkit` as well, add your user to the `libvirt` group and relogin or reboot. This is probably your issue judging by the error message. Also make sure you have the following services enabled and/or running:
- dbus
- libvirtd
- virtlockd
- virtlogd
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (4 preceding siblings ...)
2023-01-01 21:07 ` realcharmer
@ 2023-01-01 22:00 ` mrtuxa
2023-01-01 22:00 ` mrtuxa
` (12 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: mrtuxa @ 2023-01-01 22:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
New comment by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368544763
Comment:
> `ls -l /var/service`? are the virt* services running?
lrwxrwxrwx 1 root root 29 Dec 11 18:46 /var/service -> ../run/runit/runsvdir/current
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (5 preceding siblings ...)
2023-01-01 22:00 ` mrtuxa
@ 2023-01-01 22:00 ` mrtuxa
2023-01-01 22:05 ` classabbyamp
` (11 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: mrtuxa @ 2023-01-01 22:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
New comment by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368544849
Comment:
> If you are trying to use libvirt as non-root user, install `polkit` as well, add your user to the `libvirt` group and relogin or reboot. This is probably your issue judging by the error message. Also make sure you have the following services enabled and/or running:
>
> * dbus
> * libvirtd
> * virtlockd
> * virtlogd
how can i check if the service is running correctly
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (6 preceding siblings ...)
2023-01-01 22:00 ` mrtuxa
@ 2023-01-01 22:05 ` classabbyamp
2023-01-01 22:08 ` realcharmer
` (10 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: classabbyamp @ 2023-01-01 22:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368548597
Comment:
> > `ls -l /var/service`? are the virt* services running?
>
> lrwxrwxrwx 1 root root 29 Dec 11 18:46 /var/service -> ../run/runit/runsvdir/current
sorry, `ls -l /var/service/` (trailing slash is important)
that will show you the currently enabled services
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (7 preceding siblings ...)
2023-01-01 22:05 ` classabbyamp
@ 2023-01-01 22:08 ` realcharmer
2023-01-02 9:12 ` mrtuxa
` (9 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: realcharmer @ 2023-01-01 22:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368549445
Comment:
> how can i check if the service is running correctly
You can check status of services with `sv status`. All running services are present in `/var/service` in the form of symbolic links.
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (8 preceding siblings ...)
2023-01-01 22:08 ` realcharmer
@ 2023-01-02 9:12 ` mrtuxa
2023-01-02 9:13 ` mrtuxa
` (8 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: mrtuxa @ 2023-01-02 9:12 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
New comment by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368764199
Comment:
> ls -l /var/service/
```
[mrtuxa@mrtuxa ~]$ ls -l /var/service/
total 0
lrwxrwxrwx 1 root root 13 Oct 1 19:41 acpid -> /etc/sv/acpid
lrwxrwxrwx 1 root root 19 Oct 1 19:41 agetty-tty1 -> /etc/sv/agetty-tty1
lrwxrwxrwx 1 root root 19 Oct 1 19:41 agetty-tty2 -> /etc/sv/agetty-tty2
lrwxrwxrwx 1 root root 19 Oct 1 19:41 agetty-tty3 -> /etc/sv/agetty-tty3
lrwxrwxrwx 1 root root 19 Oct 1 19:41 agetty-tty4 -> /etc/sv/agetty-tty4
lrwxrwxrwx 1 root root 19 Oct 1 19:41 agetty-tty5 -> /etc/sv/agetty-tty5
lrwxrwxrwx 1 root root 19 Oct 1 19:41 agetty-tty6 -> /etc/sv/agetty-tty6
lrwxrwxrwx 1 root root 13 Jan 1 20:11 dbus -> /etc/sv/dbus/
lrwxrwxrwx 1 root root 14 Oct 1 19:41 dhcpcd -> /etc/sv/dhcpcd
lrwxrwxrwx 1 root root 11 Jan 2 10:07 iwd -> /etc/sv/iwd
lrwxrwxrwx 1 root root 16 Jan 1 20:49 libvirtd -> /etc/sv/libvirtd
lrwxrwxrwx 1 root root 15 Jan 1 20:08 lightdm -> /etc/sv/lightdm
lrwxrwxrwx 1 root root 12 Oct 1 19:41 sshd -> /etc/sv/sshd
lrwxrwxrwx 1 root root 13 Oct 1 19:41 udevd -> /etc/sv/udevd
lrwxrwxrwx 1 root root 17 Jan 1 20:49 virtlockd -> /etc/sv/virtlockd
lrwxrwxrwx 1 root root 16 Jan 1 20:49 virtlogd -> /etc/sv/virtlogd
lrwxrwxrwx 1 root root 22 Oct 1 19:41 wpa_supplicant -> /etc/sv/wpa_supplicant
```
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (9 preceding siblings ...)
2023-01-02 9:12 ` mrtuxa
@ 2023-01-02 9:13 ` mrtuxa
2023-01-02 9:16 ` realcharmer
` (7 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: mrtuxa @ 2023-01-02 9:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
New comment by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368765250
Comment:
> > how can i check if the service is running correctly
>
> You can check status of services with `sv status`. All running services are present in `/var/service` in the form of symbolic links.
> > how can i check if the service is running correctly
>
> You can check status of services with `sv status`. All running services are present in `/var/service` in the form of symbolic links.
```
[root@mrtuxa mrtuxa]# sv status dbus
run: dbus: (pid 861) 200s
[root@mrtuxa mrtuxa]# sv status libvirtd
run: libvirtd: (pid 866) 205s; run: log: (pid 865) 205s
[root@mrtuxa mrtuxa]# sv status virtlockd
run: virtlockd: (pid 864) 209s; run: log: (pid 863) 209s
[root@mrtuxa mrtuxa]# sv status virtlogd
run: virtlogd: (pid 880) 211s; run: log: (pid 878) 211s
```
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (10 preceding siblings ...)
2023-01-02 9:13 ` mrtuxa
@ 2023-01-02 9:16 ` realcharmer
2023-01-02 11:04 ` mrtuxa
` (6 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: realcharmer @ 2023-01-02 9:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368767584
Comment:
Well, your services are running. Is your user and group setup properly? Please, refer to the documentation at <https://docs.voidlinux.org/config/containers-and-vms/libvirt.html>.
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (11 preceding siblings ...)
2023-01-02 9:16 ` realcharmer
@ 2023-01-02 11:04 ` mrtuxa
2023-01-02 11:50 ` paper42
` (5 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: mrtuxa @ 2023-01-02 11:04 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
New comment by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368845391
Comment:
> Well, your services are running. Is your user and group setup properly? Please, refer to the documentation at https://docs.voidlinux.org/config/containers-and-vms/libvirt.html.
```
[mrtuxa@mrtuxa ~]$ groups
mrtuxa wheel floppy audio video cdrom optical kvm plugdev xbuilder
```
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (12 preceding siblings ...)
2023-01-02 11:04 ` mrtuxa
@ 2023-01-02 11:50 ` paper42
2023-01-02 13:48 ` mrtuxa
` (4 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: paper42 @ 2023-01-02 11:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368877260
Comment:
> ```
> [mrtuxa@mrtuxa ~]$ groups
> mrtuxa wheel floppy audio video cdrom optical kvm plugdev xbuilder
> ```
> However, if you have the polkit and dbus packages installed and you enable the dbus service, libvirtd will grant necessary privileges to any user added to the libvirt group.
You are not in the right group.
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (13 preceding siblings ...)
2023-01-02 11:50 ` paper42
@ 2023-01-02 13:48 ` mrtuxa
2023-01-02 13:50 ` realcharmer
` (3 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: mrtuxa @ 2023-01-02 13:48 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 512 bytes --]
New comment by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368961689
Comment:
> > ```
> > [mrtuxa@mrtuxa ~]$ groups
> > mrtuxa wheel floppy audio video cdrom optical kvm plugdev xbuilder
> > ```
>
> > However, if you have the polkit and dbus packages installed and you enable the dbus service, libvirtd will grant necessary privileges to any user added to the libvirt group.
>
> You are not in the right group.
which is the right group
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (14 preceding siblings ...)
2023-01-02 13:48 ` mrtuxa
@ 2023-01-02 13:50 ` realcharmer
2023-01-15 1:51 ` bugcrazy
` (2 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: realcharmer @ 2023-01-02 13:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368963388
Comment:
> which is the right group
I've mentioned this already. Read the documentation, it's pretty simple.
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (15 preceding siblings ...)
2023-01-02 13:50 ` realcharmer
@ 2023-01-15 1:51 ` bugcrazy
2023-04-15 1:52 ` github-actions
2023-04-29 1:52 ` [ISSUE] [CLOSED] " github-actions
18 siblings, 0 replies; 20+ messages in thread
From: bugcrazy @ 2023-01-15 1:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
New comment by bugcrazy on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1383021487
Comment:
Do you have a polkit authentication agent installed?
Example: polkit-kde-agent; mate-polkit; pantheon-agent; xfce-polkit; polkit-gnome.
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (16 preceding siblings ...)
2023-01-15 1:51 ` bugcrazy
@ 2023-04-15 1:52 ` github-actions
2023-04-29 1:52 ` [ISSUE] [CLOSED] " github-actions
18 siblings, 0 replies; 20+ messages in thread
From: github-actions @ 2023-04-15 1:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1509458612
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [ISSUE] [CLOSED] Virt-Manager Not Connected
2023-01-01 20:03 [ISSUE] Virt-Manager Not Connected mrtuxa
` (17 preceding siblings ...)
2023-04-15 1:52 ` github-actions
@ 2023-04-29 1:52 ` github-actions
18 siblings, 0 replies; 20+ messages in thread
From: github-actions @ 2023-04-29 1:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 3155 bytes --]
Closed issue by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397
Description:
### Is this a new report?
Yes
### System Info
Void 6.0.15_1 x86_64 AuthenticAMD uptodate FFF
### Package(s) Affected
virt-manager
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Run as normal
### Actual behaviour
[mrtuxa@mrtuxa ~]$ virt-manager --debug
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (cli:204) Version 4.1.0 launched with command line: /usr/bin/virt-manager --debug
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (virtmanager:167) virt-manager version: 4.1.0
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (virtmanager:168) virtManager import: /usr/share/virt-manager/virtManager
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (virtmanager:205) PyGObject version: 3.42.2
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (virtmanager:209) GTK version: 3.24.34
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (systray:476) Showing systray: False
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (inspection:206) python guestfs is not installed
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:113) Loading stored URIs:
qemu:///system
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:461) processing cli command uri= show_window=manager domain=
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:464) No cli action requested, launching default window
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (manager:185) Showing manager
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:316) window counter incremented to 1
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:211) Initial gtkapplication activated
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (connection:482) conn=qemu:///system changed to state=Connecting
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (connection:903) Scheduling background open thread for qemu:///system
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (connection:838) conn.close() uri=qemu:///system
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (connection:482) conn=qemu:///system changed to state=Disconnected
[Sun, 01 Jan 2023 21:00:38 virt-manager 2891] DEBUG (engine:179) Autostart connection error: Unable to connect to libvirt qemu:///system.
Verify that the 'libvirtd' daemon is running.
Libvirt URI is: qemu:///system
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 923, in _do_open
self._backend.open(cb, data)
File "/usr/share/virt-manager/virtinst/connection.py", line 171, in open
conn = libvirt.openAuth(self._open_uri,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/libvirt.py", line 147, in openAuth
raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
### Steps to reproduce
Search on Github and Stackoverflow and Arch Linux Wiki
^ permalink raw reply [flat|nested] 20+ messages in thread