|
From: | Avi Kivity |
Subject: | [Qemu-devel] Re: KVM call agenda for Jan 26 |
Date: | Tue, 26 Jan 2010 16:37:07 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1 |
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
[Prev in Thread] | Current Thread | [Next in Thread] |