From: Kip Macy <kmacy@fsmware.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: 2.0-testing.bk
Date: Tue, 25 Jan 2005 14:26:19 -0800 (PST) [thread overview]
Message-ID: <20050125142403.J89060@demos.bsdclusters.com> (raw)
In-Reply-To: <E1CtZ5B-0006Df-00@mta1.cl.cam.ac.uk>
> 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
next prev parent reply other threads:[~2005-01-25 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 15:00 2.0-testing.bk Nicholas Berry
2005-01-25 15:43 ` 2.0-testing.bk Ian Pratt
2005-01-25 17:39 ` 2.0-testing.bk Paul Larson
2005-01-25 17:45 ` 2.0-testing.bk Keir Fraser
2005-01-25 18:38 ` 2.0-testing.bk Paul Larson
2005-01-25 16:53 ` 2.0-testing.bk Keir Fraser
2005-01-25 22:08 ` 2.0-testing.bk Kip Macy
2005-01-25 22:22 ` 2.0-testing.bk Keir Fraser
2005-01-25 22:26 ` Kip Macy [this message]
2005-01-26 0:01 ` 2.0-testing.bk Kip Macy
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 13:17 2.0-testing.bk Ian Pratt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050125142403.J89060@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.