Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid

ziomario · Aug 27, 2023

I'm connected to my ARM Chromebook via ssh with this command :

Code:

ssh -Y [email protected]

and I run virt-manager from ssh (via Xorg forwarding). I have also tried to run it directly from the netbook,but I get the same error.

z7vl7abxc · Aug 27, 2023

if your version of debian uses systemd (mx does not by default), you could try checking systemctl status 'libvirtd*'

without formatting, the command is systemctl. with formatting the lowercase L's looks like 1's. so without formatting:

systemctl status 'libvirtd*'

i've not used ssh so can't help if that is part of the issue.

ziomario · Aug 27, 2023

Code:

marietto@chromarietto:~$ sudo systemctl status libvirtd



○ libvirtd.service - Virtualization daemon

Loaded: loaded (/usr/local/lib/systemd/system/libvirtd.service; disabled; preset: enabled)

Active: inactive (dead)

TriggeredBy: ○ libvirtd-ro.socket

○ libvirtd.socket

○ libvirtd-admin.socket

Docs: man:libvirtd(8)

https://libvirt.org


marietto@chromarietto:~$ ps ax | grep libvirt

2858 ?        Sl     0:00 libvirtd -d

ziomario · Aug 27, 2023

Shoud I kill process 2858 before to start libvirtd.service ?

z7vl7abxc · Aug 27, 2023

i would.

z7vl7abxc · Aug 27, 2023

regarding the sockets:

Code:

ls -l /run/libvirt/
total 0
drwxr-xr-x 2 root root  40 Aug 26 10:14 hostdevmgr/
drwx------ 2 root root  60 Aug 26 10:14 interface/
srwx------ 1 root root   0 Aug 26 10:14 libvirt-admin-sock=
srwxrwxrwx 1 root root   0 Aug 26 10:14 libvirt-sock=
srwxrwxrwx 1 root root   0 Aug 26 10:14 libvirt-sock-ro=
drwxr-xr-x 3 root root 160 Aug 26 10:14 network/
drwx------ 2 root root  60 Aug 26 10:14 nodedev/
drwx------ 2 root root  60 Aug 26 10:14 nwfilter/
drwx------ 2 root root  40 Aug 26 10:14 nwfilter-binding/
drwxr-xr-x 4 root root 120 Aug 26 10:14 qemu/
drwx------ 2 root root  60 Aug 26 10:14 secrets/
drwxr-xr-x 2 root root  80 Aug 26 10:14 storage/
srwx------ 1 root root   0 Aug 26 10:14 virtlogd-admin-sock=
srwx------ 1 root root   0 Aug 26 10:14 virtlogd-sock=

ziomario · Aug 27, 2023

marietto@chromarietto:~$ sudo kill -9 2858

marietto@chromarietto:~$ sudo systemctl start libvirtd

marietto@chromarietto:~$ sudo systemctl status libvirtd
● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/local/lib/systemd/system/libvirtd.service; disabled; preset: enabled)
Active: active (running) since Sun 2023-08-27 18:20:07 UTC; 5s ago
TriggeredBy: ● libvirtd-ro.socket
● libvirtd.socket
● libvirtd-admin.socket
Docs: man:libvirtd(8)
https://libvirt.org
Main PID: 3301 (libvirtd)
Tasks: 19 (limit: 32768)
Memory: 6.6M
CPU: 616ms
CGroup: /system.slice/libvirtd.service
└─3301 /usr/local/sbin/libvirtd --timeout 120

marietto@chromarietto:~$ virt-manager

same error as before :

Code:

libvirt.libvirtError: error from service: GDBus.Error:org.freedesktop.PolicyKit1.
Error.Failed: Action org.libvirt.unix.manage is not registered

ziomario · Aug 27, 2023

marietto@chromarietto:~$ ls -l /var/local/run/libvirt

total 52
drwxr-sr-x 2 root staff 4096 Aug 25 13:32 common
drwxr-sr-x 2 root staff 4096 Aug 25 23:00 hostdevmgr
drwxr-sr-x 2 root staff 4096 Aug 27 18:22 interface
srw------- 1 root staff 0 Aug 27 18:20 libvirt-admin-sock
srw-rw-rw- 1 root staff 0 Aug 27 18:20 libvirt-sock
srw-rw-rw- 1 root staff 0 Aug 27 18:20 libvirt-sock-ro
drwxr-sr-x 2 root staff 4096 Aug 25 11:10 libxl
drwxr-sr-x 2 root staff 4096 Aug 25 11:10 lockd
drwxr-sr-x 2 root staff 4096 Aug 27 18:22 lxc
drwxr-sr-x 2 root staff 4096 Aug 27 18:22 network
drwxr-sr-x 2 root staff 4096 Aug 27 18:22 nodedev
drwxr-sr-x 2 root staff 4096 Aug 27 18:22 nwfilter
drwxr-sr-x 2 root staff 4096 Aug 25 11:10 nwfilter-binding
drwxr-sr-x 7 libvirt-qemu libvirt-qemu 4096 Aug 27 18:22 qemu
drwxr-sr-x 2 root staff 4096 Aug 27 18:22 secrets
drwxr-sr-x 2 root staff 4096 Aug 27 18:22 storage
srw------- 1 root staff 0 Aug 27 15:30 virtlockd-sock
srw------- 1 root staff 0 Aug 27 15:30 virtlogd-sock
srw------- 1 root staff 0 Aug 27 15:30 virtqemud-admin-sock
srw-rw-rw- 1 root staff 0 Aug 27 15:30 virtqemud-sock-ro

z7vl7abxc · Aug 27, 2023

have you enabled libvirtd so that it autostarts at boot and then restarted to see if that makes any difference?

in regards to your sockets list, i find it interesting that the group is staff but am not sure what difference that would or would not make. it shows virtqemud sockets. i don't know that they would or would not interfere. perhaps the reboot would clear them and help to check that? the last thing that i see is that i have mx and linux mint both set up to run virt-manager successfully. both have a

Code:

srwx------ 1 root root   0 Aug 26 10:14 virtlogd-admin-sock=

in addition to the regular virtlogd-sock.

my suggestion is to enable libvirtd to autostart. restart and see if it works any better. if not, i would possibly check
systemctl status 'virtlogd*'

with the 's and * so you can see the status of the socket as well.

ziomario · Aug 27, 2023

How can I make libvirtd to autostart ?

z7vl7abxc · Aug 27, 2023

i believe you do that with the systemctl enable command

sudo systemctl enable libvirtd

ziomario · Aug 27, 2023

When I reboot the netbook,libvirtd is changed to inactive even if,before to reboot,I have enabled it.

Code:

marietto@chromarietto:~$ sudo systemctl status libvirtd
[sudo] password for marietto: 
○ libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/local/lib/systemd/system/libvirtd.service; disabled; preset: enabled)
     Active: inactive (dead)
TriggeredBy: ○ libvirtd.socket
             ○ libvirtd-admin.socket
             ○ libvirtd-ro.socket
       Docs: man:libvirtd(8)
             https://libvirt.org

marietto@chromarietto:~$ sudo systemctl status 'virtlogd*'

● virtlogd.socket - Virtual machine log manager socket
Loaded: loaded (/usr/local/lib/systemd/system/virtlogd.socket; disabled; preset: enabled)
Active: active (listening) since Sun 2023-08-27 19:17:21 UTC; 8min ago
   Triggers: ● virtlogd.service
     Listen: /var/local/run/libvirt/virtlogd-sock (Stream)
     CGroup: /system.slice/virtlogd.socket

Aug 27 19:17:21 chromarietto systemd[1]: Listening on virtlogd.socket - Virtual machine log manager socket.

ziomario · Aug 27, 2023

Code:

sudo usermod -a -G staff marietto
sudo usermod -a -G staff root
sudo usermod -a -G staff linux
sudo newgrp staff

marietto@chromarietto:~$ sudo systemctl start libvirtd
 
marietto@chromarietto:~$ sudo systemctl status libvirtd

● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/local/lib/systemd/system/libvirtd.service; disabled; preset: enabled)
Active: active (running) since Sun 2023-08-27 19:28:41 UTC; 2s ago
TriggeredBy: ● libvirtd.socket
● libvirtd-admin.socket
● libvirtd-ro.socket
       Docs: man:libvirtd(8)
             https://libvirt.org
   Main PID: 1678 (libvirtd)
      Tasks: 19 (limit: 32768)
     Memory: 22.5M
        CPU: 832ms
     CGroup: /system.slice/libvirtd.service
└─1678 /usr/local/sbin/libvirtd --timeout 120

marietto@chromarietto:~$ ls -l /var/local/run/libvirt

total 52
drwxr-sr-x 2 root staff 4096 Aug 25 13:32 common
drwxr-sr-x 2 root staff 4096 Aug 25 23:00 hostdevmgr
drwxr-sr-x 2 root staff 4096 Aug 27 19:28 interface
srw------- 1 root staff 0 Aug 27 19:28 libvirt-admin-sock
srw-rw-rw- 1 root staff 0 Aug 27 19:28 libvirt-sock
srw-rw-rw- 1 root staff 0 Aug 27 19:28 libvirt-sock-ro
drwxr-sr-x 2 root staff 4096 Aug 25 11:10 libxl
drwxr-sr-x 2 root staff 4096 Aug 25 11:10 lockd
drwxr-sr-x 2 root staff 4096 Aug 27 19:28 lxc
drwxr-sr-x 2 root staff 4096 Aug 27 19:28 network
drwxr-sr-x 2 root staff 4096 Aug 27 19:28 nodedev
drwxr-sr-x 2 root staff 4096 Aug 27 19:28 nwfilter
drwxr-sr-x 2 root staff 4096 Aug 25 11:10 nwfilter-binding
drwxr-sr-x 7 libvirt-qemu libvirt-qemu 4096 Aug 27 19:28 qemu
drwxr-sr-x 2 root staff 4096 Aug 27 19:28 secrets
drwxr-sr-x 2 root staff 4096 Aug 27 19:28 storage
srw------- 1 root staff 0 Aug 27 19:17 virtlockd-sock
srw------- 1 root staff 0 Aug 27 19:17 virtlogd-sock
srw------- 1 root staff 0 Aug 27 19:17 virtqemud-admin-sock
srw-rw-rw- 1 root staff 0 Aug 27 19:17 virtqemud-sock
srw-rw-rw- 1 root staff 0 Aug 27 19:17 virtqemud-sock-ro

marietto@chromarietto:~$ virt-manager

same error.

ziomario · Aug 27, 2023

Can you give a look at this ?

virsh list throw error 'Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory'

I have built the latest libvirt repo. But I am unable to connect to libvirtd using virsh command in Ubuntu 22.04. I think it is trying to connect to Modular driver daemons instead of monolithic lib...

unix.stackexchange.com

I'm not sure if it can help me or not.

ziomario · Aug 27, 2023

I'm talking about to put here :

/usr/local/etc/libvirt/libvirt.conf

the parameter mode = "legacy"

/usr/local/etc/libvirt/libvirt.conf

the parameter : mode = "legacy"

z7vl7abxc · Aug 27, 2023

have you ever gotten that specific error?

Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory

z7vl7abxc · Aug 27, 2023

it may be a bit much to look through, but you could check

sudo journalctl -b | grep -i livbirt

to see all system journal messages about libvirt. that may help explain why it won't autostart as well as show any other errors that may not have been seen yet.

ziomario · Aug 27, 2023

yes,I get it when I do the following :

marietto@chromarietto:~/Desktop/Dati/new/libvirt/build$ systemctl start virtqemud

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to start 'virtqemud.service'.
Multiple identities can be used for authentication:
1. linux
2. mario,,, (marietto)
Choose identity to authenticate as (1-2): 2
Password:
==== AUTHENTICATION COMPLETE ====

marietto@chromarietto:~/Desktop/Dati/new/libvirt/build$ systemctl enable virtqemud

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ====
Authentication is required to manage system service or unit files.
Multiple identities can be used for authentication:
1. linux
2. mario,,, (marietto)
Choose identity to authenticate as (1-2): 2
Password:
==== AUTHENTICATION COMPLETE ====

marietto@chromarietto:~/Desktop/Dati/new/libvirt/build$ ls /var/local/run/libvirt/virtqemud-sock
/var/local/run/libvirt/virtqemud-sock

but when I launch virt-manager :

marietto@chromarietto:~/Desktop/Dati/new/libvirt/build$ /usr/local/bin/./virt-manager

It tries to connect,but it gets disconnected after a couple of seconds and the error "Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory' is shown again.

In addition,virtqemud-sock is deleted :

marietto@chromarietto:~/Desktop/Dati/new/libvirt/build$ ls /var/local/run/libvirt/virtqemud-sock
ls: cannot access '/var/local/run/libvirt/virtqemud-sock': No such file or directory

ziomario · Aug 27, 2023

Code:

root@chromarietto:/home/marietto# sudo journalctl -b | grep -i libvirt

Aug 27 19:17:21 chromarietto systemd[1]: Listening on virtqemud.socket - Libvirt qemu local socket.

Aug 27 19:17:21 chromarietto systemd[1]: Listening on virtqemud-admin.socket - Libvirt qemu admin socket.

Aug 27 19:17:21 chromarietto systemd[1]: Listening on virtqemud-ro.socket - Libvirt qemu local read-only socket.

Aug 27 19:22:57 chromarietto sudo[1641]: marietto : TTY=pts/0 ; PWD=/home/marietto ; USER=root ; COMMAND=/usr/bin/systemctl status libvirtd

Aug 27 19:28:39 chromarietto sudo[1670]: marietto : TTY=pts/0 ; PWD=/home/marietto ; USER=root ; COMMAND=/usr/bin/systemctl start libvirtd

Aug 27 19:28:40 chromarietto systemd[1]: Listening on libvirtd.socket - Libvirt local socket.

Aug 27 19:28:40 chromarietto systemd[1]: Listening on libvirtd-admin.socket - Libvirt admin socket.

Aug 27 19:28:40 chromarietto systemd[1]: Listening on libvirtd-ro.socket - Libvirt local read-only socket.

Aug 27 19:28:40 chromarietto systemd[1]: Starting libvirtd.service - Virtualization daemon...

Aug 27 19:28:41 chromarietto systemd[1]: Started libvirtd.service - Virtualization daemon.

Aug 27 19:28:43 chromarietto sudo[1711]: marietto : TTY=pts/0 ; PWD=/home/marietto ; USER=root ; COMMAND=/usr/bin/systemctl status libvirtd

Aug 27 19:29:08 chromarietto systemd[1]: Stopping libvirtd.service - Virtualization daemon...

Aug 27 19:29:08 chromarietto systemd[1]: libvirtd.service: Deactivated successfully.

Aug 27 19:29:08 chromarietto systemd[1]: Stopped libvirtd.service - Virtualization daemon.

Aug 27 19:29:08 chromarietto virtqemud[1756]: libvirt version: 9.7.0

Aug 27 19:29:08 chromarietto virtqemud[1756]: error from service: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.libvirt.unix.manage is not registered

Aug 27 19:29:12 chromarietto virtqemud[1756]: error from service: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.libvirt.unix.manage is not registered

z7vl7abxc · Aug 27, 2023

ziomario said:
yes,I get it when I do the following :

marietto@chromarietto:~/Desktop/Dati/new/libvirt/build$ systemctl start virtqemud

then we have circled back around to one of my initial questions. do you know what virtqemud is used for? is it a requirement for your version of libvirtd?

i'll get to the journal messages momentarily. before that, can you check

systemctl cat libvirtd.service

that should hopefully show what it needs to run correctly. it may help to maximize the terminal window just to try to make sure all lines are shown to the end. when you get to a place where the bottom says something like "Lines 1-26", hit the space bar. when one of those last lines says (END) at the end, you should be able to press the Q key to get back to a regular prompt.

Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid

Member

Well-Known Member

Member

Member

Well-Known Member

Well-Known Member

Member

Member

Well-Known Member

Member

Well-Known Member

Member

Member

Member

Member

Well-Known Member

Well-Known Member

Member

Member

Well-Known Member