libvirt/tests/virstoragetestdata/out/qcow2-protocol-backing-file

path:ABS_SRCDIR/virstoragetestdata/images/qcow2-protocol-backing-file.qcow2
backingStoreRaw: raw
backingStoreRawFormat: <null>(-1)
capacity: 1024
encryption: 0
relPath:<null>
type:file
format:qcow2
protocol:none
hostname:<null>

path:ABS_SRCDIR/virstoragetestdata/images/raw
backingStoreRaw: <null>
backingStoreRawFormat: none(0)
capacity: 0
encryption: 0
relPath:raw
type:file
format:raw
protocol:none
hostname:<null>
virstoragetest: Add test cases for QCOW2 files with a protocol name as backing file format QEMU allows and in cases where you omit the not-strictly-needed 'raw' driver on top of raw images automatically uses the protocol name inside of the 'backing file format' field of the qcow2 image. Libvirt expects only format names in that field. Add example images showing this scenario, which will be fixed later. The qcow2 image files in this commit were formatted as: qemu-img create -f qcow2 -F nbd -b nbd+tcp://example.org:6000/blah -u qcow2-protocol-backing-nbd.qcow2 10M and qemu-img create -f qcow2 -F file -b raw qcow2-protocol-backing-file.qcow2 thus using 'nbd' and 'file' as backing format respectively. (note that '-b raw' refers to the file in the example image folder) To satisfy the test, note that the NBD image is also rejected as we can't probe it, thus such configuration would not work. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2023-11-23 19:42:54 +00:00			`path:ABS_SRCDIR/virstoragetestdata/images/qcow2-protocol-backing-file.qcow2`
			`backingStoreRaw: raw`
			`backingStoreRawFormat: <null>(-1)`
			`capacity: 1024`
			`encryption: 0`
			`relPath:<null>`
			`type:file`
			`format:qcow2`
			`protocol:none`
			`hostname:<null>`

			`path:ABS_SRCDIR/virstoragetestdata/images/raw`
			`backingStoreRaw: <null>`
			`backingStoreRawFormat: none(0)`
			`capacity: 0`
			`encryption: 0`
			`relPath:raw`
			`type:file`
			`format:raw`
			`protocol:none`
			`hostname:<null>`