qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Lucas Meneghel Rodrigues <lmr@redhat.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] ivshmem: use migration blockers to prevent live migration in peer mode
Date: Sun, 13 Nov 2011 01:54:45 +0530	[thread overview]
Message-ID: <87k47584xe.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1321043378-15344-2-git-send-email-aliguori@us.ibm.com>

On Fri, 11 Nov 2011 14:29:36 -0600, Anthony Liguori <aliguori@us.ibm.com> wrote:
> Now when you try to migrate with ivshmem, you get a proper QMP error:
> 
> (qemu) migrate tcp:localhost:1025
> Migration is disabled when using feature 'peer mode' in device 'ivshmem'
> (qemu)
> 

We may want to add a similar one when using VirtFS export. But with
VirtFS there is no easy way to do migrate_del_blocker, unless we add a
detach 9p op to map umount.

-aneesh

  reply	other threads:[~2011-11-12 21:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 20:29 [Qemu-devel] [PATCH 1/4] migrate: add migration blockers Anthony Liguori
2011-11-11 20:29 ` [Qemu-devel] [PATCH 2/4] ivshmem: use migration blockers to prevent live migration in peer mode Anthony Liguori
2011-11-12 20:24   ` Aneesh Kumar K.V [this message]
2011-11-11 20:29 ` [Qemu-devel] [PATCH 3/4] qcow2: add a migration blocker Anthony Liguori
2011-11-14 15:51   ` Stefan Hajnoczi
2011-11-14 16:25     ` Anthony Liguori
2011-11-14 16:37       ` Kevin Wolf
2011-11-14 16:45       ` Stefan Hajnoczi
2011-11-14 16:49         ` Anthony Liguori
2011-11-14 16:57           ` Stefan Hajnoczi
2011-11-11 20:29 ` [Qemu-devel] [PATCH 4/4] qed: add " Anthony Liguori

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=87k47584xe.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=lmr@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@linux.vnet.ibm.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 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).