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 10:33:03 +0000 Message-ID: References: <0A882F4D99BBF6449D58E61AAFD7EDD603BB49CB@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: <0A882F4D99BBF6449D58E61AAFD7EDD603BB49CB@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 10:12, "Tian, Kevin" wrote: > I guess it's caused by 18931 to update rombios to latest bochs > version, and some writes to rom area are added outside of disabling > rom write access. But I'm not familiar with this part, and thus hope > others (Akio?) may take a deeper dive. Etherboot likes to try to write to its ROM area. That's why I actually silenced the warning in __hvm_copy(). I would guess the reason you see this issue now is because the accesses are taking the shadow-fault path, which means you are no longer emulating real mode? ;-) Possibly we should silence the shadow code too, at least perhaps while in real mode or for a certain EIP range. -- Keir