From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MEkBB-0002zy-B6 for qemu-devel@nongnu.org; Thu, 11 Jun 2009 09:18:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MEkB5-0002wm-Q0 for qemu-devel@nongnu.org; Thu, 11 Jun 2009 09:18:52 -0400 Received: from [199.232.76.173] (port=55606 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MEkB5-0002wh-KN for qemu-devel@nongnu.org; Thu, 11 Jun 2009 09:18:47 -0400 Received: from mx20.gnu.org ([199.232.41.8]:39847) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MEkB5-00044I-Bq for qemu-devel@nongnu.org; Thu, 11 Jun 2009 09:18:47 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MEkB4-0000iz-H5 for qemu-devel@nongnu.org; Thu, 11 Jun 2009 09:18:46 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 0/4] Machine config files Date: Thu, 11 Jun 2009 14:18:43 +0100 References: <20090610173803.4674.82538.stgit@wren.home> <4A30FE41.1040907@redhat.com> In-Reply-To: <4A30FE41.1040907@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906111418.43669.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Gerd Hoffmann 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