centos 5.x on kvm-83 doesnt think pentium pro has fast system calls

Why wouldn't SEP be recognized by kvm-83 running a centos 5.x guest on a ppro? Steven -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

sysenter msrs dont vm exit on kvm-83

i'm running kvm-83 wrapped around a linux-2.6.24 x86. i dont see vm exits for rdmsr or wrmsr on the sysenter msrs (0x174 - 0x176) but do for the range (0x200 - 0x2ff). it does *not* seem to involve the msr bitmap (it doesnt seem to matter whether the msr bitmap is set or not set, enabled or

Re: handle_wrmsr behavior under kvm-83

- Original Message - From: Avi Kivity a...@redhat.com To: Steven Stovall sstov...@neuraliq.com Cc: kvm kvm@vger.kernel.org Sent: Monday, February 2, 2009 8:27:07 AM GMT -08:00 US/Canada Pacific Subject: Re: handle_wrmsr behavior under kvm-83 Steven Stovall wrote: When looking

Re: handle_wrmsr behavior under kvm-83

- Original Message - From: Avi Kivity a...@redhat.com To: Steven Stovall sstov...@neuraliq.com Cc: kvm kvm@vger.kernel.org Sent: Monday, February 2, 2009 8:27:07 AM GMT -08:00 US/Canada Pacific Subject: Re: handle_wrmsr behavior under kvm-83 Steven Stovall wrote: When looking

handle_wrmsr behavior under kvm-83

When looking at the EXIT_REASON_MSR_WRITE events that trigger handle_wrmsr() invocations, why do I only seem to see indices for MSR_MTRRfix* (0x250 - 0x2ff)? This behavior seems to have changed since kvm-60, where I would see for example SYSENTER MSR writes. Steven -- To unsubscribe from this

Re: Pending signals prevent entry to the guest

Thanks for the feedback. My problem turned out to be a mere misconfiguration propagated by a dubious provenance :-) Steven - Original Message - From: Dor Laor dl...@redhat.com To: Steven Stovall sstov...@neuraliq.com Cc: kvm kvm@vger.kernel.org Sent: Wednesday, January 21, 2009 4:14:32

Pending signals prevent entry to the guest

I posted about a week ago regarding a very different behavior with a host-side app vis a vis kvm-77 vs kvm-33. Pending signals (SIGIO and SIGALRM) never seem to be dequeued so that I never kvm_guest_enter()...it appears that only the dynticks alarm_timer gets enabled which only handles SIGALRM,

is vmx_vcpu_run deprecated in kvm-77?

I am porting an app from kvm-33 to kvm-77 (the app is also known to work on kvm-60 i believe). But so far I havent seen a KVM_EXIT_IO, only KVM_EXIT_INTRs. This means the app never changes state. Also, I never see vmx_vcpu_run called -- does x86/x86.c:__vcpu_run deprecate it? steven -- To