All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: John Cooper <john.cooper@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, Gerd Hoffman <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] Introduce global config (v3)
Date: Sun, 24 Jan 2010 09:25:56 -0600	[thread overview]
Message-ID: <4B5C6684.3060403@codemonkey.ws> (raw)
In-Reply-To: <4B5C6186.8090806@redhat.com>

On 01/24/2010 09:04 AM, Avi Kivity wrote:
> On 01/24/2010 04:22 PM, Anthony Liguori wrote:
>> This series introduces global config files stored in /etc/qemu.  
>> There is both
>> a common config (qemu.conf) and a per-target config 
>> (target-<TARGET_NAME>.conf).
>>
>> I've removed the default device bits from the series as it requires 
>> some more
>> thought on how to best integrate it.  That makes this series rather 
>> simple.
>
> btw, what does the corresponding patch to our imaginary management 
> tool author guide read?  Do we recommend -nodefconfig or not?  I think 
> we should, since otherwise qemu behaviour can be completely unexpected 
> by the management tool.

It depends.  I think there are two classes of management tools.  The 
first class, like libvirt, completely hides the details of QEMU from the 
user.  For libvirt, it should definitely use -nodefconfig because a user 
should not be encouraged to tweak bits without libvirt knowing about it.

A second class of management tools would work with QEMU and basically 
extend what we currently expose.  IOW, guest's would be represented 
through our native config file, full access would be provided to 
monitor/QMP commands.  For this class of tools, a user should be 
encouraged to use the default configuration files to make global changes 
to a particular node.

Regards,

Anthony Liguori

      parent reply	other threads:[~2010-01-24 15:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 14:22 [Qemu-devel] [PATCH 0/4] Introduce global config (v3) Anthony Liguori
2010-01-24 14:22 ` [Qemu-devel] [PATCH 1/3] Support --sysconfdir in configure to specify path to configuration files (v3) Anthony Liguori
2010-01-24 14:45   ` [Qemu-devel] " Paolo Bonzini
2010-01-24 15:23     ` Anthony Liguori
2010-01-25 14:43       ` Avi Kivity
2010-01-25 21:05         ` Paolo Bonzini
2010-01-25 21:14           ` Anthony Liguori
2010-01-25 21:19             ` Paolo Bonzini
2010-01-26  8:56           ` Avi Kivity
2010-01-24 14:22 ` [Qemu-devel] [PATCH 2/3] Move out option lookup into a separate function Anthony Liguori
2010-01-24 14:22 ` [Qemu-devel] [PATCH 3/3] Load global config files by default (v3) Anthony Liguori
2010-01-24 15:00 ` [Qemu-devel] [PATCH 0/4] Introduce global config (v3) Avi Kivity
2010-01-24 15:23   ` Anthony Liguori
2010-01-24 15:04 ` Avi Kivity
2010-01-24 15:10   ` Paolo Bonzini
2010-01-25 11:31     ` Daniel P. Berrange
2010-01-25 13:59       ` Anthony Liguori
2010-01-24 15:25   ` Anthony Liguori [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B5C6684.3060403@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=john.cooper@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.