From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/libxl: Do not use remus teardown paths for non-remus guests
Date: Thu, 19 Feb 2015 16:44:30 +0000 [thread overview]
Message-ID: <1424364270.30924.129.camel@citrix.com> (raw)
In-Reply-To: <1424349837-14763-1-git-send-email-andrew.cooper3@citrix.com>
On Thu, 2015-02-19 at 12:43 +0000, Andrew Cooper wrote:
> It causes a suspend failure to emit
>
> libxl: error: libxl_dom.c:2035:remus_teardown_done: Remus: failed to
> teardown device for guest with domid 17, rc -3
>
> for all domains, including those not using remus at all.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Ian Campbell <Ian.Campbell@citrix.com>
> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
> CC: Wei Liu <wei.liu2@citrix.com>
> ---
> tools/libxl/libxl_dom.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/libxl/libxl_dom.c b/tools/libxl/libxl_dom.c
> index 48d661a..a16d4a1 100644
> --- a/tools/libxl/libxl_dom.c
> +++ b/tools/libxl/libxl_dom.c
> @@ -2007,7 +2007,7 @@ static void domain_suspend_done(libxl__egc *egc,
> dss->guest_evtchn.port, &dss->guest_evtchn_lockfd);
>
> if (!dss->remus) {
> - remus_teardown_done(egc, &dss->rds, rc);
> + dss->callback(egc, dss, rc);
This no longer logs the rc (although the wording was wrong confusing
before). I think it needs probably to log something about the suspend
having failed if rc is set. Ian?
> return;
> }
>
next prev parent reply other threads:[~2015-02-19 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 12:43 [PATCH] tools/libxl: Do not use remus teardown paths for non-remus guests Andrew Cooper
2015-02-19 16:44 ` Ian Campbell [this message]
2015-02-19 17:21 ` Ian Campbell
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=1424364270.30924.129.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=wei.liu2@citrix.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.