On 08/17/2018 03:37 AM, Markus Armbruster wrote:
Perhaps worth documenting is the range of JSON numbers produced by
qemu (maybe as a separate patch). Libvirt just hit a bug with the
jansson library making it extremely difficult to parse JSON containing
numbers larger than INT64_MAX, when compare
On 08/17/2018 06:16 AM, Markus Armbruster wrote:
+2.7 QGA Synchronization
---
When using QGA, an additional synchronization feature is built
into
-the protocol. If the Client sends a raw 0xFF sentinel byte (not valid
-JSON), then the Server will reset its state and d
Eric Blake writes:
> On 08/08/2018 07:03 AM, Markus Armbruster wrote:
>> Section "QGA Synchronization" specifies that sending "a raw 0xFF
>> sentinel byte" makes the server "reset its state and discard all
>> pending data prior to the sentinel." What actually happens there is a
>> lexical error,
Eric Blake writes:
> On 08/08/2018 07:03 AM, Markus Armbruster wrote:
>> Section "QGA Synchronization" specifies that sending "a raw 0xFF
>> sentinel byte" makes the server "reset its state and discard all
>> pending data prior to the sentinel." What actually happens there is a
>> lexical error,
On 08/08/2018 07:03 AM, Markus Armbruster wrote:
Section "QGA Synchronization" specifies that sending "a raw 0xFF
sentinel byte" makes the server "reset its state and discard all
pending data prior to the sentinel." What actually happens there is a
lexical error, which will produce one ore more
Section "QGA Synchronization" specifies that sending "a raw 0xFF
sentinel byte" makes the server "reset its state and discard all
pending data prior to the sentinel." What actually happens there is a
lexical error, which will produce one ore more error responses.
Moreover, it's not specific to QGA
