From: David Vrabel <david.vrabel@citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>,
topperxin <topperxin@126.com>
Subject: Re: xen & MacVtap
Date: Wed, 8 Jan 2014 13:18:32 +0000 [thread overview]
Message-ID: <52CD5028.2060802@citrix.com> (raw)
In-Reply-To: <20140108122710.GZ2924@reaktio.net>
On 08/01/14 12:27, Pasi Kärkkäinen wrote:
> On Wed, Jan 08, 2014 at 06:22:06PM +0800, topperxin wrote:
>> Hi list
>> As we all know, SR-IOV technology can improve VNIC's performance,
>> while it can not support live migration. I get some information recently
>> that on KVM+Virtio platform, if we use MacVtap + SR-IOV, the live
>> migration could be done successfully. What I want to know is may I
>> configure MacVtap on Xen?
>> Any replies are welcome! Thanks a lot.
>
> I think years ago (2009, perhaps) when SR-IOV was first demoed with Xen
> it was demoed with live migration.. it was a mixture of SR-IOV VF + Xen vif.
>
> So with some toolstack/script hackery you can do it. (=use the vif pv driver during migration, normally sr-iov vf).
You may find creating an active-backup bond in the guest useful. The
active bond link is the SR-IOV device and the backup is the VIF.
I've not tried this myself.
David
next prev parent reply other threads:[~2014-01-08 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 10:22 xen & MacVtap topperxin
2014-01-08 12:27 ` Pasi Kärkkäinen
2014-01-08 13:18 ` David Vrabel [this message]
2014-01-09 3:30 ` topperxin
2014-01-09 3:07 ` topperxin
2014-01-08 18:44 ` Wei Liu
2014-01-08 19:58 ` Konrad Rzeszutek Wilk
2014-01-08 20:03 ` Wei Liu
2014-01-09 3:52 ` topperxin
2014-01-09 12:14 ` Wei Liu
2014-01-10 8:54 ` topperxin
2014-01-10 10:31 ` Wei Liu
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=52CD5028.2060802@citrix.com \
--to=david.vrabel@citrix.com \
--cc=pasik@iki.fi \
--cc=topperxin@126.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.