Hi, > > We already have qapi schema for -blockdev + -display + -audiodev + > > -chardev, creating a configuration struct which supports these > > shouldn't be that much effort. Then move over QemuOpts one by one. > > chardev-add uses a QAPI type that has too deep nesting to be user > friendly.
Yea, right, it is relatively old and doesn't use stuff like base types which didn't exist back then ... > > Once config file support is complete enough we should be able to offload > > backward compatibility command line parsing to some script which > > transforms the cli into a config file. Which is probably better than > > trying to add -writeconfig to qemu as we don't have to do the string > > processing in C then. > > If we get a launcher script anyway, I would argue that the system > emulator binary written in C should only support JSON (like it already > does) and the script can easily translate from YAML to JSON. That makes sense indeed. cheers, Gerd
