qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
	qemu-stable@nongnu.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work
Date: Fri, 09 May 2014 19:05:15 +0200	[thread overview]
Message-ID: <536D0ACB.50206@redhat.com> (raw)
In-Reply-To: <536CD48B.2020907@profihost.ag>

Il 09/05/2014 15:13, Stefan Priebe - Profihost AG ha scritto:
>
> I see no output at the monitor of Qemu 2.0.
>
> # migrate -d tcp:a.b.c.d:6000
>
> # info migrate
> capabilities: xbzrle: off x-rdma-pin-all: off auto-converge: on
> zero-blocks: off
> Migration status: failed
> total time: 0 milliseconds
>
> The target machine is still running at this point with no output.

Anything on its stdout?

Another test you could do, in addition to changing the devices, is this:

1) try with commit 6141f3bd6904df7cf9519c6444a14a608b9874c4 on the 
destination (the next one caused a migration problem that was fixed 
later).  If it passes, go to step 1a.  If it fails, go to step 2.

1a) try with commit c01a71c1a56fa27f43449ff59e5d03b2483658a2.  If it 
passes, go to step 1b.  If it fails, report it here.

1b) bisect between v2.0.0 (known-bad) and 
c01a71c1a56fa27f43449ff59e5d03b2483658a2 (known-good) to find the 
culprit.  Report results.

2) change the source to v1.7.0 and bisect between v1.7.0 and 
6141f3bd6904df7cf9519c6444a14a608b9874c4.  Report results.

Thanks!

Paolo

  parent reply	other threads:[~2014-05-09 17:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 13:13 [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not work Stefan Priebe - Profihost AG
2014-05-09 13:41 ` Dr. David Alan Gilbert
2014-05-09 16:14   ` Stefan Priebe - Profihost AG
2014-05-09 16:29     ` Dr. David Alan Gilbert
2014-05-09 20:08       ` Stefan Priebe
2014-05-09 17:05 ` Paolo Bonzini [this message]
2014-05-09 20:53   ` Stefan Priebe
2014-05-14  7:17   ` Stefan Priebe - Profihost AG
2014-05-14  8:11     ` Paolo Bonzini
2014-05-14  8:29       ` Stefan Priebe - Profihost AG
2014-05-14  8:36         ` Paolo Bonzini
2014-05-14  8:38           ` Stefan Priebe - Profihost AG
2014-05-14  9:00             ` Paolo Bonzini
2014-05-14  9:25               ` Stefan Priebe - Profihost AG
2014-05-14  9:34                 ` Paolo Bonzini

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=536D0ACB.50206@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=s.priebe@profihost.ag \
    /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).