qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com.cn>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: zhaoxing <zhaoxing@sangfor.com.cn>,
	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: Fri, 9 Jan 2015 11:24:45 +0800	[thread overview]
Message-ID: <201501091124450875358@sangfor.com.cn> (raw)
In-Reply-To: 20140618141356.GC31764@redhat.com

Hi,
what's the status of migration support for vhost-user?

Thanks,
Zhang Haoyu
                                       
On 2014-06-18 22:07:49, Michael S. Tsirkin wrote:
> On Wed, Jun 18, 2014 at 04:37:57PM +0300, Nikolay Nikolaev wrote:
> > 
> > 
> > 
> > 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
> >  
> 
> Well, QEMU is buggy in that it tries to set log
> flag without checking.
> I will fix that.
> 
> 
> However
> 1.  Your server must not publish the VHOST_F_LOG_ALL feature.
> 
> On vhost side it should validate features set
> match the supported mask.
> Also for flags in the virtqueue address structure.
> Please validate as much as possible, e.g.
> validate all unused fields are zero.
> If things work by mistake now you will have to maintain
> them indefinitely.
> 
> 
> 
> > 
> > 
> >     >
> >     >     The log address is supplied to VHOST_SET_LOG_BASE and log_guest_addr.
> >     >
> >     >
> >     >     >
> >     >     >
> >     >     >     --
> >     >     >     MST
> >     >     >
> >     >     >
> >     >     > regards,
> >     >     > Nikolay Nikolaev
> >     >
> >     >
> >     > regards,
> >     > Nikolay Nikolaev

      reply	other threads:[~2015-01-09  3:35 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
2014-06-18 14:13           ` Michael S. Tsirkin
2015-01-09  3:24             ` Zhang Haoyu [this message]

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=201501091124450875358@sangfor.com.cn \
    --to=zhanghy@sangfor.com.cn \
    --cc=a.motakis@virtualopensystems.com \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --cc=n.nikolaev@virtualopensystems.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhaoxing@sangfor.com.cn \
    /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).