From: Paolo Bonzini <pbonzini@redhat.com>
To: tlau@tetrioncapital.com, Yong Wang <yong.y.wang@linux.intel.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: kvm ivy bridge support?
Date: Thu, 04 Dec 2014 16:36:02 +0100 [thread overview]
Message-ID: <54807F62.5040709@redhat.com> (raw)
In-Reply-To: <20141204135605.6193305.66560.1954@tetrioncapital.com>
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
>
next prev parent reply other threads:[~2014-12-04 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 9:04 kvm ivy bridge support? Thomas Lau
2014-12-04 11:30 ` Yong Wang
2014-12-04 12:17 ` tlau
2014-12-04 13:54 ` Paolo Bonzini
2014-12-04 13:56 ` tlau
2014-12-04 15:36 ` Paolo Bonzini [this message]
2014-12-05 1:33 ` tlau
2014-12-05 7:29 ` Paolo Bonzini
2014-12-05 8:17 ` Thomas Lau
2014-12-05 15:23 ` Rik van Riel
2014-12-05 16:54 ` Paolo Bonzini
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=54807F62.5040709@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=tlau@tetrioncapital.com \
--cc=yong.y.wang@linux.intel.com \
/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.