On 08/31/2017 12:26 PM, John Ferlan wrote:
For reference, these were generated by updating a local qemu git
repository to the latest upstream, making sure the latest dependencies
were met via "dnf builddep qemu" from my sufficiently privileged root
account, checking out the v2.10.0 tag, and building in order to generate
an "x86_64-softmmu/qemu-system-x86_64" image.
Then using a clean libvirt tree updated to master and built, the image
was then provided as input:
tests/qemucapsprobe /path/to/x86_64-softmmu/qemu-system-x86_64 > \
tests/qemucapabilitiesdata/caps_2.10.0.x86_64.replies
With the .replies file in place and the DO_TEST line added and build,
then running the following commands:
touch tests/qemucapabilitiesdata/caps_2.10.0.x86_64.xml
VIR_TEST_REGENERATE_OUTPUT=1 ./tests/qemucapabilitiestest
to generate tests/qemucapabilitiesdata/caps_2.10.0.x86_64.xml and both
were added to the commit.
Signed-off-by: John Ferlan <jferlan(a)redhat.com>
---
v2:
https://www.redhat.com/archives/libvir-list/2017-August/msg01061.html
Differences:
* Updated my environment as discussed in v2
* Updated the commit message to describe that
* Remove the comment from tests/qemucapabilitiestest.c
.../caps_2.10.0.x86_64.replies | 18144 +++++++++++++++++++
tests/qemucapabilitiesdata/caps_2.10.0.x86_64.xml | 798 +
tests/qemucapabilitiestest.c | 1 +
3 files changed, 18943 insertions(+)
create mode 100644 tests/qemucapabilitiesdata/caps_2.10.0.x86_64.replies
create mode 100644 tests/qemucapabilitiesdata/caps_2.10.0.x86_64.xml
Anyone willing to give this processing a look see and ACK? Before more
capabilities are added ;-) [I have some non VxHS related changes that
add a capability and there's already a patch on list with more
capability changes).
Tks,
John