From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MEjob-00037i-39
	for qemu-devel@nongnu.org; Thu, 11 Jun 2009 08:55:33 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MEjoW-000340-Ec
	for qemu-devel@nongnu.org; Thu, 11 Jun 2009 08:55:32 -0400
Received: from [199.232.76.173] (port=51599 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MEjoW-00033r-7e
	for qemu-devel@nongnu.org; Thu, 11 Jun 2009 08:55:28 -0400
Received: from mx2.redhat.com ([66.187.237.31]:43537)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1MEjoV-0007uB-LO
	for qemu-devel@nongnu.org; Thu, 11 Jun 2009 08:55:27 -0400
Message-ID: <4A30FE41.1040907@redhat.com>
Date: Thu, 11 Jun 2009 14:53:21 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 0/4] Machine config files
References: <20090610173803.4674.82538.stgit@wren.home>
In-Reply-To: <20090610173803.4674.82538.stgit@wren.home>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org

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?

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 ...

> 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?

Guess I have to dive into the libftd to get a more clear picture how all 
this is supposed to work together ...

cheers,
   Gerd