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] Live migration leaves page tables read-only?

To: "John Byrne" <john.l.byrne@xxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Live migration leaves page tables read-only?
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 29 Nov 2006 01:36:45 -0000
Delivery-date: Tue, 28 Nov 2006 17:37:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <456CD0A5.1060701@xxxxxx> <456CD2DC.2020201@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccTTLDn5b65u1dwT7CByCWl2GsASwACgcxw
Thread-topic: [Xen-devel] Live migration leaves page tables read-only?
> I forgot to mention that a very simple test case I wrote using shared
> memory and the mprotect call didn't fail. So, the only test case I
have
> at the moment is to run SAP.

What happens if you use non-live relo?

Also, can you repro on 32b?

Thanks,
Ian

 
> John Byrne
> 
> John Byrne wrote:
> >
> > I have been trying to debug a problem live-migrating SAP on
Xen-3.0.3
> > x86-64 (I also tested Xen-unstable changeset 12548) without success.
> >
> > SAP seems to run fine on a given host; live-migrating it to another
host
> > causes the guest to almost immediately panic in the mprotect() call
in
> > the change_pte_range() routine in the set_pte_at() macro because the
> > page table page it is trying to update is write-protected.
> >
> > My attempts at understanding where this is coming from have come to
> > naught. Any help in running this down would be appreciated. I am
> > perfectly willing/able to write some debugging code if I am given a
few
> > clues what to look for.
> >
> > Thanks,
> >
> > John Byrne
> >
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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