On 07/15/2015 09:35 PM, Ian Jackson wrote:
When the timeout set for prompting the next remus iteration fires, we
should not treat the ERROR_TIMEDOUT as an error.
Bug in 31c836f4 "libxl: events: Permit timeouts to signal ao abort".
Reported-by: Yang Hongyang <yan...@cn.fujitsu.com>
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
CC: Yang Hongyang <yan...@cn.fujitsu.com>
CC: Wei Liu <wei.l...@citrix.com>
CC: Ian Campbell <ian.campb...@citrix.com>
Acked-by: Yang Hongyang <yan...@cn.fujitsu.com>
---
tools/libxl/libxl_dom.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/libxl/libxl_dom.c b/tools/libxl/libxl_dom.c
index 81adb3d..4cb247a 100644
--- a/tools/libxl/libxl_dom.c
+++ b/tools/libxl/libxl_dom.c
@@ -2024,6 +2024,9 @@ static void remus_next_checkpoint(libxl__egc *egc,
libxl__ev_time *ev,
STATE_AO_GC(dss->ao);
+ if (rc == ERROR_TIMEDOUT) /* As intended */
+ rc = 0;
+
/*
* Time to checkpoint the guest again. We return 1 to libxc
* (xc_domain_save.c). in order to continue executing the infinite loop
--
Thanks,
Yang.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
