All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, jcody@redhat.com,
	kwolf@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block migration: Allow compile time disable
Date: Thu, 4 May 2017 14:52:46 +0200	[thread overview]
Message-ID: <20170504125246.mfkghiglgpj4qoix@eukaryote> (raw)
In-Reply-To: <20170504102523.GB2078@work-vm>

On Thu, May 04, 2017 at 11:25:25AM +0100, Dr. David Alan Gilbert wrote:
> * Kashyap Chamarthy (kchamart@redhat.com) wrote:
> > On Wed, May 03, 2017 at 11:42:57AM +0100, Dr. David Alan Gilbert (git) wrote:

[...]

> > > +#ifndef CONFIG_LIVE_BLOCK_MIGRATION
> > > +    if (params.blk || params.shared) {
> > > +        error_setg(errp, "QEMU compiled without old-style block migration. "
> > > +                         "Use drive_mirror+NBD.");
> > 
> > Is it worth spelling out briefly what the "old-style block
> > migration" is?  Something like:
> > 
> >     "QEMU compiled without old-style (i.e. QMP `migrate` with
> >     "inc":true) block migration. Use `drive-mirror`+NBD")
> >  
> > But I also wonder if it's needlessly wordy, so your call to
> > incorporate it or not.
> 
> I was trying to find a short way to say it, and that's the closest I
> got to.

Fair enough.

> > I spelled out the QMP equivalent (as opposed to HMP: 'migrate -b')
> > because, that's what users of higher layers (libvirt, OpenStack etc)
> > see in their QMP interactions with QEMU, when the old-style approach
> > is used:
> > 
> >     {"execute":"migrate","arguments":{{"detach":true,"blk":false,"inc":true,"uri":"fd:migrate"}
> 
> But would openstack users even know about QMP?

No, they're not expected to know of it.  Only developers digging into
Nova Vir driver issues that trickle down to QEMU normally know about it.

-- 
/kashyap

  reply	other threads:[~2017-05-04 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 10:42 [Qemu-devel] [PATCH] block migration: Allow compile time disable Dr. David Alan Gilbert (git)
2017-05-03 18:06 ` Juan Quintela
2017-05-15 13:02   ` Dr. David Alan Gilbert
2017-05-15 13:09     ` Juan Quintela
2017-05-04 10:08 ` Kashyap Chamarthy
2017-05-04 10:25   ` Dr. David Alan Gilbert
2017-05-04 12:52     ` Kashyap Chamarthy [this message]
2017-05-15 13:24   ` Dr. David Alan Gilbert
2017-05-04 16:30 ` Eric Blake
2017-05-15 12:13   ` Dr. David Alan Gilbert
2017-05-15 13:44     ` Eric Blake

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=20170504125246.mfkghiglgpj4qoix@eukaryote \
    --to=kchamart@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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.