On 8/14/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> (अमेय) Ameya (पाळंदे) Palande wrote:
> > Hi Avi,
> >
> > I followed your steps for modifying vmx.c
> > Here are the messages from dmesg output :
> >
> > kvm: EIO at 852 kvm: EIO at 882 kvm: EIO at 980
> >
> >
>
> Sheng, this looks like one of the vmx compatibility patches. Can you
> take a look?
>
> Basically, it seems kvm-34 breaks on all Core cpus (not Core 2).
>
>
I got the same behaviour here, and it seems that the reason is 32-bit
machines does not use the CR8 register. But the code in vmx.c makes it
a minimum requirement as in:
min = CPU_BASED_HLT_EXITING |
CPU_BASED_CR8_LOAD_EXITING |
CPU_BASED_CR8_STORE_EXITING |
CPU_BASED_USE_IO_BITMAPS |
CPU_BASED_MOV_DR_EXITING |
CPU_BASED_USE_TSC_OFFSETING;
I think the solution is to enclose the CR8 constants in a ifdef
CONFIG_X86_64, since putting them as optional won't do the right thing
in 64-bit (and thus, core duo), machines.
I was about to post a patch for it now.
Avi, if you agree with the fix, I can do it right now.
--
Glauber de Oliveira Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
