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: Gerd Hoffmann
Subject: Re: [Qemu-devel] [PATCH 0/4] Machine config files
Date: Thu, 11 Jun 2009 16:35:37 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2

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





reply via email to

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