search for: iohelp

Hello everybody! I'm trying to make some experiments with writing/reading stream to/from volume. I've realized that libvirt-iohelper are ran to make this operations: 1) reading stream from stdin and writng to a file 2) reading stream from a file and writing to stdout I've also realized that virsh uses libvirt-iohelper via virStorageVolUpload/virStorageVolDownload. But i can't find the place where virsh works with stdin...

...age sucks, I'll send patches to improve it a little at least. What's happening here is that the you haven't read all the data you requested (it's vol.download(path, offset, length, flags), length == 0 means read the whole file which I suspect you haven't done). In this case the iohelper program that libvirt uses won't complete feeding us all the data, and it exits with SIGPIPE when we close the read end of the pipe. Now whether that should actually be an error condition is open to debate. virStreamFinish docs make it sound like it's legitimate to throw an error if it ap...

...ove it a little at least. > > > > What's happening here is that the you haven't read all the data you requested > > (it's vol.download(path, offset, length, flags), length == 0 means read the > > whole file which I suspect you haven't done). In this case the iohelper > > program that libvirt uses won't complete feeding us all the data, and it exits > > with SIGPIPE when we close the read end of the pipe. > > > > Now whether that should actually be an error condition is open to debate. > > virStreamFinish docs make it sound l...

...gt;>>> >>>> What's happening here is that the you haven't read all the data you requested >>>> (it's vol.download(path, offset, length, flags), length == 0 means read the >>>> whole file which I suspect you haven't done). In this case the iohelper >>>> program that libvirt uses won't complete feeding us all the data, and it exits >>>> with SIGPIPE when we close the read end of the pipe. >>>> >>>> Now whether that should actually be an error condition is open to debate. >>>> vi...

...>>>> What's happening here is that the you haven't read all the data you requested >>>>>> (it's vol.download(path, offset, length, flags), length == 0 means read the >>>>>> whole file which I suspect you haven't done). In this case the iohelper >>>>>> program that libvirt uses won't complete feeding us all the data, and it exits >>>>>> with SIGPIPE when we close the read end of the pipe. >>>>>> >>>>>> Now whether that should actually be an error condition is ope...

...send patches to improve it a little at least. > > What's happening here is that the you haven't read all the data you requested > (it's vol.download(path, offset, length, flags), length == 0 means read the > whole file which I suspect you haven't done). In this case the iohelper > program that libvirt uses won't complete feeding us all the data, and it exits > with SIGPIPE when we close the read end of the pipe. > > Now whether that should actually be an error condition is open to debate. > virStreamFinish docs make it sound like it's legitimate t...

...followed following procedure to compile the libvirt library. 1. ./autogen.sh --system --with-xen 2. make While running "make", I am receiving following errors : ------------------------------------------------------------------------------------------------------------- CC libvirt_iohelper-iohelper.o CCLD libvirt_iohelper CC libvirt_parthelper-parthelper.o CCLD libvirt_parthelper libvirt_parthelper-parthelper.o: In function `main': /root/Downloads/libvirt-0.9.11/src/storage/parthelper.c:103: undefined reference to `ped_device_get' /root/Downloads/libvirt-0.9.1...

...east. > > > > > > What's happening here is that the you haven't read all the data you requested > > > (it's vol.download(path, offset, length, flags), length == 0 means read the > > > whole file which I suspect you haven't done). In this case the iohelper > > > program that libvirt uses won't complete feeding us all the data, and it exits > > > with SIGPIPE when we close the read end of the pipe. > > > > > > Now whether that should actually be an error condition is open to debate. > > > virStreamFi...

...t;> What's happening here is that the you haven't read all the data you requested > >>>>>> (it's vol.download(path, offset, length, flags), length == 0 means read the > >>>>>> whole file which I suspect you haven't done). In this case the iohelper > >>>>>> program that libvirt uses won't complete feeding us all the data, and it exits > >>>>>> with SIGPIPE when we close the read end of the pipe. > >>>>>> > >>>>>> Now whether that should actually be an er...

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>

...gt; >>>>> What's happening here is that the you haven't read all the data you requested >>>>> (it's vol.download(path, offset, length, flags), length == 0 means read the >>>>> whole file which I suspect you haven't done). In this case the iohelper >>>>> program that libvirt uses won't complete feeding us all the data, and it exits >>>>> with SIGPIPE when we close the read end of the pipe. >>>>> >>>>> Now whether that should actually be an error condition is open to debate. &gt...

...ault NAT subnet (Eric Blake) - formatdomain: Add release info for disk <driver> attributes (Cole Robinson) - Fix spelling mistake: seek (Philipp Hahn) - maint: fix grammar in error message (Eric Blake) Portability: - virsh: fix mingw failure on creating nonblocking pipe (Eric Blake) - Remove iohelper on Win32 since it is not required (Daniel P. Berrange) - Fix domain events C example on Win32 (Daniel P. Berrange) - build: fix compilation on mingw (Eric Blake) - util: use SCM_RIGHTS in virFileOperation when needed (Eric Blake) - Don't use INT64_MAX in libvirt.h because it requires stdint.h...