On 01/07/2010 11:40 AM, Dor Laor wrote:
There's no such thing as Nehalem.
Intel were ok with it. Again, you can name is corei7 or
xeon34234234234, I don't care, the principle remains the same.
There are several processors belonging to the Nehalem family and each
have different features.
What's not simple about the above 4 options?
If a qemu/kvm/processor combo doesn't support a feature (say, nx) we
have to remove it from the migration pool even if the Nehalem processor
class says it's included. Or else not admit that combination into the
migration pool in the first place.
What's a better alternative (that insures users understand it and use
it and guest msi and even skype application is happy about it)?
Have management scan new nodes and classify them.
--
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
