similar to: stream finish throws exception via python API

On 04/25/2016 08:10 AM, Shahar Havivi wrote: > On 17.04.16 15:41, Shahar Havivi wrote: >> 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() >> >>

On 26.04.16 14:14, Shahar Havivi wrote: > On 25.04.16 09:11, Cole Robinson wrote: > > On 04/25/2016 08:10 AM, Shahar Havivi wrote: > > > On 17.04.16 15:41, Shahar Havivi wrote: > > >> Hi, > > >> The following snippet works fine e.g. receiving the data but when calling > > >> stream.finish() we get the following error: > > >> >

On 04/26/2016 09:35 AM, Shahar Havivi wrote: > On 26.04.16 15:30, Shahar Havivi wrote: >> On 26.04.16 14:14, Shahar Havivi wrote: >>> On 25.04.16 09:11, Cole Robinson wrote: >>>> On 04/25/2016 08:10 AM, Shahar Havivi wrote: >>>>> On 17.04.16 15:41, Shahar Havivi wrote: >>>>>> Hi, >>>>>> The following snippet works

On 04/26/2016 02:56 PM, Nir Soffer wrote: > On Tue, Apr 26, 2016 at 4:37 PM, Cole Robinson <crobinso@redhat.com> wrote: >> On 04/26/2016 09:35 AM, Shahar Havivi wrote: >>> On 26.04.16 15:30, Shahar Havivi wrote: >>>> On 26.04.16 14:14, Shahar Havivi wrote: >>>>> On 25.04.16 09:11, Cole Robinson wrote: >>>>>> On 04/25/2016 08:10

On 25.04.16 09:11, Cole Robinson wrote: > On 04/25/2016 08:10 AM, Shahar Havivi wrote: > > On 17.04.16 15:41, Shahar Havivi wrote: > >> 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)

On 26.04.16 15:30, Shahar Havivi wrote: > On 26.04.16 14:14, Shahar Havivi wrote: > > On 25.04.16 09:11, Cole Robinson wrote: > > > On 04/25/2016 08:10 AM, Shahar Havivi wrote: > > > > On 17.04.16 15:41, Shahar Havivi wrote: > > > >> Hi, > > > >> The following snippet works fine e.g. receiving the data but when calling > > >

On 17.04.16 15:41, Shahar Havivi wrote: > 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 >

On Tue, Apr 26, 2016 at 03:17:19PM -0400, Cole Robinson wrote: > On 04/26/2016 02:56 PM, Nir Soffer wrote: > > On Tue, Apr 26, 2016 at 4:37 PM, Cole Robinson <crobinso@redhat.com> wrote: > >> On 04/26/2016 09:35 AM, Shahar Havivi wrote: > >>> On 26.04.16 15:30, Shahar Havivi wrote: > >>>> On 26.04.16 14:14, Shahar Havivi wrote: >

On Tue, Apr 26, 2016 at 4:37 PM, Cole Robinson <crobinso@redhat.com> wrote: > On 04/26/2016 09:35 AM, Shahar Havivi wrote: >> On 26.04.16 15:30, Shahar Havivi wrote: >>> On 26.04.16 14:14, Shahar Havivi wrote: >>>> On 25.04.16 09:11, Cole Robinson wrote: >>>>> On 04/25/2016 08:10 AM, Shahar Havivi wrote: >>>>>> On 17.04.16 15:41,

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

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

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 2017 às 05:28, Martin Kletzander

On Wed, May 17, 2017 at 07:53:35PM +0000, JosÉ Luis Valencia Gutierrez wrote: >I just tried removing the callback before calling virStreamFinish and it >worked right, I thought by simply finish the stream would stop the events >and close it, the example I was based on only calls virStreamFinish on EOF >event. > I'm working on a patch that removes the callbacks after calling

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

This series adds a new output mode for virt-v2v, called -o json. It produces local files, just like -o local, although the metadata produced is a JSON file with data that v2v collected in the conversion process. This can be useful for converting to unsupported destinations, still based on QEMU/KVM. In addition to a simple different metadata, it offers a way to relocate the disks, with

I'm working on (re-) implementing serial console support in virtualbmc [1], and one of the issues I'm hitting right now is that after establishing a console connection via... self._stream = self._conn.newStream(libvirt.VIR_STREAM_NONBLOCK) self._domain.openConsole(None, self._stream, 0) ...I can't figure out how to close the console. Subsequent calls to openConsole fail

This series adds a new output mode for virt-v2v, called -o json. It produces local files, just like -o local, although the metadata produced is a JSON file with data that v2v collected in the conversion process. This can be useful for converting to unsupported destinations, still based on QEMU/KVM. In addition to a simple different metadata, it offers a way to relocate the disks, with

On 04/27/2016 04:26 AM, Daniel P. Berrange wrote: > On Tue, Apr 26, 2016 at 03:17:19PM -0400, Cole Robinson wrote: >> On 04/26/2016 02:56 PM, Nir Soffer wrote: >>> On Tue, Apr 26, 2016 at 4:37 PM, Cole Robinson <crobinso@redhat.com> wrote: >>>> On 04/26/2016 09:35 AM, Shahar Havivi wrote: >>>>> On 26.04.16 15:30, Shahar Havivi wrote:

I just tried removing the callback before calling virStreamFinish and it worked right, I thought by simply finish the stream would stop the events and close it, the example I was based on only calls virStreamFinish on EOF event. Em qua, 17 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 16.09.14 15:09, Richard W.M. Jones wrote: > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > I am using upstream qemu while using this local variables: > > export PATH=/home/shahar/git/qemu:$PATH > > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64 > > > > Is that sufficient? > > Yup, upstream qemu should