DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "Xie, Huawei" <huawei.xie@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] vhost: enable live migration
Date: Mon, 1 Jun 2015 04:47:55 +0000	[thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F962511B74BB4@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1432695691-22360-1-git-send-email-huawei.xie@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Huawei Xie
> Sent: Wednesday, May 27, 2015 11:02 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] vhost: enable live migration
> 
> When we migrate VM, without this feature, qemu will report error:
> "migrate: Migration disabled: vhost lacks VHOST_F_LOG_ALL feature".
> 

Is this enough for vhost to support  migrate VM?
I remember Claire has another patch, possibly need refer to that patch.

> Signed-off-by: Krishna Murthy  <krishna.j.murthy@intel.com>
> ---
>  lib/librte_vhost/virtio-net.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/librte_vhost/virtio-net.c b/lib/librte_vhost/virtio-net.c index
> 4672e67..fced2ab 100644
> --- a/lib/librte_vhost/virtio-net.c
> +++ b/lib/librte_vhost/virtio-net.c
> @@ -66,7 +66,8 @@ static struct virtio_net_config_ll *ll_root;
>  /* Features supported by this lib. */
>  #define VHOST_SUPPORTED_FEATURES ((1ULL <<
> VIRTIO_NET_F_MRG_RXBUF) | \
>  				(1ULL << VIRTIO_NET_F_CTRL_VQ) | \
> -				(1ULL << VIRTIO_NET_F_CTRL_RX))
> +				(1ULL << VIRTIO_NET_F_CTRL_RX) | \
> +				(1ULL << VHOST_F_LOG_ALL))
>  static uint64_t VHOST_FEATURES = VHOST_SUPPORTED_FEATURES;
> 
> 
> --
> 1.8.1.4

  reply	other threads:[~2015-06-01  4:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  3:01 Huawei Xie
2015-06-01  4:47 ` Ouyang, Changchun [this message]
2015-06-04 13:00   ` Thomas Monjalon
2015-06-09  4:31     ` Long, Thomas
2015-06-12 15:11 ` Thomas Monjalon

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=F52918179C57134FAEC9EA62FA2F962511B74BB4@shsmsx102.ccr.corp.intel.com \
    --to=changchun.ouyang@intel.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).