From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: KVM x86: Infinite loop on updating accessed bit in r/o page table Date: Mon, 24 Feb 2014 19:29:38 +0100 Message-ID: <530B8F92.50202@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To: kvm Return-path: Received: from david.siemens.de ([192.35.17.14]:46039 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750899AbaBXS3k (ORCPT ); Mon, 24 Feb 2014 13:29:40 -0500 Received: from mail1.siemens.de (localhost [127.0.0.1]) by david.siemens.de (8.14.3/8.14.3) with ESMTP id s1OITcUM024807 for ; Mon, 24 Feb 2014 19:29:38 +0100 Received: from mchn199C.mchp.siemens.de ([139.25.40.156]) by mail1.siemens.de (8.14.3/8.14.3) with ESMTP id s1OITbN1025762 for ; Mon, 24 Feb 2014 19:29:38 +0100 Sender: kvm-owner@vger.kernel.org List-ID: Hi, I noticed that KVM (with VMX at least) enters an inifite loop of vmentries and ept-violations when it has to set the accessed bit in a guest page table that is in read-only memory (namely: the F-segment of the BIOS). I don't think this is the proper reaction... Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux