All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	Feng Jin <joe.jin@oracle.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: an issue with 'xm save'
Date: Fri, 21 Sep 2012 17:41:27 +0800	[thread overview]
Message-ID: <505C3647.1030003@oracle.com> (raw)

Hi maintainers,

I found there is an issue when 'xm save' a pvm guest. See below:

When I do save then restore once, CPU(%) in xentop showed around 99%.
When I do that second time, CPU(%) showed 199%

top in dom0 showed:
    PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
   20946 root      18  -2 10984 1284  964 S 19.8  0.3   0:48.93 block
   4939 root      18  -2 10984 1288  964 S 19.5  0.3   1:34.68 block

I could kill the block process, then all look normal again.

xen and xen-tools are both generated with xen-unstable.
I tried xl, but it segfault.
I also tried ovm3.1.1(xen-4.1.2-18.el5.1 and xen-tools-4.1.2-18.el5.1),
can't reproduce.

Did anybody see similar issue before? Any fix already there?
thanks
zduan

             reply	other threads:[~2012-09-21  9:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  9:41 Zhenzhong Duan [this message]
2012-09-21 14:34 ` an issue with 'xm save' Konrad Rzeszutek Wilk
2012-09-26  8:48   ` Zhenzhong Duan
2012-09-26 12:35     ` Konrad Rzeszutek Wilk
2012-09-27  5:58       ` Zhenzhong Duan
2012-09-27 11:59         ` Konrad Rzeszutek Wilk
2012-09-28 10:34           ` Zhenzhong Duan
2012-09-28 14:01             ` Is: Contention in block script when doing guest saving. Was:Re: " Konrad Rzeszutek Wilk
2012-09-28 14:14               ` Ian Jackson
2012-09-28 14:46                 ` Zhenzhong Duan
2012-10-02 14:59                   ` Ian Jackson
2012-10-09  8:53                     ` DuanZhenzhong

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=505C3647.1030003@oracle.com \
    --to=zhenzhong.duan@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=joe.jin@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xen.org \
    /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.