From: Arthur Bergman <abergman@fotango.com>
To: xen-devel@lists.sourceforge.netxen-devel@lists.sourceforge.netxen-devel@lists.sourceforge.net,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Fotango Systems <systems@fotango.com>
Subject: Re: Cannot save/migrate domains
Date: Tue, 1 Feb 2005 20:45:07 +0000 [thread overview]
Message-ID: <cfb22a86cd6652182633939ef3d88088@fotango.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D12365B@liverpoolst.ad.cl.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Hi,
[Switching to process 14149]
0x40026868 in xc_linux_save (xc_handle=8, ioctxt=0xbffff8f0) at
xc_linux_save.c:516
516 if (
!translate_mfn_to_pfn(&pfn_to_mfn_frame_list[i/1024]) ){
(gdb) p mfn_to_pfn_table_start_mfn
$1 = 0
so ... 0
I have read all the public documentation I can find but I cannot seem
to figureout how to build a debugging build of the entire xen, nor how
to caputre the full serial console output. Any pointers would be good.
Thank you very much for such a cool technology.
Cheers
Arthur
-----
CTO @ Fotango Ltd
+447834716919
http://www.fotango.com/
On 1 Feb 2005, at 19:42, Ian Pratt wrote:
>
> Please can you try using a debug build of Xen, and try and capture the
> full serial console output.
>
> It's rather odd that mapping the mfn_to_pfn table is failing. It would
> bne useful to know the value of mfn_to_pfn_table_start_mfn
>
> Thanks,
> Ian
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]
next prev parent reply other threads:[~2005-02-01 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 19:42 Cannot save/migrate domains Ian Pratt
2005-02-01 20:45 ` Arthur Bergman [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 9:27 Arthur Bergman
2005-02-01 17:10 ` Arthur Bergman
2005-02-01 17:14 ` Arthur Bergman
2005-02-01 17:26 ` Arthur Bergman
2005-02-01 17:51 ` Arthur Bergman
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=cfb22a86cd6652182633939ef3d88088@fotango.com \
--to=abergman@fotango.com \
--cc=systems@fotango.com \
--cc=xen-devel@lists.sourceforge.netxen-devel \
/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.