> Probably some structure not set up correctly -- my guess might be the
> phys-to-machine mapping info that is supposed to get poked into the
> shared_info page by the unprivileged guest. It is a list of the page
> frames that make up the guest's p2m table. If you haven't init'ed it
> then the xm_save tool will probably try to map NULL and hence the
> error (Xen has low 1MB of memory marked as being an I/O page).
Thanks. I'll look there. I assumed it was looking at the page tables
themselves (which shouldn't be a problem because xen shouldn't allow it
in the first place.
> There should be a safety catch on this. DOM0 is definitely not
> saveable!
I would think not - but it doesn't appear to realize that ;-).
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel