From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tommy <thfbjhkhtdx@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: pci passthrough and live migration
Date: Tue, 25 Oct 2011 15:33:19 -0400 [thread overview]
Message-ID: <20111025193319.GA13068@phenom.dumpdata.com> (raw)
In-Reply-To: <4EA66636.30400@gmail.com>
On Tue, Oct 25, 2011 at 03:33:10PM +0800, Tommy wrote:
> Hello, everybody!
>
> I've done some research on Xenlive migration recently.
XenLive? What is that? Oh, is that the CentOS4..
>
> I've checked the maillist for pci passthrough and live migration, I
> can't figure out the current progress on them.
Did you check the Wiki?
>
> Does Xen support live migration with pci passthrough? How about that
> with vga passthrough?
You can do it with SR-IOV, but normal PCI passthrough would not work that well.
>
> If it is supported now, what extra configurations do I need?
It definitly is supported in the kernel.. you need to use 'pci-attach'
command and hardware that can do IOMMU if you want to do it with HVM.
If you want to do with PV, you need to pass 'iommu=soft' on the Linux
command line.
However, before the migration, you _must_ hot-unplug the pci-device - you
can use 'pci-detach' and then on the other end do 'pci-attach'.
I am not sure if the tools do this automatically but they might.
>
> If not, could anyone give some ideas on what is the main difficulties
> for it?
>
> At last, does anyone have some documents about this area?
Just search for SR-IOV and Xen.
>
> Thanks!
>
>
> --
>
> Yours Sincerely!
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-10-25 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 7:33 pci passthrough and live migration Tommy
2011-10-25 19:33 ` Konrad Rzeszutek Wilk [this message]
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=20111025193319.GA13068@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=thfbjhkhtdx@gmail.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.