On 08/22/2009 12:53 AM, Andre Przywara wrote:
I think this is best left to management software, which has more
information
about the migration pool.
I believe what we want is an automatic tool that will connect to a
list of machines,and determine which qemu cpu type we should use.
> Doesn't sound like black magic...
I already have such a basic tool. It uses ssh (with pubkey) to connect
to the target machine, then uses dd on /dev/cpu/0/cpuid to get the
CPUID info. This requires cpuid.ko to be loaded and the permissions on
the device file to be sufficient (the appropriate udev patch is
already upstream). It then computes the least common denominator bits
from several machines.
Were you thinking of that approach or do you want to include this host
CPUID functionality into QEMU (somehow embedded in the migration
handler)?
When qemu is involved it is already far too late. This node needs to be
classified when it is added to the cluster.
But maybe we can integrate it into 'qemu -capabilities', if and when
that is added.
--
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
