xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Michal Novotny <minovotn@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: Re: Xen-unstable save error
Date: Tue, 22 Jun 2010 07:38:48 +0200	[thread overview]
Message-ID: <4C204C68.1080803@redhat.com> (raw)
In-Reply-To: <C8456690.181EA%keir.fraser@eu.citrix.com>

On 06/21/2010 07:57 PM, Keir Fraser wrote:
> On 21/06/2010 15:50, "Michal Novotny"<minovotn@redhat.com>  wrote:
>
>    
>> 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:
>>      
> Hm, well I just saved/restored a 750MB PV guest and a 750MB HVM guest okay
> with xen-unstable tip. However I think the above type-checking code may only
> have been introduced for HVM guests as of Jan Beulich's recent changeset
> 21615. If your guest is an HVM guest, perhaps this changeset is to blame? I
> would suggest reverting it and re-testing. I've cc'ed Jan in case he can
> comment on the info you've given.
>    

Keir,
you were right about the c/s 21615. I did try reverting it and it was 
working fine to both save and restore when I was having this patch reverted.

Michal

-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

  reply	other threads:[~2010-06-22  5:38 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 [this message]
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=4C204C68.1080803@redhat.com \
    --to=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).