qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	John Cooper <john.cooper@redhat.com>,
	qemu-devel@nongnu.org, Gerd Hoffman <kraxel@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] Introduce global config (v3)
Date: Mon, 25 Jan 2010 07:59:28 -0600	[thread overview]
Message-ID: <4B5DA3C0.1030604@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100125113136.GH12739@redhat.com>

On 01/25/2010 05:31 AM, Daniel P. Berrange wrote:
> On Sun, Jan 24, 2010 at 04:10:35PM +0100, Paolo Bonzini wrote:
>    
>> On 01/24/2010 04:04 PM, 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.
>>>        
>> I think so, the next version of libvirt will use -nodefaults, and
>> -nodefconfig is in the same group.
>>      
> It sounds like we need to add -nodefconfig too, unless -nodefaults will
> automatically imply  -nodefconfig too ?
>    

Right now, -nodefaults does not imply -nodefconfig.

Regards,

Anthony Liguori

> Daniel
>    

  reply	other threads:[~2010-01-25 13:59 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 [this message]
2010-01-24 15:25   ` Anthony Liguori

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=4B5DA3C0.1030604@linux.vnet.ibm.com \
    --to=aliguori@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=berrange@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).