All of lore.kernel.org
 help / color / mirror / Atom feed
From: tgh <wwwwww4187@sina.com.cn>
To: Stefan Berger <stefanb@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: migrateDevices( ) ?
Date: Thu, 03 Jan 2008 10:35:19 +0800	[thread overview]
Message-ID: <477C49E7.4050804@sina.com.cn> (raw)
In-Reply-To: <OFC8054FBB.E2613462-ON852573C4.006752EF-852573C4.0067B60A@us.ibm.com>

hi
Thank you for your explanation
and when xen processes " live migration",xend will fork a process to do 
xc_linux_save,and also call the helphandler which will call 
migrateDevices() in three steps,that is ,migrateDevices() will copy the 
devices' state to the destination when the iterative pre-copying of the 
VM memory state is completed ,is it? or what is the tricks behind? i 
read DevController.py,but still not clear,
and i am confused about which code is called in the destination node to 
cooperate with for migration, that is ,on the destination node ,which 
code will invoke the receiving function there? is it httpserver? then 
,which function code will it call to receive ,or what to do ?i guess 
some functions will be called to deal with something ,then call the 
restore function or something, but which function is called before the 
restore function is called ? i am lost in it

Thanks in advance



Stefan Berger 写道:
>
> xen-devel-bounces@lists.xensource.com wrote on 01/02/2008 01:41:56 AM:
>
> > hi
> > I read the code of migration,and i am confused about the function of
> > migrateDevices(), it is called for 3times,and what is the function for
> > it ? could someone help me out
>
> The purpose of this function is to enable the migration of 'external 
> devices', i.e. this would be disk images or TPM state, from one 
> physical machine to another while migrating a vm.
>
> The prototype of the migrate function explains the different steps.
>
> http://xenbits.xensource.com/xen-unstable.hg?file/2491691e3e69/tools/python/xen/xend/server/DevController.py 
>
>
>
> Stefan
>
> >
> > Thanks in advance
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel

  reply	other threads:[~2008-01-03  2:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-31  3:46 xway issues / bugs Muhammad Atif
2008-01-02  6:41 ` migrateDevices( ) ? tgh
2008-01-02 18:52   ` Stefan Berger
2008-01-03  2:35     ` tgh [this message]
2008-01-04  5:59     ` device models? tgh
2008-01-04 10:28       ` Samuel Thibault
2008-01-04  6:49     ` migration and relocation server? tgh
2008-02-26  9:56       ` code read problems tgh
2008-01-04 17:57 ` xway issues / bugs Mark Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=477C49E7.4050804@sina.com.cn \
    --to=wwwwww4187@sina.com.cn \
    --cc=stefanb@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.