From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: kvm ivy bridge support? Date: Thu, 04 Dec 2014 16:36:02 +0100 Message-ID: <54807F62.5040709@redhat.com> References: <20141204113059.GA3006@ywang-linux> <20141204121709.6193305.9217.1941@tetrioncapital.com> <5480679E.20209@redhat.com> <20141204135605.6193305.66560.1954@tetrioncapital.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: kvm To: tlau@tetrioncapital.com, Yong Wang Return-path: Received: from mx1.redhat.com ([209.132.183.28]:34881 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754127AbaLDPgK (ORCPT ); Thu, 4 Dec 2014 10:36:10 -0500 In-Reply-To: <20141204135605.6193305.66560.1954@tetrioncapital.com> Sender: kvm-owner@vger.kernel.org List-ID: On 04/12/2014 14:56, tlau@tetrioncapital.com wrote: > Interesting, is it depending on KVM or libvirt on CPU support? It has to be supported all the way up. KVM provides emulation, QEMU provides command-line parsing, libvirt provides XML parsing, virt-manager probably can read the info from libvirt but I'm not 100% sure. Paolo > Sent from my BlackBerry 10 smartphone. > Original Message > From: Paolo Bonzini > Sent: Thursday, 4 December, 2014 9:54 PM > To: tlau@tetrioncapital.com; Yong Wang > Cc: kvm > Subject: Re: kvm ivy bridge support? > > > > On 04/12/2014 13:17, tlau@tetrioncapital.com wrote: >> Nothing really specific, when I use virt-manager, on CPU type it >> doesn't have Ivy Bridge selection, I just wondering why. > > Either your virt-manager or your libvirt or your QEMU are too old. > Kernel 3.17 supports up to Broadwell. > > Paolo >