From: Michal Novotny <minovotn@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: Xen-unstable save error
Date: Mon, 21 Jun 2010 16:50:09 +0200 [thread overview]
Message-ID: <4C1F7C21.30802@redhat.com> (raw)
In-Reply-To: <C8453060.18121%keir.fraser@eu.citrix.com>
On 06/21/2010 04:06 PM, Keir Fraser wrote:
> On 21/06/2010 15:02, "Michal Novotny"<minovotn@redhat.com> wrote:
>
>
>> Ok Keir, but what I don't understand is why there's nothing in
>> `/local/domain/%d/device/suspend/event-channel`. So this is OK?
>>
> Yes that's okay. The guest writes that location only If it supports the new
> event-channel notification method for suspend.
>
>
>> For the restore functionality:
>>
>> # ls -ahl rhel5-32fv.sav
>> -rwxr-xr-x 1 root root 53M Jun 21 2010 rhel5-32fv.sav
>>
> Okay, yeah, if the guest really has 1G of memory allocated to it at the time
> of the save, then something has gone wrong on the save side. But no errors
> were apparent on the save side, apart from that event-channel port warning
> which is benign? That's weird.
>
> -- Keir
>
>
>
Well, I see what's going on now but I had to turn on the debug flag now.
According to the code, this is what's being hit per almost each page and
MFN:
...
if ( pfn_type[j] == XEN_DOMCTL_PFINFO_XTAB )
{
printf("type fail: page %i mfn %08lx\n", j, gmfn);
continue;
}
...
Xend.log is having many occurences of type failures:
[2010-06-21 16:48:53 10573] DEBUG (XendCheckpoint:381) type fail: page
414 mfn 0000659e
[2010-06-21 16:48:53 10573] DEBUG (XendCheckpoint:129) In
saveInputHandler type fail: page 414 mfn 0000659e
[2010-06-21 16:48:53 10573] DEBUG (XendCheckpoint:381) type fail: page
415 mfn 0000659f
[2010-06-21 16:48:53 10573] DEBUG (XendCheckpoint:129) In
saveInputHandler type fail: page 415 mfn 0000659f
[2010-06-21 16:48:53 10573] DEBUG (XendCheckpoint:381) type fail: page
416 mfn 000065a0
[2010-06-21 16:48:53 10573] DEBUG (XendCheckpoint:129) In
saveInputHandler type fail: page 416 mfn 000065a0
Well, did somebody hit those save issues or similar?
Thanks,
Michal
--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat
next prev parent reply other threads:[~2010-06-21 14:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 11:15 Xen-unstable save error Michal Novotny
2010-06-21 12:05 ` Keir Fraser
2010-06-21 12:38 ` Michal Novotny
2010-06-21 12:44 ` Keir Fraser
2010-06-21 12:47 ` Michal Novotny
2010-06-21 12:56 ` Keir Fraser
2010-06-21 13:10 ` Michal Novotny
2010-06-21 13:11 ` Keir Fraser
2010-06-21 12:57 ` Michal Novotny
2010-06-21 13:08 ` Keir Fraser
2010-06-21 13:18 ` Michal Novotny
2010-06-21 13:24 ` Keir Fraser
2010-06-21 13:37 ` Michal Novotny
2010-06-21 13:45 ` Keir Fraser
2010-06-21 14:02 ` Michal Novotny
2010-06-21 14:06 ` Keir Fraser
2010-06-21 14:09 ` Michal Novotny
2010-06-21 14:50 ` Michal Novotny [this message]
2010-06-21 17:57 ` Keir Fraser
2010-06-22 5:38 ` Michal Novotny
2010-06-22 5:58 ` Keir Fraser
2010-06-22 6:23 ` Michal Novotny
2010-06-22 6:48 ` Jan Beulich
2010-06-22 6:51 ` Keir Fraser
2010-06-22 7:12 ` Jan Beulich
2010-06-22 7:36 ` Keir Fraser
2010-06-22 7:38 ` Michal Novotny
2010-06-22 10:01 ` Keir Fraser
2010-06-22 10:05 ` Michal Novotny
2010-06-22 10:23 ` Keir Fraser
2010-06-22 10:53 ` Michal Novotny
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=4C1F7C21.30802@redhat.com \
--to=minovotn@redhat.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).