From: Aniruddha Bohra <bohra@cs.rutgers.edu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sf.net
Subject: Re: Xen Roadmap
Date: Wed, 25 Feb 2004 09:04:02 -0500 [thread overview]
Message-ID: <403CAB52.4070805@cs.rutgers.edu> (raw)
In-Reply-To: <E1AvpeD-0006mQ-00@wisbech.cl.cam.ac.uk>
Hi,
I have a question regarding this :
> * "live migration". The 1.2 release supports suspend/resume migration
> of domains, but we have are developing a 'live' migration feature that
> will enable virtual machines to be moved beetween Xen hosts on a LAN
> without having to stop the VM. [2 months]
Does this live migration include migration of open files,
sockets, pipes etc ? Or is this limited to the process migration.
What I mean is :
If I have a VM running a web server, and I try to migrate,
will I lose the connection, or will it continue seamlessly?
Some other questions that arise if the above is true are:
1) If it does, will the client application/server application change
in any way ?
2) How do the TCP bytestreams get synchronized after migration?
3) How big a state do you envision you would need to transfer ?
Thanks,
Regards
Aniruddha
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-25 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 3:23 Xen Roadmap Ian Pratt
2004-02-25 14:04 ` Aniruddha Bohra [this message]
2004-02-25 15:49 ` Ian Pratt
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 13:51 Woloszynski, Charles
2004-02-25 14:42 Andrew Warfield
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=403CAB52.4070805@cs.rutgers.edu \
--to=bohra@cs.rutgers.edu \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sf.net \
/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.