From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: guest attempted write to read-only memory page. Date: Mon, 22 Dec 2008 13:42:39 +0000 Message-ID: References: <0A882F4D99BBF6449D58E61AAFD7EDD603BB49CE@pdsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0A882F4D99BBF6449D58E61AAFD7EDD603BB49CE@pdsmsx502.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" , "xen-devel@lists.xensource.com" Cc: 'Akio Takebe' List-Id: xen-devel@lists.xenproject.org On 22/12/2008 13:20, "Tian, Kevin" wrote: >> Should we move disable action to post rom_scan? If shadow warning >> is simply silenced for such case, it seems breaking the purpose of >> disable_dom_write_access... >> > > I make a quick test, that warning disappears after moving disable > action post rom_scan. But I haven't found the place triggering such > write violation, as in previous revision write access is also disabled > before rom_scan. It could come from recent bochs update on > expansion rom part by 18931. Yes, I can repro the warnings. They are due to the vm86 acceleration changes. -- Keir