* Live migration not possible from 5.0 to 5.1?
@ 2020-10-30 4:02 Antti Antinoja
2020-10-30 9:26 ` Daniel P. Berrangé
0 siblings, 1 reply; 2+ messages in thread
From: Antti Antinoja @ 2020-10-30 4:02 UTC (permalink / raw)
To: qemu-devel
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.
Cheers,
Antti
--
Antti Antinoja <reader@fennosys.fi>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Live migration not possible from 5.0 to 5.1?
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é
0 siblings, 0 replies; 2+ messages in thread
From: Daniel P. Berrangé @ 2020-10-30 9:26 UTC (permalink / raw)
To: Antti Antinoja; +Cc: qemu-devel
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 :|
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-10-30 9:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.