libvirt/tests/qemublocktestdata/xml2json/network-nbd-tls.json

{
  "node-name": "node-b-f",
  "read-only": false,
  "driver": "qcow2",
  "file": "node-a-s",
  "backing": null
}
{
  "driver": "nbd",
  "server": {
    "type": "inet",
    "host": "host1.example.com",
    "port": "10809"
  },
  "tls-creds": "node-a-s-tls0",
  "node-name": "node-a-s",
  "auto-read-only": true,
  "discard": "unmap"
}
tests: qemublock: Test NBD with TLS in the JSON generator Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2018-05-30 13:28:24 +00:00			`{`
			`"node-name": "node-b-f",`
			`"read-only": false,`
			`"driver": "qcow2",`
			`"file": "node-a-s",`
			`"backing": null`
			`}`
			`{`
			`"driver": "nbd",`
			`"server": {`
			`"type": "inet",`
			`"host": "host1.example.com",`
			`"port": "10809"`
			`},`
			`"tls-creds": "node-a-s-tls0",`
			`"node-name": "node-a-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,`
tests: qemublock: Test NBD with TLS in the JSON generator Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2018-05-30 13:28:24 +00:00			`"discard": "unmap"`
			`}`