libvirt/tests/qemublocktestdata/xml2json/dir-fat-floppy.json

{
  "node-name": "node-f",
  "read-only": true,
  "driver": "raw",
  "file": "node-s"
}
{
  "driver": "vvfat",
  "dir": "/var/somefiles",
  "floppy": true,
  "rw": false,
  "node-name": "node-s",
  "auto-read-only": true,
  "discard": "unmap"
}
tests: qemublock: Add test-case for the 'vvfat' driver in qemu Test mapping of the 'FAT' disk format to 'vvfat' in qemu. The top level disk image would generate the following '-drive' cmdline: dir-fat-readonly.xml: -drive file=fat:/var/somefiles,if=none,id=drive-dummy,readonly=on -device virtio-blk-pci,scsi=off,drive=drive-dummy,id=dummy dir-fat-floppy.xml -drive file=fat:floppy:/var/somefiles,if=none,id=drive-dummy,readonly=on Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: John Ferlan <jferlan@redhat.com> 2018-03-19 07:00:19 +00:00			`{`
			`"node-name": "node-f",`
			`"read-only": true,`
			`"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 11:54:12 +00:00			`"file": "node-s"`
			`}`
			`{`
			`"driver": "vvfat",`
			`"dir": "/var/somefiles",`
			`"floppy": true,`
			`"rw": false,`
			`"node-name": "node-s",`
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 17:29:10 +00: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 11:54:12 +00:00			`"discard": "unmap"`
tests: qemublock: Add test-case for the 'vvfat' driver in qemu Test mapping of the 'FAT' disk format to 'vvfat' in qemu. The top level disk image would generate the following '-drive' cmdline: dir-fat-readonly.xml: -drive file=fat:/var/somefiles,if=none,id=drive-dummy,readonly=on -device virtio-blk-pci,scsi=off,drive=drive-dummy,id=dummy dir-fat-floppy.xml -drive file=fat:floppy:/var/somefiles,if=none,id=drive-dummy,readonly=on Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: John Ferlan <jferlan@redhat.com> 2018-03-19 07:00:19 +00:00			`}`