xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Alain Tchana <alain.tchana@inria.fr>
To: xen-devel@lists.xen.org
Subject: Domain migration source code interpretation in xl/libxl (xen-4.1.2)
Date: Thu, 5 Apr 2012 22:05:53 +0200 (CEST)	[thread overview]
Message-ID: <93792556.794910.1333656353242.JavaMail.root@zmbs2.inria.fr> (raw)
In-Reply-To: <759798916.794821.1333655343974.JavaMail.root@zmbs2.inria.fr>


[-- Attachment #1.1: Type: text/plain, Size: 1020 bytes --]

Hi all, 
I am trying to understand domU migration in xen-4.1.2/tools/libxl/xm_cmdimpl.c. Here are my questions: 

1) Is there any documentation which explain each functions? 

2) What is the difference between these two functions: int main_migrate(int argc, char **argv) and int main_migrate_receive(int argc, char **argv)? 

3) In the function: static void migrate_domain(const char *domain_spec, const char *rune, const char *override_config_file) , 
what does: 

*) save_domain_core_begin(domain_spec, override_config_file, &config_data, &config_len); 

*)migrate_read_fixedmessage(recv_fd, migrate_receiver_banner, 
sizeof(migrate_receiver_banner)-1, 
"banner", rune); 

*)save_domain_core_writeconfig(send_fd, "migration stream", 
config_data, config_len); 

*)migration_child_report(child, recv_fd); 

*)Finally, which section of the" migrate_domain" function performs memory copy from the initial host to the target host? 

Please, apologize the number of questions. 

Thanks in advance for your answers. 
Alain 

[-- Attachment #1.2: Type: text/html, Size: 2023 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

           reply	other threads:[~2012-04-05 20:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <759798916.794821.1333655343974.JavaMail.root@zmbs2.inria.fr>]

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=93792556.794910.1333656353242.JavaMail.root@zmbs2.inria.fr \
    --to=alain.tchana@inria.fr \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).