Libvirt not connecting

[eriefisher]

Seems that recent updates has broken libvirt/virt-manager. I only use this vm occasionally so I don't know when it started exactly.

Code Auswählen Erweitern

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

internal error: client socket is closed

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 932, in _do_open
    self._backend.open(cb, data)
    ~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/share/virt-manager/virtinst/connection.py", line 184, in open
    self._get_caps()  # cache and log capabilities
    ~~~~~~~~~~~~~~^^
  File "/usr/share/virt-manager/virtinst/connection.py", line 107, in _get_caps
    capsxml = self._libvirtconn.getCapabilities()
  File "/usr/lib/python3/dist-packages/libvirt.py", line 4699, in getCapabilities
    raise libvirtError('virConnectGetCapabilities() failed')
libvirt.libvirtError: internal error: client socket is closed

[dibl]

I use virt-manager on siduction daily and have seen no issues, up to and including this morning (29 AUG).

[eriefisher]

Interesting. I assume your current and up to date? Like I said, this was a recent occurrence. I used the VM 4-5 days ago with no issue and just this morning I get the errors. I did notice there were several virt updates the last few days. I'll need to dig in more.

[dibl]

I ran updates at 4:30 a.m. EDT (USA) this morning.  Now I'm afraid to run them again LOL.

[hsp]

I have the same problem, but no solution.
...

[dibl]

For what it's worth:

Code Auswählen Erweitern

libvirt-common:
  Installed: 11.3.0-3+b1
  Candidate: 11.3.0-3+b1
  Version table:
*** 11.3.0-3+b1 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
virt-manager:
  Installed: 1:5.0.0-5
  Candidate: 1:5.0.0-5
  Version table:
*** 1:5.0.0-5 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Code Auswählen Erweitern

System:
  Host: Hibiscus Kernel: 6.16.3-2-siduction-amd64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.3.6 Distro: siduction 22.1.2 Masters_of_War -
    kde - (202303151559)
CPU:
  Info: quad core model: Intel Core i7-4770 bits: 64 type: MT MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 800 min/max: 800/3900 cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800

[hsp]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112481

[hsp]

I have found a workaround:
If you don't need qemu-system-sparc and qemu-system-alpha, you can use the following workaround for now.

Code Auswählen Erweitern

apt purge qemu-system-misc qemu-system-sparc

....

[eriefisher]

I have found a workaround:
If you don't need qemu-system-sparc and qemu-system-alpha, you can use the following workaround for now.

Code Auswählen Erweitern

apt purge qemu-system-misc qemu-system-sparc

....

I didn't have qemu-system-sparc installed but qemu-system-misc was removed and seem to have done the trick. I just booted up the vm with no errors.

Thanks

[dibl]

Yep, I had neither of those files installed -- that is why the evil angel of update destruction passed by my house. LOL

[eriefisher]

Yep, I had neither of those files installed -- that is why the evil angel of update destruction passed by my house. LOL

Whew!

Interesting though, if they were not required to run the vm why would they cause trouble? At least it's working again.