Re: KVM usability

[Avi Kivity <avi@redhat.com>]

On 03/09/2010 07:27 PM, Anthony Liguori wrote:
>> Perhaps a json representation of things.  We already have the parser.
>
>
> Please no :-)
>
> We have a config format, QemuOpts ties nicely into it as does qdev.  
> We just need to represent machine information via QemuOpts and tie -m 
> to manipulating the memory assigned to a machine.  IOW, instead of:
>
> (machine_init)(ram_addr_t ram_size,
>                         const char *boot_device,
>                         const char *kernel_filename,
>                         const char *kernel_cmdline,
>                         const char *initrd_filename,
>                         const char *cpu_model)
>
> It should be:
>
> (machine_init)(QemuOpts *opts);
>
> Then we can have a [machine] section in the config where we describe 
> all of these things.

Looks good.

One day we'll read VHDL descriptions of the device model from the 
machine config file and tcg them to host native code, and qemu will be 
pure infrastructure with zero details.

-- 
error compiling committee.c: too many arguments to function