WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH 0/4] stubdom-dm: Support live migration of HV

To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 0/4] stubdom-dm: Support live migration of HVM domain with stubdom-dm
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 16 Dec 2008 14:04:53 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 16 Dec 2008 06:05:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20081216100231.GD5333@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <4947734C.5070509@xxxxxxxxxxxxx> <20081216100231.GD5333@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Samuel Thibault writes ("[Xen-devel] Re: [PATCH 0/4] stubdom-dm: Support live 
migration of HVM domain with stubdom-dm"):
> Yosuke Iwamatsu, le Tue 16 Dec 2008 18:22:20 +0900, a écrit :
> > This series of patches is an attempt to support live migration of hvm
> > domains with stubdom-dm.
> 
> Err, I'm a bit surprised. I haven't tested it since then, but I'm sure
> live migration was working with stubdoms a few months ago, without
> the need for a logdirty shared buffer.  This works thanks to the few
> lines at the end of the cpu_physical_memory_rw() function that tell the
> hypervisor about modified memory.  Actually, the plan was even to use
> that bit of code in all cases (not only non-stubdom), so as to get rid
> of the logdirty shared buffer completely.

I take it you're referring to this:

#ifdef CONFIG_STUBDOM
    if (logdirty_bitmap != NULL)
        xc_hvm_modified_memory(xc_handle, domid, _addr >> TARGET_PAGE_BITS,
                ((_addr + _len + TARGET_PAGE_SIZE - 1) >> TARGET_PAGE_BITS)
                    - (_addr >> TARGET_PAGE_BITS));
#endif

Yosuke Iwamatsu: is this not working for you then ?  It's possible
that I've broken it somehow.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel