From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35262) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S74vo-0005yE-2q for qemu-devel@nongnu.org; Mon, 12 Mar 2012 09:05:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S74vP-00014r-CL for qemu-devel@nongnu.org; Mon, 12 Mar 2012 09:04:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:23731) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S74vP-00014P-44 for qemu-devel@nongnu.org; Mon, 12 Mar 2012 09:04:31 -0400 Date: Mon, 12 Mar 2012 13:04:19 +0000 From: "Daniel P. Berrange" Message-ID: <20120312130419.GF20867@redhat.com> References: <20111218095816.GG21664@redhat.com> <20120309205652.GA6807@otherpad.lan.raisama.net> <20120309210403.GA2319@redhat.com> <20120310124246.GA4408@redhat.com> <20120310155843.GJ2914@otherpad.lan.raisama.net> <4F5B9C6F.3050705@codemonkey.ws> <20120311132755.GJ17882@redhat.com> <4F5CB2EA.10000@codemonkey.ws> <20120312125227.GA20654@otherpad.lan.raisama.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20120312125227.GA20654@otherpad.lan.raisama.net> Subject: Re: [Qemu-devel] [libvirt] Modern CPU models cannot be used with libvirt Reply-To: "Daniel P. Berrange" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: Gleb Natapov , libvir-list@redhat.com, qemu-devel@nongnu.org, Avi Kivity , Anthony Liguori , Jiri Denemark , "arch@ovirt.org" On Mon, Mar 12, 2012 at 09:52:27AM -0300, Eduardo Habkost wrote: > On Sun, Mar 11, 2012 at 09:12:58AM -0500, Anthony Liguori wrote: > > On 03/11/2012 08:27 AM, Gleb Natapov wrote: > > >On Sat, Mar 10, 2012 at 12:24:47PM -0600, Anthony Liguori wrote: > > >>Let's step back here. > > >> > > >>Why are you writing these patches? It's probably not because you > > >>have a desire to say -cpu Westmere when you run QEMU on your laptop. > > >>I'd wager to say that no human has ever done that or that if they > > >>had, they did so by accident because they read documentation and > > >>thought they had to. > > No, it's because libvirt doesn't handle all the tiny small details > involved in specifying a CPU. All libvirty knows about are a set of CPU > flag bits, but it knows nothing about 'level', 'family', and 'xlevel', > but we would like to allow it to expose a Westmere-like CPU to the > guest. This is easily fixable in libvirt - so for the point of going discussion, IMHO, we can assume libvirt will support level, family, xlevel, etc. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|