distrobox icon indicating copy to clipboard operation
distrobox copied to clipboard

libvirt + virt-manager setup doesnt connect anymore

Open secretmango opened this issue 2 years ago • 0 comments

Thanks for your guide on how to setup a rootful container with qemu and another container with virt-manager. I did that, added ksshaskpass to the virt-manager container for password auth, set the root password in the qemu rootful container and it worked.

But now, weirdly, after reboot it doesnt work anymore?

I have a Desktop entry that launches the rootful container, requires sudo privileges. libvirtd and sshd should run.

I already tried using user "qemu" in the libvirt root container, and adding "qemu" to the "libvirt" group for enhanced permission isolation, and setting the qemu user password accordingly and re-creating the connection, entering the new password.

But in virt-manager I get:

Unable to connect to libvirt qemu+ssh://[email protected]:2222/system.

packet 1416128879 bytes received from server too large, want 33554432

Verify that the 'libvirtd' daemon is running on the remote host.

Libvirt URI is: qemu+ssh://[email protected]:2222/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.12/site-packages/libvirt.py", line 147, in openAuth
    raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: packet 1416128879 bytes received from server too large, want 33554432

The setup is with your guide, an almalinux rootful container and a Fedora39 container for virt-manager and ksshaskpass. It already worked, but now not anymore?

Libvirtd and sshd are now running, libvirtd was dead

secretmango avatar Nov 10 '23 09:11 secretmango