3 Commits

Author	SHA1	Message	Date
Daniel P. Berrangé	8851d87556	qemu: use on|off instead of yes|no for -object boolean properties ... QEMU has long accepted many different values for boolean properties, but set accepted has been different depending on which QEMU parser you hit. The on|off values were supported by all QEMU parsers. The yes|no, y|n, true|false values were only partially supported: https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg01012.html Thus we should standardize on on|off everywhere since that is most widely supported in QEMU. Reviewed-by: Peter Krempa <pkrempa@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>	2021-02-16 14:03:13 +00:00
Daniel P. Berrangé	43c9c0859f	qemu: use long on|off syntax for -chardev boolean option values ... The preferred syntax for boolean options is to set the value "on" or "off". QEMU 7.1.0 will deprecate the short format we currently use. The long format has been supported with -chardev since at least 1.5.3, so we don't need to check for it. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>	2021-02-16 12:38:20 +00:00
Peter Krempa	bfe82ec142	tests: qemuxml2argv: Lock in "disk-network-tlsx509-vxhs" case to qemu-5.0.0 ... QEMU 5.1 will drop the vxhs driver. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>	2020-07-31 10:27:51 +02:00