From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: libvir-list@redhat.com, Jiri Denemark <jdenemar@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [libvirt] Modern CPU models cannot be used with libvirt
Date: Sun, 25 Mar 2012 15:08:52 +0200 [thread overview]
Message-ID: <4F6F18E4.2040905@redhat.com> (raw)
In-Reply-To: <4F6F15D2.8000504@codemonkey.ws>
On 03/25/2012 02:55 PM, Anthony Liguori wrote:
>> If cpu models are not part of configuration they should not be affected
>> by configuration mechanism. You are just avoiding addressing the real
>> question that if asked above.
>
>
> I think you're just refusing to listen.
>
> The stated direction of QEMU, for literally years now, is that we want
> to arrive at the following:
>
> QEMU is composed of a series of objects who's relationships can be
> fully described by an external configuration file. Much of the
> current baked in concepts (like machines) would then become
> configuration files.
>
> qemu -M pc
>
> Would effectively be short hand for -readconfig
> /usr/share/qemu/machines/pc.cfg
In that case
qemu -cpu westmere
is shorthand for -readconfig /usr/share/qemu/cpus/westmere.cfg.
> I think the thread has reduced to: should /usr/share configuration
> files be read by default or just treated as additional configuration
> files.
If they're read as soon as they're referenced, what's the difference?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-03-25 13:09 UTC|newest]
Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 14:54 [Qemu-devel] Modern CPU models cannot be used with libvirt Jiri Denemark
2011-12-15 14:58 ` Anthony Liguori
2011-12-15 15:30 ` Jiri Denemark
2011-12-18 10:07 ` Dor Laor
2011-12-15 15:42 ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2011-12-18 9:58 ` Gleb Natapov
2012-03-09 20:56 ` Eduardo Habkost
2012-03-09 21:04 ` Daniel P. Berrange
2012-03-09 21:15 ` Anthony Liguori
2012-03-10 4:37 ` Eduardo Habkost
2012-03-11 11:45 ` Gleb Natapov
2012-03-10 12:42 ` Daniel P. Berrange
2012-03-10 15:58 ` Eduardo Habkost
2012-03-10 18:24 ` Anthony Liguori
2012-03-10 18:37 ` Andreas Färber
2012-03-10 22:39 ` Doug Goldstein
2012-03-11 0:55 ` Andrew Cathrow
2012-03-11 13:27 ` Gleb Natapov
2012-03-11 14:12 ` Anthony Liguori
2012-03-11 14:56 ` Gleb Natapov
2012-03-11 15:33 ` Anthony Liguori
2012-03-11 16:16 ` Gleb Natapov
2012-03-12 14:48 ` Anthony Liguori
2012-03-12 15:16 ` Eduardo Habkost
2012-03-12 15:49 ` Andreas Färber
2012-03-12 16:50 ` Eduardo Habkost
2012-03-12 17:41 ` Andreas Färber
2012-03-12 17:47 ` Peter Maydell
2012-03-12 17:53 ` Andreas Färber
2012-03-12 17:55 ` Gleb Natapov
2012-03-12 17:59 ` Alexander Graf
2012-03-12 17:52 ` Gleb Natapov
2012-03-12 18:30 ` Eduardo Habkost
2012-03-12 18:42 ` Anthony Liguori
2012-03-12 18:53 ` Itamar Heim
2012-03-12 19:01 ` Anthony Liguori
2012-03-12 19:12 ` Itamar Heim
2012-03-12 19:50 ` Anthony Liguori
2012-03-12 20:00 ` Itamar Heim
2012-03-12 20:19 ` Ayal Baron
2012-03-13 8:32 ` Itamar Heim
2012-03-14 0:11 ` Ayal Baron
2012-03-12 12:52 ` Eduardo Habkost
2012-03-12 13:04 ` Daniel P. Berrange
2012-03-12 13:15 ` Gleb Natapov
2012-03-12 13:32 ` Eduardo Habkost
2012-03-12 13:34 ` Gleb Natapov
2012-03-12 13:50 ` Daniel P. Berrange
2012-03-12 13:53 ` Gleb Natapov
2012-03-12 13:55 ` Daniel P. Berrange
2012-03-12 14:01 ` Gleb Natapov
2012-03-25 13:21 ` Avi Kivity
2012-03-25 13:26 ` Anthony Liguori
2012-03-25 16:06 ` Avi Kivity
2012-03-11 12:41 ` Gleb Natapov
2012-03-11 14:16 ` Anthony Liguori
2012-03-11 15:12 ` Gleb Natapov
2012-03-11 15:41 ` Anthony Liguori
2012-03-11 16:27 ` Gleb Natapov
2012-03-12 13:08 ` Eduardo Habkost
2012-03-13 14:53 ` Eduardo Habkost
2012-03-22 9:32 ` Gleb Natapov
2012-03-22 13:31 ` Eduardo Habkost
2012-03-22 14:30 ` Gleb Natapov
2012-03-22 15:50 ` Eduardo Habkost
2012-03-25 10:19 ` Gleb Natapov
2012-03-25 13:09 ` Anthony Liguori
2012-03-25 14:46 ` Gleb Natapov
2012-03-25 15:06 ` Anthony Liguori
2012-03-25 16:34 ` Gleb Natapov
2012-03-26 16:00 ` Eduardo Habkost
2012-03-22 16:37 ` Anthony Liguori
2012-03-22 17:14 ` Eduardo Habkost
2012-03-22 20:01 ` Anthony Liguori
2012-03-25 9:49 ` Gleb Natapov
2012-03-25 12:55 ` Anthony Liguori
2012-03-25 13:08 ` Avi Kivity [this message]
2012-03-25 13:12 ` Anthony Liguori
2012-03-25 13:14 ` Avi Kivity
2012-03-25 13:22 ` Anthony Liguori
2012-03-25 13:34 ` Avi Kivity
2012-03-25 14:36 ` Anthony Liguori
2012-03-25 14:46 ` Avi Kivity
2012-03-25 14:59 ` Anthony Liguori
2012-03-25 15:16 ` Avi Kivity
2012-03-25 15:26 ` Anthony Liguori
2012-03-25 15:40 ` Avi Kivity
2012-03-25 18:11 ` Anthony Liguori
2012-03-26 9:08 ` Avi Kivity
2012-03-26 9:53 ` Gleb Natapov
2012-03-26 19:03 ` Anthony Liguori
2012-03-28 9:55 ` Avi Kivity
2012-03-26 16:34 ` Eduardo Habkost
2012-03-26 11:24 ` Jiri Denemark
2012-03-26 11:59 ` Avi Kivity
2012-03-26 12:03 ` Gleb Natapov
2012-03-26 16:14 ` Eduardo Habkost
2012-03-26 19:04 ` Anthony Liguori
2012-03-25 14:58 ` Gleb Natapov
2012-03-25 15:07 ` Anthony Liguori
2012-03-25 15:18 ` Avi Kivity
2012-03-25 15:30 ` Anthony Liguori
2012-03-25 15:45 ` Avi Kivity
2012-03-25 18:01 ` Anthony Liguori
2012-03-25 18:09 ` Avi Kivity
2012-03-26 19:00 ` Anthony Liguori
2012-03-28 9:59 ` Avi Kivity
2012-03-20 18:59 ` Eduardo Habkost
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=4F6F18E4.2040905@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=jdenemar@redhat.com \
--cc=libvir-list@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).