[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [Solved] the cause of invalid entries in physical-to-machine table

On Thu, 25 Jan 2007 18:53:10 +0100
Stephan Creutz <stephan.creutz@xxxxxxxxxxxxxxxxx> wrote:
> I am currently trying to understand the details of live-migration by
> looking at the code xc_linux_save.c in libxc and writing a simple
> program to make things more clear.
> The program memory maps all mfns which are used for the pfn to mfn
> list, goes through all pfns, resolves each pfn to a mfn and tries to
> memory map each of them to read its content. One thing I noticed are
> invalid physical-to-machine list entries (list entries where the
> resulting mfn equals INVALID_P2M_ENTRY and xc_map_foreign_range
> failes). I wonder what are the possible causes for invalid entries in
> the pfn to mfn list. One cause I can think of are pfns that are
> reserved for Xen itself, but what are the other ones?

I used Xen 3.0.3-1 (which forgot to mention in the original mail). After
Upgrading to version 3.0.4-1 the invalid entries disappeared.


Attachment: pgpPEAJt6Whvc.pgp
Description: PGP signature

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.