xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>, Michal Novotny <minovotn@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: Xen-unstable save error
Date: Tue, 22 Jun 2010 11:01:26 +0100	[thread overview]
Message-ID: <C8464886.18374%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C2078E202000078000078BB@vpn.id2.novell.com>

On 22/06/2010 07:48, "Jan Beulich" <JBeulich@novell.com> wrote:

>>>> On 22.06.10 at 08:23, Michal Novotny <minovotn@redhat.com> wrote:
>> Jan, as we were solving this with Keir on the list I was unable to save
>> the HVM guest properly and reverting your c/s 21615 helped and with your
>> patch reverted it was working fine. Any idea why there were so type
>> failures for all the pages of HVM guest?
> 
> Not really, and I think you will need to find out by instrumenting the
> hypercall implementation (XEN_DOMCTL_getpageframeinfo{2,3}) -
> really, type failures should only happen for grant frames and I/O
> memory pages (as you can see in the code, for the function to
> report XTAB either the MFN must be invalid, must be a Xen frame,
> or it must be impossible to obtain a reference to the page - all of
> which shouldn't hold for the majority of a HVM guest's pages).

Michal, is it possible you are running new tools against a slightly older
hypervisor? The tools changes had a corresponding, non-version-checked,
modification to a hypercall. Without running the modified hypervisor, HVM
save would indeed behave very oddly!

 -- Keir

  parent reply	other threads:[~2010-06-22 10:01 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
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 [this message]
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=C8464886.18374%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=minovotn@redhat.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).