Qemu reinstall aftter 'dnf remove'

jon-will · June 6, 2023, 6:19am

I’ll strait up: I did something dumb. I ‘dnf remove’ ed all of my QEMU and libvirt packages. I need to find a new way to get ot my vms but I keep getting

libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': Connection refused

libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': Permision denied

and even

libvirt.libvirtError: An error occurred, but the cause is unknown

I have no clue hot to fix and and no clue where to start. I’ve now hit the 4 hour mark and no progress. Any ideas?

jn64 · June 6, 2023, 6:35am

It’s not clear what you need help with.

To install QEMU/libvirt and related packages, easiest way is using the virtualization group (or virtualization-headless to exclude GUI packages like virt-manager):

sudo dnf group install virtualization

If you have issues using libvirt then please describe the exact steps/commands and full output.

jon-will · June 6, 2023, 6:38am

I did what you have suggested and still on virt manger I get

libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': Connection refused

I guess I should mension no matter how many time I run this command (because I have done so before) I can run it over and over again and it will prompt me yes or no([y/N]).

barryascott · June 6, 2023, 7:35am

Its not missing software that is the issue i think it is missing config or need to restart services.
Did you try a reboot after all the reinstalls.
That often helps clean out temp state that may need resetting.

augenauf · June 6, 2023, 11:09am

journalctl -u libvirtd.service

Did you modify /etc/libvirt/libvirtd.conf?

Did you add your user to the libvirt group? (Restart required after):

 sudo usermod -aG libvirt username

jon-will · June 6, 2023, 4:07pm

I added the user and rebooted and after going into virt-manger I get

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

as for journalctl -u libvirtd.service That looks like this

Jun 06 02:10:26 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Deactivated successfully.
Jun 06 02:10:26 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 9249 (dnsmasq) remains running after unit stopped.
Jun 06 02:10:26 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 9295 (dnsmasq) remains running after unit stopped.
Jun 06 02:10:26 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 9296 (dnsmasq) remains running after unit stopped.
Jun 06 02:10:26 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 13328 (dnsmasq) remains running after unit stopped.
Jun 06 02:10:26 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 13329 (dnsmasq) remains running after unit stopped.
Jun 06 02:10:26 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 19007 (qemu-system-x86) remains running after unit stopped.
Jun 06 02:10:26 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 19010 (kvm-nx-lpage-recovery-19007) remains running after unit stopped.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Found left-over process 9249 (dnsmasq) in control group while starting unit. Ignoring.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Found left-over process 9295 (dnsmasq) in control group while starting unit. Ignoring.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Found left-over process 9296 (dnsmasq) in control group while starting unit. Ignoring.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Found left-over process 13328 (dnsmasq) in control group while starting unit. Ignoring.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Found left-over process 13329 (dnsmasq) in control group while starting unit. Ignoring.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Found left-over process 19007 (qemu-system-x86) in control group while starting unit. Ignoring.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Found left-over process 19010 (kvm-nx-lpage-recovery-19007) in control group while starting unit. Ignoring.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: Starting libvirtd.service - Virtualization daemon...
Jun 06 02:11:58 DESKTOP-2CQB8G2.lan systemd[1]: Started libvirtd.service - Virtualization daemon.
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan dnsmasq[9295]: read /etc/hosts - 8 names
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan dnsmasq[13328]: read /etc/hosts - 12 names
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan dnsmasq[9295]: read /var/lib/libvirt/dnsmasq/default-2.addnhosts - 0 names
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan dnsmasq[13328]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan dnsmasq-dhcp[9295]: read /var/lib/libvirt/dnsmasq/default-2.hostsfile
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan dnsmasq-dhcp[13328]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan dnsmasq[9249]: read /etc/hosts - 8 names
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan dnsmasq[9249]: read /var/lib/libvirt/dnsmasq/Whonix-External.addnhosts - 0 names
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Deactivated successfully.
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 9249 (dnsmasq) remains running after unit stopped.
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 9295 (dnsmasq) remains running after unit stopped.
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 9296 (dnsmasq) remains running after unit stopped.
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 13328 (dnsmasq) remains running after unit stopped.
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 13329 (dnsmasq) remains running after unit stopped.
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 19007 (qemu-system-x86) remains running after unit stopped.
Jun 06 02:11:59 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 19010 (kvm-nx-lpage-recovery-19007) remains running after unit stopped.

