From: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Antonios Motakis <a.motakis@virtualopensystems.com>
Subject: Re: [Qemu-devel] vhost-user: migration?
Date: Wed, 18 Jun 2014 16:37:57 +0300 [thread overview]
Message-ID: <CADDJ2=Nw7ayFFpZF-cSnL7MgGhoKAoaP5hWO4pGF7Fak9UHOOQ@mail.gmail.com> (raw)
In-Reply-To: <20140618123521.GA31764@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]
On Wed, Jun 18, 2014 at 3:35 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> On Wed, Jun 18, 2014 at 02:41:15PM +0300, Nikolay Nikolaev wrote:
> >
> >
> >
> > On Wed, Jun 18, 2014 at 2:29 PM, Michael S. Tsirkin <mst@redhat.com>
> wrote:
> >
> > On Wed, Jun 18, 2014 at 02:24:32PM +0300, Nikolay Nikolaev wrote:
> > > Hello,
> > >
> > > On Wed, Jun 18, 2014 at 12:33 PM, Michael S. Tsirkin <
> mst@redhat.com>
> > wrote:
> > >
> > > Just a query whether migration works for you
> > > guys with vhost-user and snabbswitch.
> > >
> > >
> > > I am not aware of anyone ever did such tests.
> > >
> > >
> > > vhost user code seems to have enough hooks in
> > > place to make it work, but was it tested
> > > in practice?
> > >
> > >
> > >
> > > Can you give some pointers of a simple/quick test scenario. Maybe
> we'll
> > be able
> > > to set it up.
> >
> >
> > Basically migrate while doing networking :)
> >
> > Does your vhost server have code to set bits in the memory log
> > when logging is enabled?
> >
> >
> > No - we didn't implement this feature.
>
> Interesting. In that case vhost user should for now
> block migration.
>
Any place in the source where we can see example of similar behaviour?
> You must also check log feature and return failure.
>
Should this happen on the QEMU side? Is this the log feature of the device?
regards,
Nikolay Nikolaev
>
>
> >
> > The log address is supplied to VHOST_SET_LOG_BASE and log_guest_addr.
> >
> >
> > >
> > >
> > > --
> > > MST
> > >
> > >
> > > regards,
> > > Nikolay Nikolaev
> >
> >
> > regards,
> > Nikolay Nikolaev
>
[-- Attachment #2: Type: text/html, Size: 2997 bytes --]
next prev parent reply other threads:[~2014-06-18 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 9:33 [Qemu-devel] vhost-user: migration? Michael S. Tsirkin
2014-06-18 11:24 ` Nikolay Nikolaev
2014-06-18 11:29 ` Michael S. Tsirkin
2014-06-18 11:41 ` Nikolay Nikolaev
2014-06-18 12:35 ` Michael S. Tsirkin
2014-06-18 13:37 ` Nikolay Nikolaev [this message]
2014-06-18 14:13 ` Michael S. Tsirkin
2015-01-09 3:24 ` Zhang Haoyu
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='CADDJ2=Nw7ayFFpZF-cSnL7MgGhoKAoaP5hWO4pGF7Fak9UHOOQ@mail.gmail.com' \
--to=n.nikolaev@virtualopensystems.com \
--cc=a.motakis@virtualopensystems.com \
--cc=imammedo@redhat.com \
--cc=mst@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 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).