All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jens Freimann <jfreimann@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/9] add failover feature for assigned network devices
Date: Tue, 6 Aug 2019 04:43:35 -0400	[thread overview]
Message-ID: <20190806043953-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190805184949.kmv7qra67jfxie2j@jenstp.localdomain>

On Mon, Aug 05, 2019 at 08:49:49PM +0200, Jens Freimann wrote:
> On Mon, Aug 05, 2019 at 10:22:25AM -0400, Michael S. Tsirkin wrote:
> > On Mon, Aug 05, 2019 at 03:12:15PM +0200, Jens Freimann wrote:
> > > On Fri, Aug 02, 2019 at 11:22:10AM -0400, Michael S. Tsirkin wrote:
> > > > On Fri, Aug 02, 2019 at 05:05:56PM +0200, Jens Freimann wrote:
> > > > > This is implementing the host side of the net_failover concept
> > > > > (https://www.kernel.org/doc/html/latest/networking/net_failover.html)
> > > > >
> > > > > Changes since v1:
> > > 
> > > [...]
> > > 
> > > > Didn't read this yet, one question: how do migration commands look
> > > > like?
> > > 
> > > You mean the hmp commands I think:
> > > 
> > > migrate -d tcp:host:port
> > > 
> > > and to cancel
> > > 
> > > migrate_cancel
> > > 
> > > 
> > > regards,
> > > Jens
> > 
> > Sorry, no. I mean the command line on the incoming side.
> 
> It looks the same with -incoming tcp:0:4444 added. Pci address of
> vfio-pci device can be changed.


Sounds good. And I assume one can also skip the vfio device and
hotplug it later, right?


> > 
> > -- 
> > MST
> > 


  reply	other threads:[~2019-08-06  8:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 15:05 [Qemu-devel] [PATCH v2 0/9] add failover feature for assigned network devices Jens Freimann
2019-08-02 15:05 ` [Qemu-devel] [PATCH 1/9] qdev/qbus: Add hidden device support Jens Freimann
2019-08-02 15:05 ` [Qemu-devel] [PATCH 2/9] net/virtio: add failover support Jens Freimann
2019-08-02 15:05 ` [Qemu-devel] [PATCH 3/9] vfio: unplug failover primary device before migration Jens Freimann
2019-08-12 15:18   ` Cornelia Huck
2019-08-12 21:22     ` Alex Williamson
2019-08-13  6:45       ` Jens Freimann
2019-08-13  9:35         ` Cornelia Huck
2019-08-13  6:50     ` Jens Freimann
2019-08-02 15:06 ` [Qemu-devel] [PATCH 4/9] migration: allow unplug during migration for failover devices Jens Freimann
2019-08-02 15:06 ` [Qemu-devel] [PATCH 5/9] qapi: add unplug primary event Jens Freimann
2019-08-02 15:06 ` [Qemu-devel] [PATCH 6/9] qapi: Add failover negotiated event Jens Freimann
2019-08-02 15:06 ` [Qemu-devel] [PATCH 7/9] migration: Add new migration state wait-unplug Jens Freimann
2019-08-02 15:06 ` [Qemu-devel] [PATCH 8/9] pci: mark devices partially unplugged Jens Freimann
2019-08-02 15:06 ` [Qemu-devel] [PATCH 9/9] pci: mark device having guest unplug request pending Jens Freimann
2019-08-02 15:22 ` [Qemu-devel] [PATCH v2 0/9] add failover feature for assigned network devices Michael S. Tsirkin
2019-08-05 13:12   ` Jens Freimann
2019-08-05 14:22     ` Michael S. Tsirkin
2019-08-05 18:49       ` Jens Freimann
2019-08-06  8:43         ` Michael S. Tsirkin [this message]
2019-08-07  9:15           ` Jens Freimann
2019-08-02 15:22 ` no-reply
2019-08-02 16:12 ` no-reply
2019-08-12 14:53 ` Michael S. Tsirkin

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=20190806043953-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jfreimann@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.