All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: xen devel <xen-devel@lists.xen.org>
Subject: Re: question about suspending the guest
Date: Fri, 27 Mar 2015 10:31:52 +0000	[thread overview]
Message-ID: <1427452312.13935.99.camel@citrix.com> (raw)
In-Reply-To: <5514F304.8020105@cn.fujitsu.com>

On Fri, 2015-03-27 at 14:04 +0800, Wen Congyang wrote:
> When I test COLO, I find that suspending the primay guest will fail.
> 
> static void domain_suspend_common_wait_guest(libxl__egc *egc,
>                                              libxl__domain_suspend_state2 *dss2)
> {
>     STATE_AO_GC(dss2->ao);
>     int rc;
> 
>     LOG(DEBUG, "wait for the guest to suspend");
> 
>     rc = libxl__ev_xswatch_register(gc, &dss2->guest_watch,
>                                     suspend_common_wait_guest_watch,
>                                     "@releaseDomain");
>     if (rc) goto err;
> 
>     rc = libxl__ev_time_register_rel(gc, &dss2->guest_timeout,
>                                      suspend_common_wait_guest_timeout,
>                                      60*1000);
>     if (rc) goto err;
>     return;
> 
>  err:
>     domain_suspend_common_failed(egc, dss2);
> }
> 
> suspend_common_wait_guest_watch() is not called and timeout. I don't know
> who will wake up this watch.

Any watch on @releaseDomain should be fired by xenstored whenever a
domain is destroyed. xenstored is notified of such events by the
hypervisor via VIRQ_DOM_EXC.

If the watch is not firing then either the domain is not suspending in a
timely manner (i.e. it takes longer than 60 seconds, or never happens at
all) or something else is wrong with your configuration.

Ian.

      reply	other threads:[~2015-03-27 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27  6:04 question about suspending the guest Wen Congyang
2015-03-27 10:31 ` Ian Campbell [this message]

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=1427452312.13935.99.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=wency@cn.fujitsu.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.