From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: mark.williamson@cl.cam.ac.uk
Cc: Stefan Berger <stefanb@us.ibm.com>, xen-devel@lists.sourceforge.net
Subject: Re: Another migration question
Date: Thu, 17 Mar 2005 15:29:50 +0000 [thread overview]
Message-ID: <1111073390.848.7.camel@localhost> (raw)
In-Reply-To: <Prayer.1.0.13.0503171431040.6397@hermes-1.csi.cam.ac.uk>
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.
Harry.
-------------------------------------------------------
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 15:29 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 [this message]
2005-03-17 21:25 ` Jacob Gorm Hansen
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=1111073390.848.7.camel@localhost \
--to=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.