From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Antti Antinoja <reader@fennosys.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: Live migration not possible from 5.0 to 5.1?
Date: Fri, 30 Oct 2020 09:26:42 +0000 [thread overview]
Message-ID: <20201030092642.GD99222@redhat.com> (raw)
In-Reply-To: <20201030120218.57ce841be22970274491be08@fennosys.fi>
On Fri, Oct 30, 2020 at 12:02:18PM +0800, Antti Antinoja wrote:
> Hi All,
>
> I couldn't find any mention about live migration incompatibility between 5.0 and 5.1 in the release notes but at least on our AMD based platform live migration from 5.0 to 5.1 is not possible.
>
> The upgraded host had identical versions with it's pair before the upgrade was started:
> * qemu 5.0.0-r2
> * kernel 5.7.17
>
> After upgrade:
> * qemu 5.1.0-r1
> * kernel 5.8.16
>
> After reverting qemu back to 5.0.0-r2 migration worked normally.
>
> On the sending end "info migrate" shows:
> (qemu) info migrate
> info migrate
> globals:
> store-global-state: on
> only-migratable: off
> send-configuration: on
> send-section-footer: on
> decompress-error-check: on
> clear-bitmap-shift: 18
> Migration status: failed (Unable to write to socket: Broken pipe)
> total time: 0 milliseconds
>
> At least once the receiving end died (while running 5.1.0-r1). All attempts resulted a "Broken pipe" error on the sending (5.0.0-r2) end.
You'll need to provide more information, most importantly how are you
launching QEMU - if manually, what CLI args are you giving it.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2020-10-30 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 4:02 Live migration not possible from 5.0 to 5.1? Antti Antinoja
2020-10-30 9:26 ` Daniel P. Berrangé [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=20201030092642.GD99222@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=reader@fennosys.fi \
/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.