On Wed, 25 Jan 2012 20:55:14 -0700
Eric Blake <eblake(a)redhat.com> wrote:
On 12/02/2011 01:32 PM, Anthony Liguori wrote:
>> But we already have to call 'qemu -h' for other reasons; so we might as
>> well be efficient and learn as much as possible from that result than by
>> calling both 'qemu -h' and 'qemu -qmp ...', in order to probe
what qemu
>> supports.
>>
>> Also, 'qemu -qmp' doesn't work. What's the proper syntax for
invoking
>> qemu in order to query QMP capabilities, but without also starting up a
>> guest?
>
>
> anthony@titi:~/build/qemu$ (sleep 1; echo -e '{"execute":
> "qmp_capabilities"}\n{"execute": "quit"}') |
> x86_64-softmmu/qemu-system-x86_64 -qmp stdio -S -display none | head -1
> {"QMP": {"version": {"qemu": {"micro": 94,
"minor": 15, "major": 0},
> "package": ""}, "capabilities": []}}
Doesn't work on 0.12 (the first version with qmp):
There's another problem lurking here, and I think it's a more serious one:
I don't we are doing proper integration tests with libvirt (we == qemu, but
mostly me).
My tests are sporadic and mostly manual (I used to use libvirt-tck, but it's
been a while since I ran it last time).
Is libvirt-tck the recommended way to run integration tests? If it's we should
be running it frequently.