|
From: | Dor Laor |
Subject: | Re: [Qemu-devel] cpuid problem in upstream qemu with kvm |
Date: | Tue, 22 Dec 2009 15:54:26 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Lightning/1.0pre Thunderbird/3.0 ThunderBrowse/3.2.6.8 |
On 12/22/2009 12:51 AM, john cooper wrote:
Dor Laor wrote:Qemu will check the required cpuid of the cpu model on the host and refuse to load otherwise. When moving to this model, migration can be simplified too since there are fewer combination, and one can choose performance over migration flexibility and wise versa. Due to the above check, the destination qemu won't load if the host does not support its cpu model.If you're referring to the check in my patch, that's currently advisory only. The existing cpu model encoding of CPUID tosses flags in to the soup on speculation they may be available on the host. If not it assumes they will be quietly disabled on their way to the guest along with whatever
why not shout loudly and abort? Do you want windows to reactivate itself?
flags were enabled via +<flag> on the command line. This mixed treatment for model implied vs. user specified flags could be partly an artifact of trying to adapt the legacy qemu64 model to whatever host silicon it finds itself upon. -john
[Prev in Thread] | Current Thread | [Next in Thread] |