WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] guest attempted write to read-only memory page.

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] guest attempted write to read-only memory page.
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 22 Dec 2008 10:33:03 +0000
Cc: 'Akio Takebe' <takebe_akio@xxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Dec 2008 02:33:03 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <0A882F4D99BBF6449D58E61AAFD7EDD603BB49CB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclkHdhNymC5crU+TeGYz4yjUsNejgAAtLZC
Thread-topic: [Xen-devel] guest attempted write to read-only memory page.
User-agent: Microsoft-Entourage/12.14.0.081024
On 22/12/2008 10:12, "Tian, Kevin" <kevin.tian@xxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel