Re: [Qemu-devel] [PATCH 2/2] qemu-kvm: Add svm cpuid features

["garymberger@gmail.com" <garymberger@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]



Sent from my HTC on the Now Network from Sprint!

----- Reply message -----
From: "Avi Kivity" <avi@redhat.com>
Date: Sun, Sep 12, 2010 6:22 am
Subject: [Qemu-devel] [PATCH 2/2] qemu-kvm: Add svm cpuid features
To: "Alexander Graf" <agraf@suse.de>
Cc: "Joerg Roedel" <joro@8bytes.org>, "Joerg Roedel" <joerg.roedel@amd.com>, "Marcelo Tosatti" <mtosatti@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>


  On 09/12/2010 12:06 PM, Alexander Graf wrote:
>>> For the Phenom type, I honestly don't remember why, but there was also a good reason to add it. In fact, I use it today to have nested virt without -cpu host on hardware that's too new for my guests.
>> Curious, what guests balk at modern hardware but are fine with phenom?
> Sles11 GA ;).

Still curious, how does -cpu host break it?

>>> Either way, I don't think we need a phenom2 type. The features additional are minor enough to not really matter and all use cases I can come up with require either -cpu host (local virt) or -cpu phenom (migration).
>> I'm fine with this (or with adding phenom2).  But don't make phenom contain flags that real phenoms don't have.
> Those were my words :).

Then we are in agreement.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: Type: text/html, Size: 1849 bytes --]