Bug#659956: libvirt-bin: virsh/virt-manager connection failure: Cannot recv data: Value too large for defined data type,Date: Tue, 16 Oct 2012 10:12:18 +0200

2013-04-15 Thread ~redShadow~
I'm experiencing this bug too. Here it is some relevant information: Client machine: Debian Wheezy 64bit virt-manager0.9.1-4 libvirt-bin 0.9.12-11 libvirt00.9.12-11 python-libvirt 0.9.12-11 Problematic server machine: Debian Wheezy 64bit libvirt-bin 0.9.12-11 libvirt0

Bug#659956: libvirt-bin: virsh/virt-manager connection failure: Cannot recv data: Value too large for defined data type

2012-10-16 Thread Martin Steigerwald
Am Samstag, 13. Oktober 2012 schrieb Guido Günther: On Wed, Feb 15, 2012 at 11:03:18AM +0100, Martin Steigerwald wrote: Package: libvirt-bin Version: 0.9.10~rc1-1 Severity: important [..snip..] ms@mango:~ LANG=C virsh -d1 -c qemu+ssh://r...@frisbie.of.teamix.net/system error:

Bug#659956: libvirt-bin: virsh/virt-manager connection failure: Cannot recv data: Value too large for defined data type

2012-10-13 Thread Guido Günther
On Wed, Feb 15, 2012 at 11:03:18AM +0100, Martin Steigerwald wrote: Package: libvirt-bin Version: 0.9.10~rc1-1 Severity: important [..snip..] ms@mango:~ LANG=C virsh -d1 -c qemu+ssh://r...@frisbie.of.teamix.net/system error: Cannot recv data: Value too large for defined data type error:

Bug#659956: libvirt-bin: virsh/virt-manager connection failure: Cannot recv data: Value too large for defined data type

2012-02-15 Thread Martin Steigerwald
Package: libvirt-bin Version: 0.9.10~rc1-1 Severity: important Dear Maintainer, Yesterday I reported a connection failure without error message in virt-manager (#659860). The lack of an error message was a problem with virt-manager that is fixed meanwhile, but the actual connection failure is a