External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-08-28 19:41:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
7b79ee2f78
libvirt/tests/qemumonitorjsondata/qemumonitorjson-nodename-relative.result

34 lines
958 B
Plaintext
Raw Normal View History

tests: qemumonitorjson: Fix 'relative' node name detection test case Add the blockstats data and fix the expected output. Test data was created as: qemu-img create -f qcow2 img0 10M qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img0" img1 qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img1" img2 ... Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:30:18 +00:00
drive-ide0-0-0
tests: qemumonitorjson: Add relative image names for node name detection oVirt uses relative names with directories in them. Test such configuration. Also tests a snapshot done with _REUSE_EXTERNAL and a relative backing file pre-specified in the qcow2 metadata.
2017-03-14 15:20:47 +00:00
filename : '/var/lib/libvirt/images/img3'
tests: qemumonitorjson: Fix 'relative' node name detection test case Add the blockstats data and fix the expected output. Test data was created as: qemu-img create -f qcow2 img0 10M qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img0" img1 qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img1" img2 ... Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:30:18 +00:00
format node : '#block118'
format drv : 'qcow2'
storage node: '#block092'
storage drv : 'file'
tests: qemumonitorjson: Add relative image names for node name detection oVirt uses relative names with directories in them. Test such configuration. Also tests a snapshot done with _REUSE_EXTERNAL and a relative backing file pre-specified in the qcow2 metadata.
2017-03-14 15:20:47 +00:00
filename : '/var/lib/libvirt/images/img2'
tests: qemumonitorjson: Fix 'relative' node name detection test case Add the blockstats data and fix the expected output. Test data was created as: qemu-img create -f qcow2 img0 10M qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img0" img1 qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img1" img2 ... Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:30:18 +00:00
format node : '#block346'
format drv : 'qcow2'
storage node: '#block232'
storage drv : 'file'
tests: qemumonitorjson: Add relative image names for node name detection oVirt uses relative names with directories in them. Test such configuration. Also tests a snapshot done with _REUSE_EXTERNAL and a relative backing file pre-specified in the qcow2 metadata.
2017-03-14 15:20:47 +00:00
filename : '/var/lib/libvirt/images/img1'
tests: qemumonitorjson: Fix 'relative' node name detection test case Add the blockstats data and fix the expected output. Test data was created as: qemu-img create -f qcow2 img0 10M qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img0" img1 qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img1" img2 ... Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:30:18 +00:00
format node : '#block548'
format drv : 'qcow2'
storage node: '#block442'
storage drv : 'file'
tests: qemumonitorjson: Add relative image names for node name detection oVirt uses relative names with directories in them. Test such configuration. Also tests a snapshot done with _REUSE_EXTERNAL and a relative backing file pre-specified in the qcow2 metadata.
2017-03-14 15:20:47 +00:00
filename : '/var/lib/libvirt/images/img0'
tests: qemumonitorjson: Fix 'relative' node name detection test case Add the blockstats data and fix the expected output. Test data was created as: qemu-img create -f qcow2 img0 10M qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img0" img1 qemu-img create -f qcow2 -o "backing_fmt=qcow2,backing_file=img1" img2 ... Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:30:18 +00:00
format node : '#block797'
format drv : 'qcow2'
storage node: '#block614'
storage drv : 'file'
tests: deterministichash: Make hash tables arch-independent It turns out that our implementation of the hashing function is endian-dependent and thus if used on various architectures the testsuite may have different results. Work this around by mocking virHashCodeGen to something which does not use bit operations instead of just setting a deterministic seed.
2017-08-02 15:23:51 +00:00
drive-ide0-0-1
filename : '/var/lib/libvirt/images/relsnap.qcow2'
format node : '#block1290'
format drv : 'qcow2'
storage node: '#block1107'
storage drv : 'file'
filename : '/var/lib/libvirt/images/base.qcow2'
format node : '#block927'
format drv : 'qcow2'
storage node: '#block800'
storage drv : 'file'
Reference in New Issue Copy Permalink