From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH 3/6] add_to_physmap: Move the code for XENMEM_add_to_physmap Date: Mon, 21 Nov 2011 09:39:40 +0100 Message-ID: <20111121083940.GA19892@aepfle.de> References: <20111120132512.GA31844@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: allen.m.kay@intel.com, xen-devel@lists.xensource.com, tim@xen.org, Jean Guyader , JBeulich@suse.com List-Id: xen-devel@lists.xenproject.org On Sun, Nov 20, Keir Fraser wrote: > > Nov 20 06:21:11.744519 (XEN) hvm.c:2312:d1 guest attempted write to read-only > > memory page. gfn=0xc0, mfn=0x201979 > > Is that new behaviour? It may be unrelated to whatever HVM test failure > we're seeing, or else be a mere symptom of a guest gone haywire for other > reasons (we write-protect that memory range because it is supposed to be > ROM). The message does not trigger with changeset 24162, but it does with 24167. Olaf