From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MElPZ-0003dp-LT for qemu-devel@nongnu.org; Thu, 11 Jun 2009 10:37:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MElPV-0003dF-0o for qemu-devel@nongnu.org; Thu, 11 Jun 2009 10:37:49 -0400 Received: from [199.232.76.173] (port=56653 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MElPU-0003d9-Q4 for qemu-devel@nongnu.org; Thu, 11 Jun 2009 10:37:44 -0400 Received: from mx2.redhat.com ([66.187.237.31]:52480) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MElPU-0007i4-8o for qemu-devel@nongnu.org; Thu, 11 Jun 2009 10:37:44 -0400 Message-ID: <4A311639.9040301@redhat.com> Date: Thu, 11 Jun 2009 16:35:37 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/4] Machine config files References: <20090610173803.4674.82538.stgit@wren.home> <4A30FE41.1040907@redhat.com> <200906111418.43669.paul@codesourcery.com> In-Reply-To: <200906111418.43669.paul@codesourcery.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org On 06/11/09 15:18, Paul Brook wrote: > On Thursday 11 June 2009, Gerd Hoffmann wrote: >> 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. Not supporting command line options isn't going to fly. While VM managers probably can and will generate config files, not everybody uses management software. And having to hack the dts and run it through the dtc doesn't look like a reasonable solution for users to me. Also currently qemu lacks an option to specify such dt directly. >> 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). Sure. You still have to link them. > The > details are going to depend how we end up doing the host configuration bits. Ok, sounds like there isn't (yet) a plan. > git://www.jdl.com/software/dtc.git Thanks. cheers, Gerd