From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: windows workload: many ept_violation and mmio exits Date: Sun, 28 Aug 2011 10:42:22 +0300 Message-ID: <4E59F15E.6000201@redhat.com> References: <4B17C12B.4020300@linux.vnet.ibm.com> <4B17CC5F.20101@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrew Theurer , kvm@vger.kernel.org To: ya su Return-path: Received: from mx1.redhat.com ([209.132.183.28]:48845 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750926Ab1H1Hms (ORCPT ); Sun, 28 Aug 2011 03:42:48 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 08/26/2011 08:32 AM, ya su wrote: > hi,Avi: > > I met the same problem, tons of hpet vm_exits(vector 209, fault > address is in the guest vm's hpet mmio range), even I disable hpet > device in win7 guest vm, it still produce a larget amount of vm_exits > when trace-cmd ; I add -no-hpet to start the vm, it still has HPET > device inside VM. > > Does that means the HPET device in VM does not depend on the > emulated hpet device in qemu-kvm? Is there any way to disable the VM > HPET device to prevent so many vm_exits? Thansk. > Looks like a bug to me. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.