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] a problem about xm migrate

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] a problem about xm migrate
From: 刘铭 <liuming910@xxxxxxxxx>
Date: Sun, 19 Apr 2009 15:44:11 +0800
Delivery-date: Sun, 19 Apr 2009 00:44:38 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=qWdZJa3fokMx8jOvq2TA8V2SM02zLH7EzoeiYyjUryo=; b=TLv/mqb54n8vPCkOCV0e6OOaFhfcZv59pA4tHgfgz3EXAmwPYGkeN69bAjyBRBM2+P WcMZ/Z2GyyfFX1WmgI7skxO/mnApLmmfAQPqEH5pFH77p6dSFqhXqmYwSnDDM0pQpL2i j4TTJ7mfoybundGJ+XwdCRbV/OdxaxvkYGvlc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JhODA0bThqLKNe1Rfj3+DoCXqnHRslSYlMNcxcId70A0NJ3mfKgz/8HsIo36JqvlCW cnhE3YHlOmBIZwdAsuejMSWrkZ2PIuDjPGDr1bQpaujbD4l8pDw5f7LgNjJTSIRfra5B veC6LW67mLVd6dWSYqjIEDA2y7oDiChY3Ygto=
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
I have a big obsession about the execution process of command "xm migrate" in
xen.
I analyze this command in xen-3.1.0. And I want to add a parameter in function:
server.xend.domain.migrate(
dom, dst, opts.vals.live,
                                   opts.vals.resource,
                                   opts.vals.port)
Or rewrite another function like:
server.xend.domain.migrate(dom, dst, opts.vals.block,
                                   opts.vals.resource,
                                   opts.vals.port)
Then we'll have a command like this 'xm migrate -b DomUID IP'. But I don't
know how
the parameters are parsed. For example, the function above, where  it jumps to.
Would you tell me the process in details?
Thank you very much.
Best wishes for you.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] a problem about xm migrate, 刘铭 <=