From xen-devel-bounces@lists.xen.org Fri Jan 10 10:31:16 2014 Received: (at maildrop) by bugs.xenproject.org; 10 Jan 2014 10:31:16 +0000 Received: from lists.xen.org ([50.57.142.19]) by bugs.xenproject.org with esmtp (Exim 4.80) (envelope-from ) id 1W1ZMy-0001fL-SF for xen-devel-maildrop-Eithu9ie@bugs.xenproject.org; Fri, 10 Jan 2014 10:31:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1ZIT-0005Fa-Qv; Fri, 10 Jan 2014 10:26:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1ZIR-0005FS-VC for xen-devel@lists.xen.org; Fri, 10 Jan 2014 10:26:36 +0000 Received: from [85.158.137.68:55847] by server-12.bemta-3.messagelabs.com id 0D/E2-20055-BDACFC25; Fri, 10 Jan 2014 10:26:35 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1389349592!8317185!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22970 invoked from network); 10 Jan 2014 10:26:34 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 10 Jan 2014 10:26:34 -0000 X-IronPort-AV: E=Sophos;i="4.95,637,1384300800"; d="scan'208";a="89479028" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 10 Jan 2014 10:26:32 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Fri, 10 Jan 2014 05:26:31 -0500 Message-ID: <1389349591.19142.25.camel@kazak.uk.xensource.com> From: Ian Campbell To: Ian Jackson Date: Fri, 10 Jan 2014 10:26:31 +0000 In-Reply-To: <21198.62393.819485.361532@mariner.uk.xensource.com> References: <21196.19900.136146.867552@mariner.uk.xensource.com> <1389186144.4883.60.camel@kazak.uk.xensource.com> <21198.62393.819485.361532@mariner.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 Cc: xen-devel@lists.xen.org Subject: Re: [Xen-devel] 3.4.70+ kernel WARNING spew dysfunction on failed migration X-BeenThere: xen-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org On Thu, 2014-01-09 at 19:08 +0000, Ian Jackson wrote: > Ian Campbell writes ("Re: [Xen-devel] 3.4.70+ kernel WARNING spew dysfunction on failed migration"): > > The older method is that the toolstack resets a bunch of state (see > > tools/python/xen/xend/XendDomainInfo.py resumeDomain) and then restarts > > the domain. The domain will see HYPERVISOR_suspend return 0 and will > > continue without any realisation that it is actually running in the > > original domain and not in a new one. This method is supposed to be > > implemented by libxl_domain_resume(suspend_cancel=0) but it is not. > > I have looked into this and I think I can fairly simply implement the > old protocol in libxl. This is necessary, I think, to preserve our > back-to-3.0 ABI compatibility guarantee. > > Looking at a modern pvops Linux kernel, does seem to try to cope with > older hypervisors which don't do the "new" protocol. So that's a > reasonable thing to start with, but looking at the code in Linux I > suspect it may not actually work very well. So if anyone has an > ancient test case of some kind that would be helpful... The linux-2.6.18-xen.hg kernel ought to work in the old mode I think. Or any of the SLES fwd ports? Looks like RHEL4 (linux-2.6.9-89.0.16.EL kernel) doesn't have the support for the new mode at all. It would probably be wise to validate this under xend before chasing red-herrings with xl. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel