On 01/08/2016 11:24, Marc-André Lureau wrote:
> Hi
>
> - Original Message -
>>
>>
>> On 27/07/2016 23:37, Laszlo Ersek wrote:
>>> It seems to me that QEMU deadlocks when it tries to emit the
>>> SPICE_DISCONNECTED event.
>>>
>>> (Note that I can't find "handle SPICE_DISCONNECTED" in the
Hi
- Original Message -
>
>
> On 27/07/2016 23:37, Laszlo Ersek wrote:
> > It seems to me that QEMU deadlocks when it tries to emit the
> > SPICE_DISCONNECTED event.
> >
> > (Note that I can't find "handle SPICE_DISCONNECTED" in the libvirtd log
> > even in the successful case (i.e., wh
On 27/07/2016 23:37, Laszlo Ersek wrote:
> It seems to me that QEMU deadlocks when it tries to emit the
> SPICE_DISCONNECTED event.
>
> (Note that I can't find "handle SPICE_DISCONNECTED" in the libvirtd log
> even in the successful case (i.e., when QEMU is built at the parent of
> 3d344c2aabb7)
On 07/19/16 20:41, Markus Armbruster wrote:
> From: Paolo Bonzini
>
> This saves a lot of memory compared to a statically-sized array,
> or at least 24kb could be considered a lot on an Atari ST.
> It also makes the code more similar to QmpOutputVisitor.
>
> This removes the limit on the depth of
From: Paolo Bonzini
This saves a lot of memory compared to a statically-sized array,
or at least 24kb could be considered a lot on an Atari ST.
It also makes the code more similar to QmpOutputVisitor.
This removes the limit on the depth of a QObject that can be processed
into a QAPI tree. This
