Re: [Xen-devel] [PATCH 0 of 4 V6] libxl: refactor suspend/resume code

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Fri, 2012-05-18 at 15:57 +0100, Shriram Rajagopalan wrote:
> On Fri, May 18, 2012 at 6:07 AM, Ian Campbell
> <Ian.Campbell@xxxxxxxxxx> wrote:
>         On Thu, 2012-05-17 at 20:45 +0100, Shriram Rajagopalan wrote:
>         > This patch series refactors the suspend/resume code to
>         minimize
>         > Remus specific code in libxl. There are a couple of trivial
>         bug
>         > fixes too.
>         
>         
>         I've applied all four of these as well as the two patches from
>         "libxl:
>         Remus support". Thanks for your contribution, and thanks for
>         your
>         patience in particular.
>         
>         I fixed up a minor reject in "libxl: refactor migrate_domain
>         and
>         generalize migrate_receive" due to the context line
>             dom_info.restore_file = "incoming migration stream";
>         having been removed. It's hard to imagine I messed that up but
>         you'd
>         best check!
>         
> 
> 
> Strange.. the c/s on my local box is 25334 (before applying the
> patches).
> I believe thats where xen-unstable.hg but the patches were applied
> against staging/xen-unstable.hg.. 

Yes, patches are always applied against staging.

> And I think the issue you faced was because of a conflict with 
> c/s 25344: xl make clear distinction between "filename" and "data
> source"

Yes, I think so, as I said it was just a line in the context which
differs.
 
> that george submitted. Its in staging but not in the main unstable
> repo.

Right, things are applied to staging and propagate automatically to the
main repo after automated testing. Nothing is ever applied direct to the
main repo.

Testing is a bit broken at the minute so the main repo is a little bit
behind.

>         BTW I tested PV migrate, HVM migrate with qemu-xen-traditional
>         (stub and
>         non-stub) and PVHVM migrate with qemu-xen-traditional (stub
>         and
>         non-stub). All seemed OK.
>         
> 
> 
> Thanks a lot :).

No problem.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel