qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/4] Machine config files


From: Paul Brook
Subject: Re: [Qemu-devel] [PATCH 0/4] Machine config files
Date: Thu, 11 Jun 2009 14:18:43 +0100
User-agent: KMail/1.11.4 (Linux/2.6.29-2-amd64; KDE/4.2.4; x86_64; ; )

On Thursday 11 June 2009, Gerd Hoffmann wrote:
> On 06/10/09 19:38, Paul Brook wrote:
> > The following series implements machine config files, and adds converts
> > some of the existing hardcoded machines.
>
> Hmm.  The converted machine types have a pretty static configuration,
> i.e. where you don't need to specify more that just "-M type" on the
> command line.
>
> What is the plan for machines which can be configured in alot of
> different ways such as a typical PC?  Where you can configure lots of
> details such as cpu, memory, nic, disk drives, ... using command line
> options?

I don't believe most of these things should be configured by commandline 
options. It's only done that way because we don't have any alternative (i.e. a 
machine config file). If you really want full control, I expect your VM 
manager will generate the machine config for you.

> What is the plan for linking host and guest devices (i.e. hook up nics
> to vlans, connect disks to blkdrvstates, ...)?  Right now
> qdev_get_macaddr() does it in a hackish way with a bold FIXME ...

Probably identifying things by name.

As I've said before, I think it's good to isolate machine configuration (what 
hardware to emulate) and host configuration (image location, vlans, etc).  The 
details are going to depend how we end up doing the host configuration bits.

> > The config files themselves are based on the ppc-linux Flattened Device
> > Trees. In generaly I've tried to structure things so that the same config
> > file can be used for both qemu and linux.
>
> Is there Documentation (other than source code) for libftd?  Do you have
> a pointer for me?

git://www.jdl.com/software/dtc.git

Paul




reply via email to

[Prev in Thread] Current Thread [Next in Thread]