Am 25.01.2020 um 11:18 hat Markus Armbruster geschrieben: > Kevin Wolf <kw...@redhat.com> writes: > > > Am 24.01.2020 um 11:27 hat Daniel P. Berrangé geschrieben: > >> This is finally something I'd consider to be on a par with the > >> original QEMU syntax, before we added hierarchical data. You > >> have the minimal possible amount of syntax here. No commas, > >> no quotes, no curly brackets, etc. > > > > This seems to have the same problems as the QEMU command line (how do > > you distinguish strings from ints, from bools, from null?). > > True: YAML provides only string scalars. > > TOML provides strings, integers, floats, booleans, and several flavors > of time. It lacks null. > > > It's > > basically just a pretty-printed version of it with the consequence that > > it needs to be stored in an external file and there is no reasonable way > > to keep it in my shell history. > > There is a reasonable way to keep it in my file system, though. I find > that decidedly superior.
That depends a lot on your use case. If you have a long-lived production VM that you always run with the same configuration, then yes, having a config file for it in the file system is what you probably want. Currently, for this case, people directly using QEMU tend to write a script that contains the command line. I think I do have such scripts somewhere, but their number is very small. My common case is short-lived VMs with configurations that change very often between QEMU invocations. Here the command line is decidedly superior. Requiring me to create a file in the file system each time and to remember deleting it after I'm done feels about as convenient as a *nix shell that doesn't accept parameters for commands on the command line, but instead requires you to write a one-off script first and then run that. Kevin