|
From: | Avi Kivity |
Subject: | [Qemu-devel] Re: [PATCH] introduce kvm64 CPU |
Date: | Sun, 23 Aug 2009 12:03:27 +0300 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3 |
On 08/22/2009 12:53 AM, Andre Przywara wrote:
I think this is best left to management software, which has more informationabout 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
[Prev in Thread] | Current Thread | [Next in Thread] |