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-users

Re: [Xen-users] live migration with xen 2.0.7 with fibre channel onDebia

To: "Cole, Ray" <Ray_Cole@xxxxxxx>
Subject: Re: [Xen-users] live migration with xen 2.0.7 with fibre channel onDebian - help needed
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Wed, 07 Dec 2005 16:25:39 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, Michael Mey <michael.mey@xxxxxx>
Delivery-date: Wed, 07 Dec 2005 16:38:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Message from "Cole, Ray" <Ray_Cole@xxxxxxx> of "Wed, 07 Dec 2005 10:20:29 CST." <4C38B972143E1A4BA2D5E1F12104ECA61017E887@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> I had this exact same problem with 2.0.7.  I had done a little
> investigation and found scheduled_work gets called to schedule the
> shutdown in the user domain kernel, but the shutdown work that gets
> scheduled never actually gets called.  I'm glad someone else is
> seeing this same problem now :-) Like you, it worked a number of
> times in a row, then would fail, and it didn't seem to matter if
> there was really any load going on or not.

At least one issue with live migration in 2.0.7 is fixed in the 
the 2.0-testing tree (cset 3513:80a8b005b669 if you want to just 
apply the patch directly) 

This doesn't explain the situation where your domain dies tho; do 
you have any console information from the domain in question?

cheers,

S.


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