All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuval Shaia <yuval.shaia@oracle.com>
To: Sukrit Bhatnagar <skrtbhtngr@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 0/2] Add live migration support in the PVRDMA device
Date: Thu, 29 Aug 2019 15:00:13 +0300	[thread overview]
Message-ID: <20190829120013.GA9911@lap1> (raw)
In-Reply-To: <20190828142328.24561-1-skrtbhtngr@gmail.com>

On Wed, Aug 28, 2019 at 07:53:26PM +0530, Sukrit Bhatnagar wrote:
> This series enables the migration of various GIDs used by the device.    
> This is in addition to the successful migration of PCI and MSIX states
> as well as various DMA addresses and ring page information.
>     
> We have a setup having two hosts and two VMs running atop them.    
> Migrations are performed over the local network.    
> 
> We also have performed various ping-pong tests (ibv_rc_pingpong) in the    
> guest(s) after adding GID migration support and this is the current status:    
> - ping-pong to localhost succeeds, when performed before starting the    
>   migration and after the completion of migration.    
> - ping-pong to a peer succeeds, both before and after migration as above,    
>   provided that both VMs are running on/migrated to the same host.    
>   So, if two VMs were started on two different hosts, and one of them    
>   was migrated to the other host, the ping-pong was successful.    

This limitation looks to me like wrongly configured network. This patch-set
should enable any migration.

After our last meeting, please confirm.

In addition, i don't see why non-VM peer (i.e. Bare-metal) is not
supported. Can you run a test and update with the results?

>   Similarly, if two VMs are migrated to the same host, then after migration,    
>   the ping-pong was successful.    
> - ping-pong to a peer on the remote host is not working as of now.    
>     
> Our next goal is to achieve successful migration with live traffic.    
>     
> This is the same as the RFC v3 series posted earlier:
> https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg04752.html
> https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg04753.html
> https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg04754.html
> 
> 
> Sukrit Bhatnagar (2):
>   hw/pvrdma: make DSR mapping idempotent in load_dsr()
>   hw/pvrdma: add live migration support
> 
>  hw/rdma/vmw/pvrdma_main.c | 94 +++++++++++++++++++++++++++++++++++----
>  1 file changed, 86 insertions(+), 8 deletions(-)
> 
> -- 
> 2.21.0
> 
> 


  parent reply	other threads:[~2019-08-29 12:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 14:23 [Qemu-devel] [PATCH v1 0/2] Add live migration support in the PVRDMA device Sukrit Bhatnagar
2019-08-28 14:23 ` [Qemu-devel] [PATCH v1 1/2] hw/pvrdma: make DSR mapping idempotent in load_dsr() Sukrit Bhatnagar
2019-08-29 12:57   ` Yuval Shaia
2019-08-31 19:39   ` Marcel Apfelbaum
2019-08-28 14:23 ` [Qemu-devel] [PATCH v1 2/2] hw/pvrdma: add live migration support Sukrit Bhatnagar
2019-08-29 12:53   ` Yuval Shaia
2019-09-03 21:33     ` Sukrit Bhatnagar
2019-09-04  5:04       ` Yuval Shaia
2019-08-29 12:56   ` Yuval Shaia
2019-08-31 19:45   ` Marcel Apfelbaum
2019-09-01  9:35     ` Yuval Shaia
2019-09-03 11:05     ` Sukrit Bhatnagar
2019-08-29 12:00 ` Yuval Shaia [this message]
2019-08-31 19:37 ` [Qemu-devel] [PATCH v1 0/2] Add live migration support in the PVRDMA device Marcel Apfelbaum

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=20190829120013.GA9911@lap1 \
    --to=yuval.shaia@oracle.com \
    --cc=qemu-devel@nongnu.org \
    --cc=skrtbhtngr@gmail.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.