All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: sanjay kushwaha <sanjay.kushwaha@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Live vm migration broken in latest xen-unstable
Date: Thu, 07 Sep 2006 11:28:26 +0900	[thread overview]
Message-ID: <44FF83CA.7020207@lab.ntt.co.jp> (raw)
In-Reply-To: <2717599f0609051209s6a7e80baxefa99ba1909fff2c@mail.gmail.com>

sanjay kushwaha wrote:
> Hi Ewan,
> I did a "hg pull -u" on my tree which also got the changeset 11422. but 
> I am
> still facing the same problem. btw this changeset seems to be specific to
> hvm domain while I am facing this problem with paravirtualized domain.
> 
> Thanks,
> Sanjay

I've tested live migration with paravirt domain for changeset 11429,
but didn't have such a problem.
Did you also rebuild xen and dom0 kernel after you updated the repository?
If not, I would recommend to do so.

Yoshi Tamura

> 
> On 9/5/06, Ewan Mellor <ewan@xensource.com> wrote:
>>
>> On Fri, Sep 01, 2006 at 05:36:00PM -0400, sanjay kushwaha wrote:
>>
>> > Folks,
>> > I am experiencing that live migration is not working in latest
>> > xen-unstable. I get the following message during migration
>> >
>> > [root@pc5 ksanjay]# xm migrate --live 1 [1]199.77.138.23
>> > Error: /usr/lib/xen/bin/xc_save 18 1 0 0 1 failed
>> > [root@pc5 ksanjay]#
>> >
>> > I traced the problem to a function in xen named set_sh_allocation() in
>> > file xen/arch/x86/mm/shadow/common.c
>> >
>> > tools/libxc/xc_linux_save.c:xc_linux_save() is called from the python
>> > script which makes the following hypercall
>> >
>> >     if (live) {
>> >         if (xc_shadow_control(xc_handle, dom,
>> >                               XEN_DOMCTL_SHADOW_OP_ENABLE_LOGDIRTY,
>> >                               NULL, 0, NULL, 0, NULL) < 0) {
>> >             ERR("Couldn't enable shadow mode");
>> >             goto out;
>> >         }
>> >         last_iter = 0;
>> >     } else {
>> > -----------
>> >
>> > this particular hypercall leads to the call of set_sh_allocation which
>> > fails in the following code
>> >
>> >         if ( d-> arch.shadow.total_pages < pages )
>> >         {
>> >             /* Need to allocate more memory from domheap */
>> >             pg = alloc_domheap_pages(NULL, SHADOW_MAX_ORDER, 0);
>> >             if ( pg == NULL )
>> >             {
>> >                 SHADOW_PRINTK("failed to allocate shadow pages.\n");
>> >                 return -ENOMEM;
>> >             }
>> >
>> > alloc_domheap_pages fails and returns NULL. however I think I have
>> enough
>> > memory available so this function should not fail.
>> >
>> > Is there anybody else experiencing the same problem? Could someone
>> please
>> > tell me how to fix it?
>>
>> I've put some changes into xen-unstable today which might help.  The last
>> fix
>> is on its way through testing now.  Look out for xen-unstable changeset
>> 11422, and try that, see how you get on.
>>
>> Cheers,
>>
>> Ewan.
>>
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


-- 
TAMURA, Yoshiaki

NTT Cyber Space Labs
OSS Computing Project
Kernel Group
E-mail: tamura.yoshiaki@lab.ntt.co.jp
TEL: (046)-859-2771
FAX: (046)-855-1152
Address: 1-1 Hikarinooka, Yokosuka
	 Kanagawa 239-0847 JAPAN

  reply	other threads:[~2006-09-07  2:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01 21:36 Live vm migration broken in latest xen-unstable sanjay kushwaha
2006-09-05 15:57 ` Ewan Mellor
2006-09-05 19:09   ` sanjay kushwaha
2006-09-07  2:28     ` Yoshiaki Tamura [this message]
2006-09-07 21:29     ` Tim Deegan
2006-09-08 13:48       ` sanjay kushwaha
2006-09-09 22:16         ` sanjay kushwaha
     [not found] <E1GLjNQ-00050a-VB@host-192-168-0-1-bcn-london>
2006-09-08 20:09 ` John Byrne

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=44FF83CA.7020207@lab.ntt.co.jp \
    --to=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=sanjay.kushwaha@gmail.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.