search for: virnetclientincomingev

Displaying 3 results from an estimated 3 matches for "virnetclientincomingev".

libvirt tls error
2013 Apr 22
2
libvirt tls error
...tdev private]# virsh -c qemu+tls://ovirtdev.localhost/system list 2013-04-22 03:37:09.362+0000: 9898: info : libvirt version: 0.9.10, package: 21.el6_3.8 (CentOS BuildSystem <http://bugs.centos.org>, 2013-01-28-19:24:16, c6b10.bsys.dev.centos.org) 2013-04-22 03:37:09.362+0000: 9898: warning : virNetClientIncomingEvent:1665 : Something went wrong during async message processing error: Unable to read TLS confirmation: Input/output error error: failed to connect to the hypervisor thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvir...
Fwd: [Issue]: Regarding client socket getting closed from the server once the lxc container is started
2016 Mar 18
0
Fwd: [Issue]: Regarding client socket getting closed from the server once the lxc container is started
...rocessCleanInterfaces:475 : Cleared net names: eth0 * *2016-03-12 08:18:55.750+0000: 1247: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x7fed5c168eb0* *2016-03-12 08:18:55.750+0000: 1247: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x7fed5c169600* *2016-03-12 08:18:55.755+0000: 1244: debug : virNetClientIncomingEvent:1808 : client=0x7fed54009d10 wantclose=0* *2016-03-12 08:18:55.755+0000: 1244: debug : virNetClientIncomingEvent:1816 : Event fired 0x7fed54009040 1* *2016-03-12 08:18:55.755+0000: 1244: debug : virNetMessageDecodeLength:151 : Got length, now need 36 total (32 more)* *2016-03-12 08:18:55.756+...
Re: libvirt tls error
2013 May 28
0
Re: libvirt tls error
...te]# virsh -c qemu+tls://ovirtdev.localhost/system list > 2013-04-22 03:37:09.362+0000: 9898: info : libvirt version: 0.9.10, package: 21.el6_3.8 (CentOS BuildSystem <http://bugs.centos.org>, 2013-01-28-19:24:16, c6b10.bsys.dev.centos.org) > 2013-04-22 03:37:09.362+0000: 9898: warning : virNetClientIncomingEvent:1665 : Something went wrong during async message processing > error: Unable to read TLS confirmation: Input/output error > error: failed to connect to the hypervisor > > thanks I get a very similar error with an updated Centos 6.4 distro: [root@darkgoo ~]# virsh -c qemu+tls://hvm...