[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] cpuid problem in upstream qemu with kvm
From: |
Lennart Sorensen |
Subject: |
Re: [Qemu-devel] cpuid problem in upstream qemu with kvm |
Date: |
Wed, 6 Jan 2010 11:19:35 -0500 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Tue, Jan 05, 2010 at 06:10:10PM -0600, Anthony Liguori wrote:
> Typically, there is at least a little sanity naming for these cases.
> For instance, any Xeon W35xx should have the same features. A Xeon
> W55xx may be different.
It doesn't work that way for intel. For example:
Core 2 Duo E7400 AT80571PH0723M does not have VT support.
Core 2 Duo E7400 AT80571PH0723ML does have VT support.
Good luck buying the variant you want. So model names do not define
the feature set.
> It's not going to be easy to include every possible model. It's a hard
> problem for management tools too. The thing is, I imagine most
> management tools are going to cat /proc/cpuinfo to get what the
> processor is and that's going to be a Xeon YYXXXX type name so I really
> believe that's the thing that makes sense to expose in QEMU.
>
> Maybe we could name models like IntelXeonW35xx.
>
> Clever use of the preprocessor will make this effort much, much saner.
> Also, we really need some sort of human readable document that explains
> the differences between processor classes and makes recommendations
> about what management tools should take into consideration.
--
Len Sorensen
Re: [Qemu-devel] cpuid problem in upstream qemu with kvm, Daniel P. Berrange, 2010/01/06
Re: [Qemu-devel] cpuid problem in upstream qemu with kvm,
Lennart Sorensen <=