From: Kashyap Chamarthy <kchamart@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] crash with -incoming and -snapshot
Date: Mon, 15 Feb 2016 12:20:54 +0100 [thread overview]
Message-ID: <20160215112054.GC15761@tesla.redhat.com> (raw)
In-Reply-To: <56C199B9.5000400@redhat.com>
On Mon, Feb 15, 2016 at 10:26:17AM +0100, Paolo Bonzini wrote:
>
>
> On 15/02/2016 10:12, Kevin Wolf wrote:
> > Am 14.02.2016 um 17:12 hat Paolo Bonzini geschrieben:
> >> On 14/02/2016 16:52, Paolo Bonzini wrote:
> >>> Reproducer:
> >>>
> >>> x86_64-softmmu/qemu-system-x86_64 \
> >>> -incoming tcp:localhost:12345 -snapshot \
> >>> /vm/virt_test/images/jeos-21-64-base.qcow2
> >>>
> >>>
> >>> Weird as it may seem, this actually makes some sense for testing
> >>> migration with non-shared storage...
> >>
> >> In fact, migration with non-shared storage (migrate -b) is broken in
> >> general, even without -snapshot.
> >
> > Oh cool, does this mean that we can finally remove it? :-)
>
> I wouldn't object, but people are using it. :)
One case I know for sure: Upstream libvirt (consequently, OpenStack
Nova) falls back to 'migrate -b'/("inc:" true) approach when there's no
NBD support on the destination during live block migration:
# From qemuMigrationRun() function in libvirt source
$ less libvirt/src/qemu/qemu_migration.c
[...]
if (migrate_flags & (QEMU_MONITOR_MIGRATE_NON_SHARED_DISK |
QEMU_MONITOR_MIGRATE_NON_SHARED_INC)) {
if (mig->nbd) {
/* This will update migrate_flags on success */
if (qemuMigrationDriveMirror(driver, vm, mig,
spec->dest.host.name,
migrate_speed,
&migrate_flags,
nmigrate_disks,
migrate_disks,
dconn) < 0) {
goto cleanup;
}
} else {
/* Destination doesn't support NBD server.
* Fall back to previous implementation. */
VIR_DEBUG("Destination doesn't support NBD server "
"Falling back to previous implementation.");
}
}
[...]
This fallback also kicks in when people enable TUNNELLED migration (as
NBD does not have support for it in libvirt, due to valid technical
reasons documented else where).
--
/kashyap
prev parent reply other threads:[~2016-02-15 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 15:52 [Qemu-devel] crash with -incoming and -snapshot Paolo Bonzini
2016-02-14 16:12 ` Paolo Bonzini
2016-02-15 9:12 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-02-15 9:26 ` [Qemu-devel] " Paolo Bonzini
2016-02-15 11:20 ` Kashyap Chamarthy [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=20160215112054.GC15761@tesla.redhat.com \
--to=kchamart@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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.