shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-26 14:03:49 +03:00
Code Releases Activity
libvirt/tests/qemumonitorjsondata/qemumonitorjson-nodename-relative-named-nodes.json

555 lines
15 KiB
JSON
Raw Normal View History

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 16:20:47 +01:00
[
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"backing-image": {
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/base.qcow2",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"dirty-flag": false
},
"backing-filename-format": "qcow2",
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/relsnap.qcow2",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"full-backing-filename": "/var/lib/libvirt/images/base.qcow2",
"backing-filename": "/var/lib/libvirt/images/base.qcow2",
"dirty-flag": false
},
"iops_wr": 0,
"ro": false,
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 10:30:18 +02:00
"node-name": "#block1290",
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 16:20:47 +01:00
"backing_file_depth": 1,
"drv": "qcow2",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"backing_file": "/var/lib/libvirt/images/base.qcow2",
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/relsnap.qcow2",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 197120,
"filename": "/var/lib/libvirt/images/relsnap.qcow2",
"format": "file",
"actual-size": 200704,
"dirty-flag": false
},
"iops_wr": 0,
"ro": false,
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 10:30:18 +02:00
"node-name": "#block1107",
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 16:20:47 +01:00
"backing_file_depth": 0,
"drv": "file",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/relsnap.qcow2",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/base.qcow2",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"dirty-flag": false
},
"iops_wr": 0,
"ro": true,
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 10:30:18 +02:00
"node-name": "#block927",
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 16:20:47 +01:00
"backing_file_depth": 0,
"drv": "qcow2",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/base.qcow2",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 197120,
"filename": "/var/lib/libvirt/images/base.qcow2",
"format": "file",
"actual-size": 200704,
"dirty-flag": false
},
"iops_wr": 0,
"ro": true,
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 10:30:18 +02:00
"node-name": "#block800",
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 16:20:47 +01:00
"backing_file_depth": 0,
"drv": "file",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/base.qcow2",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img0",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"dirty-flag": false
},
"iops_wr": 0,
"ro": true,
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 10:30:18 +02:00
"node-name": "#block797",
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 16:20:47 +01:00
"backing_file_depth": 0,
"drv": "qcow2",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/img0",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 197120,
"filename": "/var/lib/libvirt/images/img0",
"format": "file",
"actual-size": 200704,
"dirty-flag": false
},
"iops_wr": 0,
"ro": true,
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 10:30:18 +02:00
"node-name": "#block614",
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 16:20:47 +01:00
"backing_file_depth": 0,
"drv": "file",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/img0",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"backing-image": {
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img0",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"dirty-flag": false
},
"backing-filename-format": "qcow2",
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img1",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"full-backing-filename": "/var/lib/libvirt/images/img0",
"backing-filename": "/var/lib/libvirt/images/img0",
"dirty-flag": false
},
"iops_wr": 0,
"ro": true,
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 10:30:18 +02:00
"node-name": "#block548",
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 16:20:47 +01:00
"backing_file_depth": 1,
"drv": "qcow2",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"backing_file": "/var/lib/libvirt/images/img0",
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/img1",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 197120,
"filename": "/var/lib/libvirt/images/img1",
"format": "file",
"actual-size": 200704,
"dirty-flag": false
},
"iops_wr": 0,
"ro": true,
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 10:30:18 +02:00
"node-name": "#block442",
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 16:20:47 +01:00
"backing_file_depth": 0,
"drv": "file",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/img1",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"backing-image": {
"backing-image": {
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img0",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"dirty-flag": false
},
"backing-filename-format": "qcow2",
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img1",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"full-backing-filename": "/var/lib/libvirt/images/img0",
"backing-filename": "/var/lib/libvirt/images/img0",
"dirty-flag": false
},
"backing-filename-format": "qcow2",
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img2",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"full-backing-filename": "/var/lib/libvirt/images/img1",
"backing-filename": "/var/lib/libvirt/images/img1",
"dirty-flag": false
},
"iops_wr": 0,
"ro": true,
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 10:30:18 +02:00
"node-name": "#block346",
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 16:20:47 +01:00
"backing_file_depth": 2,
"drv": "qcow2",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"backing_file": "/var/lib/libvirt/images/img1",
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/img2",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 197120,
"filename": "/var/lib/libvirt/images/img2",
"format": "file",
"actual-size": 200704,
"dirty-flag": false
},
"iops_wr": 0,
"ro": true,
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 10:30:18 +02:00
"node-name": "#block232",
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 16:20:47 +01:00
"backing_file_depth": 0,
"drv": "file",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/img2",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"backing-image": {
"backing-image": {
"backing-image": {
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img0",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"dirty-flag": false
},
"backing-filename-format": "qcow2",
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img1",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"full-backing-filename": "/var/lib/libvirt/images/img0",
"backing-filename": "/var/lib/libvirt/images/img0",
"dirty-flag": false
},
"backing-filename-format": "qcow2",
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img2",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"full-backing-filename": "/var/lib/libvirt/images/img1",
"backing-filename": "/var/lib/libvirt/images/img1",
"dirty-flag": false
},
"backing-filename-format": "qcow2",
"virtual-size": 10485760,
"filename": "/var/lib/libvirt/images/img3",
"cluster-size": 65536,
"format": "qcow2",
"actual-size": 200704,
"format-specific": {
"type": "qcow2",
"data": {
"compat": "1.1",
"lazy-refcounts": false,
"refcount-bits": 16,
"corrupt": false
}
},
"full-backing-filename": "/var/lib/libvirt/images/img2",
"backing-filename": "/var/lib/libvirt/images/img2",
"dirty-flag": false
},
"iops_wr": 0,
"ro": false,
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 10:30:18 +02:00
"node-name": "#block118",
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 16:20:47 +01:00
"backing_file_depth": 3,
"drv": "qcow2",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"backing_file": "/var/lib/libvirt/images/img2",
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/img3",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 197120,
"filename": "/var/lib/libvirt/images/img3",
"format": "file",
"actual-size": 200704,
"dirty-flag": false
},
"iops_wr": 0,
"ro": false,
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 10:30:18 +02:00
"node-name": "#block092",
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 16:20:47 +01:00
"backing_file_depth": 0,
"drv": "file",
"iops": 0,
"bps_wr": 0,
"write_threshold": 0,
"encrypted": false,
"bps": 0,
"bps_rd": 0,
"cache": {
"no-flush": false,
"direct": false,
"writeback": true
},
"file": "/var/lib/libvirt/images/img3",
"encryption_key_missing": false
}
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 10:30:18 +02:00
]
Copy Permalink