From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH] tools/libxc: Disable CONFIG_MIGRATE in stubdom environments Date: Tue, 27 Jan 2015 17:24:06 +0000 Message-ID: <54C7C9B6.2000301@citrix.com> References: <1422377886-10334-1-git-send-email-andrew.cooper3@citrix.com> <1422378083.16180.12.camel@citrix.com> <54C7C684.4080001@citrix.com> <1422378740.16180.16.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1422378740.16180.16.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Wei Liu , Ian Jackson , Xen-devel List-Id: xen-devel@lists.xenproject.org On 27/01/15 17:12, Ian Campbell wrote: > On Tue, 2015-01-27 at 17:10 +0000, Andrew Cooper wrote: >>> As opposed to e.g. an HVM domain using a qemu-stubdom, but being >>> migrated by a normal toolstack in domain 0 (or at least, not in a >>> mini-os based stubdom). >> A qemu-stubdom equally cant participate in migrate of its domain >> (because of the issues in passing the qemu save record), but that is a >> separate issue. > This works today AFAIK, I'm afraid I think it needs to keep working for > the new migration stuff to land. Nothing along these lines is (should be) impacted by legacy vs migration-v2. Migration v2 changes the point at which the existing qemu save record infrastructure is called, but does not change its functionality. But as I say, this point is unrelated to the purpose of the patch. ~Andrew