augenauf · June 6, 2023, 5:57pm

systemctl status libvirtd

jon-will · June 6, 2023, 7:04pm



○ libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
TriggeredBy: ○ libvirtd-tls.socket
             ○ libvirtd-tcp.socket
             ○ libvirtd.socket
             ○ libvirtd-admin.socket
             ○ libvirtd-ro.socket
       Docs: man:libvirtd(8)
             https://libvirt.org

systemctl start libvirtd will start but then I get

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

and the status is then

○ libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Tue 2023-06-06 15:02:47 EDT; 35s ago
   Duration: 361ms
TriggeredBy: ○ libvirtd-tls.socket
             ○ libvirtd-tcp.socket
             ● libvirtd.socket
             ● libvirtd-admin.socket
             ● libvirtd-ro.socket
       Docs: man:libvirtd(8)
             https://libvirt.org
    Process: 22357 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS)
   Main PID: 22357 (code=exited, status=0/SUCCESS)
      Tasks: 5 (limit: 32768)
     Memory: 39.7M
        CPU: 306ms
     CGroup: /system.slice/libvirtd.service
             ├─22464 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/Whonix-External.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
             ├─22518 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default-2.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
             ├─22519 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default-2.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
             ├─22556 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
             └─22557 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper

Jun 06 15:02:47 DESKTOP-2CQB8G2.lan dnsmasq[22556]: using nameserver 127.0.0.53#53
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan dnsmasq[22556]: read /etc/hosts - 12 names
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan dnsmasq[22556]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan dnsmasq-dhcp[22556]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Deactivated successfully.
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 22464 (dnsmasq) remains running after unit stopped.
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 22518 (dnsmasq) remains running after unit stopped.
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 22519 (dnsmasq) remains running after unit stopped.
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 22556 (dnsmasq) remains running after unit stopped.
Jun 06 15:02:47 DESKTOP-2CQB8G2.lan systemd[1]: libvirtd.service: Unit process 22557 (dnsmasq) remains running after unit stopped.

vgaetera · June 6, 2023, 9:17pm

This is a legacy service which is no longer used or required as it was split to other virtualization service components, so you don’t need to care about it.

computersavvy · June 6, 2023, 9:29pm

jon will:

○ libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
TriggeredBy: ○ libvirtd-tls.socket
             ○ libvirtd-tcp.socket
             ○ libvirtd.socket
             ○ libvirtd-admin.socket
             ○ libvirtd-ro.socket
       Docs: man:libvirtd(8)
             https://libvirt.org

Note the several ‘TriggeredBy’ lines. That service does not need to be enabled since it is launched by one of the named sockets. The default is disabled. It also is not designed to be started manually.

jon-will · June 6, 2023, 10:47pm

OK but how do I fix this?

vekruse · June 6, 2023, 11:12pm

These units are normally enabled

    virtqemud.service           enabled
    virtinterfaced.socket       enabled
    virtnetworkd.socket         enabled
    virtnodedevd.socket         enabled
    virtnwfilterd.socket        enabled
    virtproxyd.socket           enabled
    virtsecretd.socket          enabled
    virtstoraged.socket         enabled

These units are normally disabled

    libvirt-guests.service      disabled
    libvirtd.service            disabled
    virtinterfaced.service      disabled
    virtlockd.service           disabled
    virtlogd.service            disabled
    virtnetworkd.service        disabled
    virtnodedevd.service        disabled
    virtnwfilterd.service       disabled
    virtproxyd.service          disabled
    virtsecretd.service         disabled
    virtstoraged.service        disabled
    libvirtd-admin.socket       disabled
    libvirtd-ro.socket          disabled
    libvirtd-tcp.socket         disabled
    libvirtd-tls.socket         disabled
    libvirtd.socket             disabled
    virtinterfaced-admin.socket disabled
    virtinterfaced-ro.socket    disabled
    virtlockd-admin.socket      disabled
    virtlockd.socket            disabled
    virtlogd-admin.socket       disabled
    virtlogd.socket             disabled
    virtnetworkd-admin.socket   disabled
    virtnetworkd-ro.socket      disabled
    virtnodedevd-admin.socket   disabled
    virtnodedevd-ro.socket      disabled
    virtnwfilterd-admin.socket  disabled
    virtnwfilterd-ro.socket     disabled
    virtproxyd-admin.socket     disabled
    virtproxyd-ro.socket        disabled
    virtproxyd-tcp.socket       disabled
    virtproxyd-tls.socket       disabled
    virtqemud-admin.socket      disabled
    virtqemud-ro.socket         disabled
    virtqemud.socket            disabled
    virtsecretd-admin.socket    disabled
    virtsecretd-ro.socket       disabled
    virtstoraged-admin.socket   disabled
    virtstoraged-ro.socket      disabled

