From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37687) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SBnBx-0006lT-K9 for qemu-devel@nongnu.org; Sun, 25 Mar 2012 09:09:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SBnBv-0000HZ-SG for qemu-devel@nongnu.org; Sun, 25 Mar 2012 09:09:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50573) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SBnBv-0000HO-KU for qemu-devel@nongnu.org; Sun, 25 Mar 2012 09:09:03 -0400 Message-ID: <4F6F18E4.2040905@redhat.com> Date: Sun, 25 Mar 2012 15:08:52 +0200 From: Avi Kivity MIME-Version: 1.0 References: <20120311124116.GI17882@redhat.com> <4F5CB3D1.4050100@codemonkey.ws> <20120311151246.GL17882@redhat.com> <4F5CC7AC.6080703@codemonkey.ws> <20120312130810.GB20654@otherpad.lan.raisama.net> <20120313145319.GD25451@otherpad.lan.raisama.net> <20120322093244.GE22368@redhat.com> <4F6B5553.20601@codemonkey.ws> <20120322171445.GJ25451@otherpad.lan.raisama.net> <4F6B850D.9000505@codemonkey.ws> <20120325094920.GJ22368@redhat.com> <4F6F15D2.8000504@codemonkey.ws> In-Reply-To: <4F6F15D2.8000504@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [libvirt] Modern CPU models cannot be used with libvirt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: libvir-list@redhat.com, Jiri Denemark , Eduardo Habkost , Gleb Natapov , qemu-devel@nongnu.org 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