search for: virstreamabort

I get just _READABLE events repeatedly, virStreamAbort() doesn't work, it gets out of control after the target domain stops and the unix scocket is deleted. I ended connecting directly to the unix socket. I just wanted to ask if it certainly is a bug or perhaps someone went through this before and have a workaround. Jose V. Em ter, 16 de mai de 20...

On Wed, May 17, 2017 at 09:08:14AM +0200, Martin Kletzander wrote: >On Wed, May 17, 2017 at 01:01:39AM +0000, JosÉ Luis Valencia Gutierrez wrote: >>I get just _READABLE events repeatedly, virStreamAbort() doesn't work, it >>gets out of control after the target domain stops and the unix scocket is >>deleted. I ended connecting directly to the unix socket. I just wanted to >>ask if it certainly is a bug or perhaps someone went through this before >>and have a workaround....

Hello everyone, I am opening a virChannel(unix) to a domain and receiving data with a non-blocking virStream using events, when the connected domain gets stopped(which deletes the channel unix socket) by calling destroy, shutdown, pause or migrate on that domain, with the stream open the read event is triggered repeatedly, and virStreamRecv returns 0 bytes indicating EOF but neither

On Wed, May 17, 2017 at 01:01:39AM +0000, JosÉ Luis Valencia Gutierrez wrote: >I get just _READABLE events repeatedly, virStreamAbort() doesn't work, it >gets out of control after the target domain stops and the unix scocket is >deleted. I ended connecting directly to the unix socket. I just wanted to >ask if it certainly is a bug or perhaps someone went through this before >and have a workaround. > It's O...

...rStreamRecv returns end-of-file. * * This method is a synchronization point for all asynchronous * errors, so if this returns a success code the application can * be sure that all data has been successfully processed. * * Returns 0 on success, -1 upon error */ So maybe in your case you want virStreamAbort instead (which also unconditionally throws an error which is also an issue IMO but can be ignored) CCing danpb for this thoughts on the erroring semantics - Cole

...de mai de 2017 às 12:49, Martin Kletzander <mkletzan@redhat.com> escreveu: > On Wed, May 17, 2017 at 09:08:14AM +0200, Martin Kletzander wrote: > >On Wed, May 17, 2017 at 01:01:39AM +0000, JosÉ Luis Valencia Gutierrez > wrote: > >>I get just _READABLE events repeatedly, virStreamAbort() doesn't work, it > >>gets out of control after the target domain stops and the unix scocket is > >>deleted. I ended connecting directly to the unix socket. I just wanted to > >>ask if it certainly is a bug or perhaps someone went through this before > >>and...

...n point for all asynchronous > > * errors, so if this returns a success code the application can > > * be sure that all data has been successfully processed. > > * > > * Returns 0 on success, -1 upon error > > */ > > > > So maybe in your case you want virStreamAbort instead (which also > > unconditionally throws an error which is also an issue IMO but can be ignored) > > > > CCing danpb for this thoughts on the erroring semantics > > > > - Cole

...* This method is a synchronization point for all asynchronous > * errors, so if this returns a success code the application can > * be sure that all data has been successfully processed. > * > * Returns 0 on success, -1 upon error > */ > > So maybe in your case you want virStreamAbort instead (which also > unconditionally throws an error which is also an issue IMO but can be ignored) > > CCing danpb for this thoughts on the erroring semantics > > - Cole

...m Utils error : this function is not supported by >the connection driver: virStreamEventRemoveCallback > > >Is there other way to stop getting this errors? or perhaps this is a bug. > This sounds like a bug. Do you get no other event than just _READABLE? No _HANGUP or _ERROR? Does virStreamAbort() work, even though it's probably not what you are looking for? >Thanks in advance. > >Jose Valencia >_______________________________________________ >libvirt-users mailing list >libvirt-users@redhat.com >https://www.redhat.com/mailman/listinfo/libvirt-users

...d out>, opaque=0x7fa0ec00cad0) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/conf/virconsole.c:259 #2 0x00007fa0ffa7a303 in virFDStreamCloseInt (st=0x7fa0ec00c900, streamAbort=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/fdstream.c:325 #3 0x00007fa0ffaa0503 in virStreamAbort (stream=0x7fa0ec00c900) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/libvirt.c:15289 #4 0x00000000004290c0 in daemonStreamEvent (st=<optimized out>, events=12, opaque=0x18869f0) at /var/tmp/build/libvirt/libvirt-0.9.13/./daemon/stream.c:234 #5 0x00007fa0ffa7a4ac in virFDStreamEvent (w...

...gt; > * errors, so if this returns a success code the application can > > > * be sure that all data has been successfully processed. > > > * > > > * Returns 0 on success, -1 upon error > > > */ > > > > > > So maybe in your case you want virStreamAbort instead (which also > > > unconditionally throws an error which is also an issue IMO but can be ignored) > > > > > > CCing danpb for this thoughts on the erroring semantics > > > > > > - Cole

Hi, The following snippet works fine e.g. receiving the data but when calling stream.finish() we get the following error: stream = con.newStream() vol.download(stream, 0, 0, 0) buf = stream.recv(1024) stream.finish() libvirt: I/O Stream Utils error : internal error: I/O helper exited abnormally Traceback (most recent call last): File "./helpers/kvm2ovirt", line 149, in <module>