All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	Feng Jin <joe.jin@oracle.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: an issue with 'xm save'
Date: Wed, 26 Sep 2012 16:48:42 +0800	[thread overview]
Message-ID: <5062C16A.1020306@oracle.com> (raw)
In-Reply-To: <20120921143430.GA3522@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 1799 bytes --]

Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 21, 2012 at 05:41:27PM +0800, Zhenzhong Duan wrote:
>    
>> 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.
>>      
>
> What is the 'block' process? If you attach 'perf' to it do you get an idea
> of what it is spinning at?
>    
It's /etc/xen/scripts/block
I add 'set -x' to /etc/xen/scripts/block, found it blocked at claim_lock.
When domU was created first time, claim_lock/release_lock finished quickly,
when 'xm save' was called, claim_lock spin in its own while loop.
I can ensure no other domU create/save/etc happen when I test.
>    
>> xen and xen-tools are both generated with xen-unstable.
>> I tried xl, but it segfault.
>>      
>
> It segfaulted? When doing 'xl save'  or 'xl resume'? Or just allocating
> the guest?
>    
When xl create vm.cfg
>    
>> 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.
>>      
>
> So the issue is only present with Xen-unstable?
>    
Yes,  I found in /etc/xen/scripts/locking.sh of ovm3.1.1, func 
claim_lock is quite different to xen-unstable
Maybe this is why ovm3.1.1 work with save/restore.
> Did you clear _any_ older Xen libraries/tools when you installed Xen-unstable?
>    
No, I built xen and xen-tools on el5, then installed to ovm3.1.1 on 
other partition.
thanks
zduan

[-- Attachment #1.2: Type: text/html, Size: 2850 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-09-26  8:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  9:41 an issue with 'xm save' Zhenzhong Duan
2012-09-21 14:34 ` Konrad Rzeszutek Wilk
2012-09-26  8:48   ` Zhenzhong Duan [this message]
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=5062C16A.1020306@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.