Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1695532 - virt-manager over qemu+ssh fails with "Cannot recv data: Value too large for defined data type" [NEEDINFO]
Summary: virt-manager over qemu+ssh fails with "Cannot recv data: Value too large for ...
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-manager
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: virt-mgr-maint
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2019-04-03 09:52 UTC by Christophe de Dinechin
Modified: 2019-04-03 13:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug
Target Upstream Version:
crobinso: needinfo? (dinechin)

Attachments (Terms of Use)

Description Christophe de Dinechin 2019-04-03 09:52:50 UTC
Description of problem:

Connecting to virt-manager over ssh with `virt-manager -c qemu+ssh://virtlab` fails with the following message:

   Unable to connect to libvirt qemu+ssh://virtlab
   Cannot recv data: Value too large for defined data type
   Verify that the 'libvirtd' daemon is running on the remote host

libvirtd is running on the remote host.

Version-Release number of selected component (if applicable):

virt-manager.noarch                2.0.0-5.el8                 @beaker-AppStream
virt-manager.noarch                    2.1.0-1.fc29                     @updates

How reproducible: Always

Steps to Reproduce:
1. From F9 machine, virt-manager -c qemu+ssh://rhel8-machine

Actual results: Above error message

Expected results: Remote connexion is established

Comment 1 Cole Robinson 2019-04-03 13:13:12 UTC
That URI is incorrect, it should have /system appended to it. But there should be an explicit error about that, not sure why you aren't seeing it.

Does 'virsh --connect ...' give the same error? Do either work with the corrected URI?

Note You need to log in before you can comment on or make changes to this bug.