External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-08 14:29:56 +00:00
Code Issues Packages Projects Releases Wiki Activity
f204cf5103
libvirt/tests/qemumonitorjsondata/qemumonitorjson-nodename-same-backing-named-nodes.json

317 lines
8.0 KiB
JSON
Raw Normal View History

tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00:00
[
{
"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: Add data and fix 'same-backing' node detection case With the new approach we are actually able to correctly detect node names for the two instances of the same backing file. Test images were created as: qemu-img create -f qcow2 /var/lib/libvirt/images/base.qcow2 10M qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/a.qcow2 qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/b.qcow2 and then used for two separate disks. Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:27:57 +00:00
"node-name": "#block771",
tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00: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: Add data and fix 'same-backing' node detection case With the new approach we are actually able to correctly detect node names for the two instances of the same backing file. Test images were created as: qemu-img create -f qcow2 /var/lib/libvirt/images/base.qcow2 10M qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/a.qcow2 qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/b.qcow2 and then used for two separate disks. Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:27:57 +00:00
"node-name": "#block692",
tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00: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": {
"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/b.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: Add data and fix 'same-backing' node detection case With the new approach we are actually able to correctly detect node names for the two instances of the same backing file. Test images were created as: qemu-img create -f qcow2 /var/lib/libvirt/images/base.qcow2 10M qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/a.qcow2 qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/b.qcow2 and then used for two separate disks. Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:27:57 +00:00
"node-name": "#block548",
tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00: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/b.qcow2",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 197120,
"filename": "/var/lib/libvirt/images/b.qcow2",
"format": "file",
"actual-size": 200704,
"dirty-flag": false
},
"iops_wr": 0,
"ro": false,
tests: qemumonitorjson: Add data and fix 'same-backing' node detection case With the new approach we are actually able to correctly detect node names for the two instances of the same backing file. Test images were created as: qemu-img create -f qcow2 /var/lib/libvirt/images/base.qcow2 10M qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/a.qcow2 qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/b.qcow2 and then used for two separate disks. Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:27:57 +00:00
"node-name": "#block487",
tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00: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/b.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: Add data and fix 'same-backing' node detection case With the new approach we are actually able to correctly detect node names for the two instances of the same backing file. Test images were created as: qemu-img create -f qcow2 /var/lib/libvirt/images/base.qcow2 10M qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/a.qcow2 qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/b.qcow2 and then used for two separate disks. Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:27:57 +00:00
"node-name": "#block320",
tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00: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: Add data and fix 'same-backing' node detection case With the new approach we are actually able to correctly detect node names for the two instances of the same backing file. Test images were created as: qemu-img create -f qcow2 /var/lib/libvirt/images/base.qcow2 10M qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/a.qcow2 qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/b.qcow2 and then used for two separate disks. Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:27:57 +00:00
"node-name": "#block224",
tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00: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": {
"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/a.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: Add data and fix 'same-backing' node detection case With the new approach we are actually able to correctly detect node names for the two instances of the same backing file. Test images were created as: qemu-img create -f qcow2 /var/lib/libvirt/images/base.qcow2 10M qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/a.qcow2 qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/b.qcow2 and then used for two separate disks. Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:27:57 +00:00
"node-name": "#block132",
tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00: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/a.qcow2",
"encryption_key_missing": false
},
{
"iops_rd": 0,
"detect_zeroes": "off",
"image": {
"virtual-size": 197120,
"filename": "/var/lib/libvirt/images/a.qcow2",
"format": "file",
"actual-size": 200704,
"dirty-flag": false
},
"iops_wr": 0,
"ro": false,
tests: qemumonitorjson: Add data and fix 'same-backing' node detection case With the new approach we are actually able to correctly detect node names for the two instances of the same backing file. Test images were created as: qemu-img create -f qcow2 /var/lib/libvirt/images/base.qcow2 10M qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/a.qcow2 qemu-img create -f qcow2 \ -o "backing_fmt=qcow2,backing_file=/var/lib/libvirt/images/base.qcow2 \ /var/lib/libvirt/images/b.qcow2 and then used for two separate disks. Reviewed-by: Eric Blake <eblake@redhat.com>
2017-07-26 08:27:57 +00:00
"node-name": "#block020",
tests: qemumonitorjson: Add case for two disks sharing a backing image Since we have to match the images by filename a common backing image will break the detection process. Add a test case to see that the code correctly did not continue the detection process.
2017-03-14 14:02:11 +00: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/a.qcow2",
"encryption_key_missing": false
}
]
Reference in New Issue Copy Permalink