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] 2.0-testing.bk

To: Kip Macy <kmacy@xxxxxxxxxxx>
Subject: Re: [Xen-devel] 2.0-testing.bk
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 25 Jan 2005 22:22:45 +0000
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 25 Jan 2005 22:23:11 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 25 Jan 2005 14:08:43 PST." <20050125140422.B89060@xxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> What changeset should we be up to? I'm currently running 1.1666 which
> you committed yesterday evening.
> 
> Frustrated that xm save for freebsd would give me:
> (XEN) DOM0: (file=memory.c, line=425) Non-privileged attempt to map I/O
> space 00000000

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).

> I tried 'xm save 0 foo' - which I'm not sure should be allowed - and
> saw the following:

There should be a safety catch on this. DOM0 is definitely not
saveable! 

 -- Keir


-------------------------------------------------------
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