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

[Xen-devel] Problem with stubdom-dm and live migration in xen 4.0.1

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Problem with stubdom-dm and live migration in xen 4.0.1
From: Roberto Scudeller <beto.rvs@xxxxxxxxx>
Date: Thu, 14 Oct 2010 10:50:47 -0300
Delivery-date: Thu, 14 Oct 2010 06:51:27 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=zVv3T7OcmHRnHa3lHmCn+vplgEMF7skO6LpYdWGBXlc=; b=foO4e3yzXPvbSFCl/+NCgHiZrmiDc5UEtt3UCNnjtxAd9JPrS8kEAmfXnQ2D7tr7kd C87o5iBKG12v+Nqtrd80vglsYE+dnH+HjpAJ/xESx8RulluUEi9vcpHd1d/OidKPnioD VfKLTeqmfnLDLhyTJCZoOrRbUyrSXTtuIFnj8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YFrp8q0NHgsWFoIfQa4rn81cdEbjPRKc1Wi89B/xIhqXnJDhEDHTaiBHsK/6TUH8X/ syUchlATl/uye+UQQ9OIt7oET7QxLQGdi+zLprgb30u4ibSBjVFmDtnz0gY4vR0Ii41F F9xwvtRtVBi3KLQXtggNnj6vuE9h0C5qRF9Q8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

I try using a VM with stubdom-dm instead qemu-dm, and "live migration" don't work.

This command "xm migrate --live w2k3-ent.15 IP_Dom0_Destiny" works, in the Dom0 destiny, created a paused VM (with memory but not a vcpus), but in the end of process, not started appropriate and destroyed VM in both Dom0 Xen. Look "xl list" below:


This description in "xl list", Dom0:

Name                                        ID   Mem VCPUs    State    Time(s)
w2k3-ent.15                                 29  4099     4        r--    545.1
w2k3-ent.15-dm                              30    32     1        r--    482.4

In Dom0_Destiny, during "xm migrate...":

Name                                        ID   Mem VCPUs    State    Time(s)
w2k3-ent.15                                  8  4099     1        -p-      0.0



I using xen 4.0.1 and a kernel 2.6.31.21.

Anybody help?

Sorry for my English terrible.

--
Roberto Scudeller

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Problem with stubdom-dm and live migration in xen 4.0.1, Roberto Scudeller <=