From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] crash with -incoming and -snapshot
Date: Mon, 15 Feb 2016 10:12:59 +0100 [thread overview]
Message-ID: <20160215091259.GB5244@noname.str.redhat.com> (raw)
In-Reply-To: <56C0A75E.4020807@redhat.com>
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? :-)
Kevin
next prev parent reply other threads:[~2016-02-15 9:13 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 ` Kevin Wolf [this message]
2016-02-15 9:26 ` Paolo Bonzini
2016-02-15 11:20 ` Kashyap Chamarthy
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=20160215091259.GB5244@noname.str.redhat.com \
--to=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 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).