All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: John Cooper <john.cooper@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Gerd Hoffman <kraxel@redhat.com>, Avi Kivity <avi@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] Introduce global config (v3)
Date: Mon, 25 Jan 2010 11:31:36 +0000	[thread overview]
Message-ID: <20100125113136.GH12739@redhat.com> (raw)
In-Reply-To: <4B5C62EB.1050808@redhat.com>

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 ?


Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2010-01-25 11:31 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 [this message]
2010-01-25 13:59       ` Anthony Liguori
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=20100125113136.GH12739@redhat.com \
    --to=berrange@redhat.com \
    --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.