All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "Zhai, Edwin" <edwin.zhai@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: PV domain save/restore break
Date: Tue, 10 Apr 2007 10:13:14 +0100	[thread overview]
Message-ID: <C24113BA.D027%keir@xensource.com> (raw)
In-Reply-To: <20070410020504.GB4593@edwin-srv.sh.intel.com>

Our regression tests ran fine on r14773, and our tests include lots of PV
save/restores.

 -- Keir

On 10/4/07 03:05, "Zhai, Edwin" <edwin.zhai@intel.com> wrote:

> I encounter PV domain restore failure on r14770. Are you guys aware of this?
> 
> 
> ========================================================================
> [2007-04-10 09:57:24 4664] DEBUG (balloon:113) Balloon: 754076 KiB free; need
> 65536; done.
> [2007-04-10 09:57:24 4664] DEBUG (XendCheckpoint:220) [xc_restore]:
> /usr/lib/xen/bin/xc_restore 24 4 1 2 0 0 0
> [2007-04-10 09:57:24 4664] INFO (XendCheckpoint:336) xc_domain_restore start:
> p2m_size = 4800
> [2007-04-10 09:57:24 4664] INFO (XendCheckpoint:336) Reloading memory pages:
> 0%
> [2007-04-10 09:57:25 4664] INFO (XendCheckpoint:336) Failed allocation for dom
> 4: 125 extents of order 0
> [2007-04-10 09:57:25 4664] INFO (XendCheckpoint:336) ERROR Internal error:
> Failed to allocate memory for batch.!
> [2007-04-10 09:57:25 4664] INFO (XendCheckpoint:336)
> [2007-04-10 09:57:25 4664] INFO (XendCheckpoint:336) PT L1 race on
> pfn=000003ec mfn=0002e475
> [2007-04-10 09:57:25 4664] INFO (XendCheckpoint:336) Failed allocation for dom
> 4: 49 extents of order 0
> [2007-04-10 09:57:25 4664] INFO (XendCheckpoint:336) ERROR Internal error:
> Failed to allocate memory for batch.!
> [2007-04-10 09:57:25 4664] INFO (XendCheckpoint:336)
> [2007-04-10 09:57:25 4664] INFO (XendCheckpoint:336) Restore exit with rc=1
> [2007-04-10 09:57:25 4664] DEBUG (XendDomainInfo:1652) XendDomainInfo.destroy:
> domid=4
> [2007-04-10 09:57:25 4664] DEBUG (XendDomainInfo:1669)
> XendDomainInfo.destroyDomain(4)
> [2007-04-10 09:57:25 4664] ERROR (XendDomainInfo:1681) XendDomainInfo.destroy:
> xc.domain_destroy failed.
> Traceback (most recent call last):
>   File 
> "/home/gzhai/srcs/hg/tip/dist/install/usr/lib/python/xen/xend/XendDomainInfo.p
> y", line 1675, in destroyDomain
> Error: (3, 'No such process')
> [2007-04-10 09:57:25 4664] ERROR (XendDomain:1086) Restore failed
> Traceback (most recent call last):
>   File 
> "/home/gzhai/srcs/hg/tip/dist/install/usr/lib/python/xen/xend/XendDomain.py",
> line 1081, in domain_restore_fd
>   File 
> "/home/gzhai/srcs/hg/tip/dist/install/usr/lib/python/xen/xend/XendCheckpoint.p
> y", line 224, in restore
>   File 
> "/home/gzhai/srcs/hg/tip/dist/install/usr/lib/python/xen/xend/XendCheckpoint.p
> y", line 324, in forkHelper
> XendError: /usr/lib/xen/bin/xc_restore 24 4 1 2 0 0 0 failed
> 

  reply	other threads:[~2007-04-10  9:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10  2:05 PV domain save/restore break Zhai, Edwin
2007-04-10  9:13 ` Keir Fraser [this message]
2007-04-10  9:40   ` Stephan Creutz
2007-04-10  9:48     ` Keir Fraser
2007-04-10  9:58       ` Stephan Creutz
2007-04-10 10:07         ` Keir Fraser
2007-04-10 12:46           ` Keir Fraser
2007-04-11  8:37             ` Stephan Creutz

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=C24113BA.D027%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=edwin.zhai@intel.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 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.