Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #270045

virt-manager: Cannot recv data: Connection reset by peer

Show all headers | View raw

Context: I am on sid, so random breakage is expected. This time it happened
somewhere between virt-manager and KVM, and I got stuck as I don't know much
about KVM and emulation general.

I have been using virt-manager to manage virtual machine with QEMU/KVM user
session for some months without any issue. From monday the session is "Not
Connected" and when I try to connect I get the following message:

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

	Cannot recv data: Connection reset by peer

and Details:

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

	Cannot recv data: Connection reset by peer

	Libvirt URI is: qemu:///session

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

I supposed something happened when I upgraded my (host) machine with aptitude
full-upgrade, and in fact aptitude logs include the following:

    [UPGRADE] libvirt-daemon-driver-qemu:amd64 10.3.0-3 -> 10.4.0-1
    [UPGRADE] python3-libvirt:amd64 10.3.0-1 -> 10.4.0-1
    [UPGRADE] qemu-block-extra:amd64 1:8.2.4+ds-1 -> 1:8.2.4+ds-2
    [UPGRADE] qemu-system-common:amd64 1:8.2.4+ds-1 -> 1:8.2.4+ds-2
    [UPGRADE] qemu-system-data:amd64 1:8.2.4+ds-1 -> 1:8.2.4+ds-2
    [UPGRADE] qemu-system-gui:amd64 1:8.2.4+ds-1 -> 1:8.2.4+ds-2
    [UPGRADE] qemu-system-modules-opengl:amd64 1:8.2.4+ds-1 -> 1:8.2.4+ds-2
    [UPGRADE] qemu-system-modules-spice:amd64 1:8.2.4+ds-1 -> 1:8.2.4+ds-2
    [UPGRADE] qemu-system-x86:amd64 1:8.2.4+ds-1 -> 1:8.2.4+ds-2
    [UPGRADE] qemu-utils:amd64 1:8.2.4+ds-1 -> 1:8.2.4+ds-2

But I couldn't find anything interesting in their changelogs.
The usual online forums digging suggested to make sure that libvirtd is active
[1] - and it does. I also experimented with solutions proposed for similar but
different issues, to no avail. Here I got stuck.
Someone can help me investigate or resolve the issue?



[1]: https://bbs.archlinux.org/viewtopic.php?id=289546z



--
Ceppo

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

virt-manager: Cannot recv data: Connection reset by peer Ceppo <ceppo@oziosi.org> - 2024-06-12 17:40 +0200
  Re: virt-manager: Cannot recv data: Connection reset by peer Bruno Kleinert <fuddl@debian.org> - 2024-06-28 18:30 +0200
    Re: virt-manager: Cannot recv data: Connection reset by peer Ceppo <ceppo@oziosi.org> - 2024-07-02 18:30 +0200

csiph-web