These would normally be set up that way at install time.

vgaetera · June 7, 2023, 1:54am

Check the output:

systemctl status virtqemud.service virtqemud.socket
virsh -d 0 connect qemu:///session
virsh -d 0 connect qemu:///system
groups; sestatus; ls -l -Z /var/run/libvirt/virtqemud-sock
journalctl -b -g avc

jon-will · June 7, 2023, 2:19am

so I started virtqemud.service and virtqemud.socket and it kinda worked.

scratch that, not really. As I am righting this it shut down again.
here is the output of the above.

× virtqemud.service - Virtualization qemu daemon
     Loaded: loaded (/usr/lib/systemd/system/virtqemud.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: start-limit-hit) since Tue 2023-06-06 22:16:05 EDT; 3min 25s ago
   Duration: 6ms
TriggeredBy: × virtqemud.socket
             × virtqemud-ro.socket
             × virtqemud-admin.socket
       Docs: man:virtqemud(8)
             https://libvirt.org
    Process: 13753 ExecStart=/usr/sbin/virtqemud $VIRTQEMUD_ARGS (code=exited, status=0/SUCCESS)
   Main PID: 13753 (code=exited, status=0/SUCCESS)
        CPU: 18ms

Jun 06 22:16:05 DESKTOP-2CQB8G2.lan systemd[1]: Started virtqemud.service - Virtualization qemu daemon.
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan virtqemud[13753]: libvirt version: 9.0.0, package: 2.fc38 (Fedora Project, 2023-01-19-19:58:16, )
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan virtqemud[13753]: hostname: DESKTOP-2CQB8G2.lan
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan virtqemud[13753]: invalid argument: Failed to parse group 'libvirt-qemu'
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan virtqemud[13753]: Initialization of QEMU state driver failed: invalid argument: Failed to parse group 'libvirt-qemu'
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan virtqemud[13753]: Driver state initialization failed
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan systemd[1]: virtqemud.service: Deactivated successfully.
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan systemd[1]: virtqemud.service: Start request repeated too quickly.
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan systemd[1]: virtqemud.service: Failed with result 'start-limit-hit'.
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan systemd[1]: Failed to start virtqemud.service - Virtualization qemu daemon.

× virtqemud.socket - Libvirt qemu local socket
     Loaded: loaded (/usr/lib/systemd/system/virtqemud.socket; enabled; preset: disabled)
     Active: failed (Result: service-start-limit-hit) since Tue 2023-06-06 22:16:05 EDT; 3min 25s ago
   Duration: 31.450s
   Triggers: ● virtqemud.service
     Listen: /run/libvirt/virtqemud-sock (Stream)

Jun 06 22:15:34 DESKTOP-2CQB8G2.lan systemd[1]: Listening on virtqemud.socket - Libvirt qemu local socket.
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan systemd[1]: virtqemud.socket: Failed with result 'service-start-limit-hit'.
connect: name(optdata): qemu:///session

connect: name(optdata): qemu:///system
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory

jon wheel cdrom kvm input docker libvirt nobody
SELinux status:                 disabled
ls: cannot access '/var/run/libvirt/virtqemud-sock': No such file or directory
-- No entries --

jon-will · June 7, 2023, 2:21am

and here is what the out put of virt manger when it “worked”

Unable to connect to libvirt qemu:///system.

Cannot recv data: Connection reset by peer

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/lib64/python3.11/site-packages/libvirt.py", line 147, in openAuth
    raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Cannot recv data: Connection reset by peer

vgaetera · June 7, 2023, 3:16am

jon will:

