From xen-devel-bounces@lists.xen.org Thu Jan 09 19:14:27 2014 Received: (at maildrop) by bugs.xenproject.org; 9 Jan 2014 19:14:27 +0000 Received: from lists.xen.org ([50.57.142.19]) by bugs.xenproject.org with esmtp (Exim 4.80) (envelope-from ) id 1W1L3j-0000q4-0V for xen-devel-maildrop-Eithu9ie@bugs.xenproject.org; Thu, 09 Jan 2014 19:14:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1KyY-0003T5-Lb; Thu, 09 Jan 2014 19:09:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W1KyX-0003T0-0I for xen-devel@lists.xen.org; Thu, 09 Jan 2014 19:09:05 +0000 Received: from [193.109.254.147:35329] by server-2.bemta-14.messagelabs.com id 85/C9-00361-0D3FEC25; Thu, 09 Jan 2014 19:09:04 +0000 X-Env-Sender: Ian.Jackson@citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1389294540!7647128!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 17151 invoked from network); 9 Jan 2014 19:09:02 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 9 Jan 2014 19:09:02 -0000 X-IronPort-AV: E=Sophos;i="4.95,632,1384300800"; d="scan'208";a="89268480" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 09 Jan 2014 19:08:43 +0000 Received: from norwich.cam.xci-test.com (10.80.248.129) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Thu, 9 Jan 2014 14:08:43 -0500 Received: from mariner.cam.xci-test.com ([10.80.2.22] helo=mariner.uk.xensource.com) by norwich.cam.xci-test.com with esmtp (Exim 4.72) (envelope-from ) id 1W1KyA-0004Pi-EM; Thu, 09 Jan 2014 19:08:42 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.80) (envelope-from ) id 1W1KyA-0003VN-7t; Thu, 09 Jan 2014 19:08:42 +0000 From: Ian Jackson MIME-Version: 1.0 Message-ID: <21198.62393.819485.361532@mariner.uk.xensource.com> Date: Thu, 9 Jan 2014 19:08:41 +0000 To: Ian Campbell In-Reply-To: <1389186144.4883.60.camel@kazak.uk.xensource.com> References: <21196.19900.136146.867552@mariner.uk.xensource.com> <1389186144.4883.60.camel@kazak.uk.xensource.com> X-Mailer: VM 8.1.0 under 23.4.1 (i486-pc-linux-gnu) 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 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... Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel