View previous topic :: View next topic |
Author |
Message |
Pietrog Tux's lil' helper
Joined: 03 Jul 2021 Posts: 125 Location: Italy
|
Posted: Wed Jan 12, 2022 5:58 pm Post subject: [SOLVED] Virt Manager unable to connect to QEMU |
|
|
Hi all,
I wanted to try kvm and virt-manager for the first time so I grubbed a cup of tea, opened the wiki and installed everything.
The problem come out when I start virt-manager, I get an error "Unable to connect to libvirt", this is the extended version:
Code: | Unable to connect to libvirt qemu:///system.
Failed to connect socket to '/var/run/libvirt/virtqemud-sock': File o directory non esistente
Libvirt URI is: qemu:///system
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 922, in _do_open
self._backend.open(cb, data)
File "/usr/share/virt-manager/virtinst/connection.py", line 153, in open
conn = libvirt.openAuth(self._open_uri,
File "/usr/lib/python3.9/site-packages/libvirt.py", line 148, in openAuth
raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': File o directory non esistente |
"File o directory non esistente" is the Italian equivalent to "file or directory doesn't exist".
Any ideas of where I might have slipped?
Thank you :)
Last edited by Pietrog on Thu Jan 13, 2022 11:54 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Wed Jan 12, 2022 6:00 pm Post subject: |
|
|
Pietrog,
Did you start the libvirtd service? _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
alamahant Advocate
Joined: 23 Mar 2019 Posts: 3879
|
Posted: Wed Jan 12, 2022 6:02 pm Post subject: |
|
|
Try
Code: |
usermod -aG libvirt <your-user>
|
in addition to Neddy's advice. _________________
|
|
Back to top |
|
|
Pietrog Tux's lil' helper
Joined: 03 Jul 2021 Posts: 125 Location: Italy
|
Posted: Wed Jan 12, 2022 6:06 pm Post subject: |
|
|
NeddySeagoon wrote: | Pietrog,
Did you start the libvirtd service? |
I start it manually with rc-service libvirtd start.
Can I add it to a the default runlevel to autostart it? |
|
Back to top |
|
|
Pietrog Tux's lil' helper
Joined: 03 Jul 2021 Posts: 125 Location: Italy
|
Posted: Wed Jan 12, 2022 6:11 pm Post subject: |
|
|
alamahant wrote: | Try
Code: |
usermod -aG libvirt <your-user>
|
in addition to Neddy's advice. |
If I recall correctly I've already added my user to the libvirt group, I'll check it when I'm at the pc again. |
|
Back to top |
|
|
Pietrog Tux's lil' helper
Joined: 03 Jul 2021 Posts: 125 Location: Italy
|
Posted: Thu Jan 13, 2022 11:53 pm Post subject: |
|
|
After rebooting and logging back in it works now, probably I didn't refresh something, rookie mistake.
Thank you all. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21630
|
Posted: Sat Jan 15, 2022 6:12 pm Post subject: |
|
|
Group membership is a per-process attribute. If you added your user account to the group, newly created login sessions would have the group. Shells that you started before the change would not have it. Rebooting forced you to close all your old shells, and all the new shells would pick up your change. |
|
Back to top |
|
|
|