On 01/26/2010 04:32 PM, Anthony Liguori wrote:
It would need to know which cpuid bits qemu supports. Only qemu
knows that.
I'm not sure I understand why. Can you elaborate?
If qemu doesn't recognize -cpu qemu64,+nx, then no amount of hardware
and kvm.ko support will allow the user to enable nx in a guest.
Does -cpu host filter out flags that we don't know about? I'm pretty
sure it doesn't. Since we're planning on moving to -cpu host by
default for KVM, does it really matter?
People who use discovery tools are probably setting up a migration
cluster. They aren't going to use -cpu host.
Oh, I was under the impression that the tool was meant to be software
agnostic. IOW, here are all the virt features your hardware supports.
That's /proc/cpuinfo, we should just extend it, maybe that's what Alex
meant, but I'd like to see something more capable.
--
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
