All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
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 14:58:03 -0500	[thread overview]
Message-ID: <20140108195803.GB16230@phenom.dumpdata.com> (raw)
In-Reply-To: <20140108184405.GB13867@zion.uk.xensource.com>

On Wed, Jan 08, 2014 at 06:44:05PM +0000, Wei Liu 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.
> 
> AIUI MacVtap runs in emulation mode and connects to VirtIO to implement
> the feature you want. That would mean you also need to use VirtIO
> network driver for Xen's HVM domain, if you manage to configure MacVtap
> for Xen.
> 
> Basically that means a configuration that nobody ever tried. Good luck.
> :-)

Do you know what would be needed to make MacVtap run with Xen's drivers?

  reply	other threads:[~2014-01-08 19:58 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
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 [this message]
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=20140108195803.GB16230@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=topperxin@126.com \
    --cc=wei.liu2@citrix.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.