libvirt/tests/qemublocktestdata/xml2json/file-raw-noopts.json

{
  "node-name": "0123456789ABCDEF0123456789ABCDE",
  "read-only": false,
  "driver": "raw",
  "file": "0123456789ABCDEF0123456789ABCDE"
}
{
  "driver": "file",
  "filename": "/var/lib/libvirt/images/i.img",
  "node-name": "0123456789ABCDEF0123456789ABCDE",
  "auto-read-only": true,
  "discard": "unmap"
}
tests: qemublock: Add basic 'raw' file test Test the JSON props generator with a very simple 'raw' image with no other options. The node-names for the image are 31 bytes long so that we validate our node name detector. The top level disk image would generate the following '-drive' cmdline: -drive file=/var/lib/libvirt/images/i.img,format=raw,if=none,id=drive-dummy -device virtio-blk-pci,scsi=off,drive=drive-dummy,id=dummy Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: John Ferlan <jferlan@redhat.com> 2018-03-28 09:40:03 +02:00			`{`
			`"node-name": "0123456789ABCDEF0123456789ABCDE",`
			`"read-only": false,`
			`"driver": "raw",`
qemu: block: Don't nest storage layer properties into format layer Reference the storage via node name rather than inlining it. This is the approach that will be used with -blockdev/blockdev-add since it allows more control and is more future proof. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: John Ferlan <jferlan@redhat.com> 2018-05-14 13:54:12 +02:00			`"file": "0123456789ABCDEF0123456789ABCDE"`
			`}`
			`{`
			`"driver": "file",`
			`"filename": "/var/lib/libvirt/images/i.img",`
			`"node-name": "0123456789ABCDEF0123456789ABCDE",`
qemu: block: Use 'auto-read-only' instead of 'read-only' for backing chain To allow using -blockdev with blockjobs QEMU needs to reopen files in read-write mode when modifying the backing chain. To achieve this we need to use 'auto-read-only' for the backing files rather than the normal 'read-only' property. That way qemu knows that the files need to be reopened. Note that the format drivers (e.g. qcow2) are still opened with the read-only property enabled when being a member of the backing chain since they are supposed to be immutable unless a block job is started. QEMU v4.0 (since commit 23dece19da4) allows also dynamic behaviour for auto-read-only which allows us to use sVirt as we only grant write permissions to files when doing a blockjob. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2018-09-04 19:29:10 +02:00			`"auto-read-only": true,`
qemu: block: Don't nest storage layer properties into format layer Reference the storage via node name rather than inlining it. This is the approach that will be used with -blockdev/blockdev-add since it allows more control and is more future proof. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: John Ferlan <jferlan@redhat.com> 2018-05-14 13:54:12 +02:00			`"discard": "unmap"`
tests: qemublock: Add basic 'raw' file test Test the JSON props generator with a very simple 'raw' image with no other options. The node-names for the image are 31 bytes long so that we validate our node name detector. The top level disk image would generate the following '-drive' cmdline: -drive file=/var/lib/libvirt/images/i.img,format=raw,if=none,id=drive-dummy -device virtio-blk-pci,scsi=off,drive=drive-dummy,id=dummy Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: John Ferlan <jferlan@redhat.com> 2018-03-28 09:40:03 +02:00			`}`