On 23 February 2011 16:01, Anthony Liguori <anth...@codemonkey.ws> wrote:
> Yes.   I view the command line as optional.  To me, this is the ideal
> interaction:
>
> 1) start qemu with an empty stateful config file
>
> 2) issue monitor commands to create all devices and backends
>
> 3) the stateful config file totally captures the state of all of the issued
> QMP commands.  The management tool can relaunch the guest just by passing
> the stateful config file to QEMU.
>
> 4) when the management tool needs to "extract" a config file, it can read
> the stateful config (through the monitor) and generate it's own config.
>
> 5) the management tool should treat the stateful config file as more or less
> opaque.  It shouldn't be visible to end user.
>
> In the non-managed case, users should interact directly with the config
> file.

For the typical TCG use case, that sounds a whole lot worse than
the current situation of "just run qemu with a suitable command
line"...

-- PMM

Reply via email to