Jun 06 22:16:05 DESKTOP-2CQB8G2.lan virtqemud[13753]: invalid argument: Failed to parse group 'libvirt-qemu'
Jun 06 22:16:05 DESKTOP-2CQB8G2.lan virtqemud[13753]: Initialization of QEMU state driver failed: invalid argument: Failed to parse group 'libvirt-qemu'

It shouldn’t be like that on Fedora:

github.com

libvirt/libvirt/blob/master/meson.build#L1635-L1656


      
            qemu_moddir = libdir / 'qemu'
          endif
          conf.set_quoted('QEMU_MODDIR', qemu_moddir)
          
          qemu_datadir = get_option('qemu_datadir')
          if qemu_datadir == ''
            qemu_datadir = datadir / 'qemu'
          endif
          conf.set_quoted('QEMU_DATADIR', qemu_datadir)
          
          qemu_user = get_option('qemu_user')
          qemu_group = get_option('qemu_group')
          if (qemu_user == '' and qemu_group != '') or (qemu_user != '' and qemu_group == '')
            error('Please specify both qemu_user and qemu_group or neither of them')
          endif
          if qemu_user == '' and qemu_group == ''
            if host_machine.system() in [ 'freebsd', 'darwin' ]
              qemu_user = 'root'
              qemu_group = 'wheel'
            else

This file has been truncated. show original

But you can still specify the proper group name in the config:

github.com

libvirt/libvirt/blob/master/src/qemu/qemu.conf.in#L521-L523


      
          # The group for QEMU processes run by the system instance. It can be
          # specified in a similar way to user.
          #group = "@QEMU_GROUP@"

This also doesn’t look good.
I had issues trying to use libvirt with disabled SELinux in the past.

jon-will · June 7, 2023, 3:17am

I have made a tests. I can restart virtqemud.service and virtqemud.socket as meany times as I want and it will “work” giving me the cannot access but then I get the Cannot recv data error

jon-will · June 7, 2023, 3:32am

How would I go about enabling it? I tred so many times that I just can not enable it

vekruse · June 7, 2023, 5:28am

As root run


systemctl disable libvirt-guests.service libvirtd.service virtinterfaced.service virtlockd.service
systemctl disable libvirtd-admin.socket libvirtd-ro.socket libvirtd-tcp.socket libvirtd-tls.socket libvirtd.socket
systemctl disable virtinterfaced-admin.socket virtinterfaced-ro.socket virtlockd-admin.socket virtlogd-admin.socket virtnetworkd-admin.socket
systemctl disable virtlogd.service virtnetworkd.service virtnodedevd.service virtnwfilterd.service
systemctl disable virtnetworkd-ro.socket virtnodedevd-admin.socket virtnodedevd-ro.socket virtnwfilterd-admin.socket virtnwfilterd-ro.socket
systemctl disable virtproxyd-admin.socket virtproxyd-ro.socket virtproxyd-tcp.socket virtproxyd-tls.socket virtsecretd-admin.socket
systemctl disable virtproxyd.service virtsecretd.service virtstoraged.service
systemctl disable virtsecretd-ro.socket virtstoraged-admin.socket virtstoraged-ro.socket


systemctl enable virtinterfaced.socket virtlockd.socket virtlogd.socket virtnetworkd.socket virtnodedevd.socket virtnwfilterd.socket
systemctl enable virtproxyd.socket virtqemud-admin.socket virtqemud-ro.socket virtqemud.socket virtsecretd.socket virtstoraged.socket
systemctl enable virtqemud.service

Reboot (or stop the disable units and start the enabled units)

jon-will · June 7, 2023, 6:07am

sorry but did not work

Topic		Replies	Views
Virt-manager not connecting to Qemu Ask Fedora f38	10	3810	November 13, 2023
Virt Manager in Fedora Silverblue: "Failed to connect socket to '/var/run/libvirt/virtstoraged-sock': No such file or directory" Ask Fedora virt-manager , libvirt , virtualization , silverblue	4	818	August 3, 2024
Problems with libvirt/virt-manager Ask Fedora f38 , virt-manager , libvirt	9	3177	May 18, 2023
Virt-manager/kvm failed to read iso images - Permission denied Ask Fedora f38 , virt-manager , libvirt , silverblue	5	2246	May 21, 2023
Libvirt unable to connect to qemu after connecting successfuly once Ask Fedora	2	1378	June 16, 2023

Qemu reinstall aftter 'dnf remove'

Related topics