From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
Cc: mark.williamson@cl.cam.ac.uk, Stefan Berger <stefanb@us.ibm.com>,
xen-devel@lists.sourceforge.net
Subject: Re: Another migration question
Date: Thu, 17 Mar 2005 13:25:04 -0800 [thread overview]
Message-ID: <4239F5B0.1030006@diku.dk> (raw)
In-Reply-To: <1111073390.848.7.camel@localhost>
Harry Butterworth wrote:
> On Thu, 2005-03-17 at 14:31 +0000, M.A. Williamson wrote:
>
>>USB is a little trickier because there isn't a straightforward way to
>>ensure the guest can still access the device after the migration nor to
>>make the process transparent to the guest USB stack. For this reason, USB
>>doesn't support suspend, so you can't suspend a USB frontend domain. We can
>>probably do a bit better e.g. fake out port disconnects on suspend then
>>allow a device reconnect on resume - it won't be transparent but it'll be
>>more useful.
>
>
> If the inter-domain communication interface was network transparent it
> would allow you to migrate a domain within a cluster for load-balancing
> whilst leaving the usb devices where they were.
There is an argument against making any of this transparent. If you
migrate stuff somewhere, you would like to be independent of the
originating machine once you arrive. Network transparent IPC/RPC,
filesystems, and process migration, were all hot topics in systems
research some 10-15 years ago, and, apart from NFS (which is now being
replaced by iSCSI) none of these fancy transparent schemes survived in
the real world.
I've done some test with self-migration (the right way to do all of this
IMHO) using software RAID-1. In this setup it is trivial to mirror a
block device onto the target node, and when the mirror is synced up you
migrate the OS itself. I guess it is not currently possible to upgrade a
remote iSCSI mount to a local Xen-block device mount.
There is no need to forward any migration events into userspace, because
userspace is what is controlling the whole thing anyway. The TCP
connection is opened and fed from userspace, the ARP reply is sent from
userspace, even the protocol implementation running at the remote end is
uploaded from userspace.
You could argue that self-migration, implemented inside XenoLinux, is
less portable. However, I recently counted, and it seems that today
there are more different VMMs than there are operating systems.
But that is just my view. I am likely to be wrong, or at least suffering
from the 'second system effect' ;-).
Jacob
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-17 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 4:13 Another migration question Stefan Berger
2005-03-17 9:27 ` Keir Fraser
2005-03-17 14:31 ` M.A. Williamson
2005-03-17 15:29 ` Harry Butterworth
2005-03-17 21:25 ` Jacob Gorm Hansen [this message]
2005-03-18 1:27 ` Eric S. Johansson
-- strict thread matches above, loose matches on Subject: below --
2005-03-17 10:42 Ian Pratt
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=4239F5B0.1030006@diku.dk \
--to=jacobg@diku.dk \
--cc=harry@hebutterworth.freeserve.co.uk \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=stefanb@us.ibm.com \
--cc=xen-devel@lists.sourceforge.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.