From: Daniel Berteaud <daniel@firewall-services.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Live VM migration 6.3 to 6.2 fails
Date: Wed, 2 Dec 2020 09:17:44 +0100 (CET) [thread overview]
Message-ID: <20758633.47066.1606897064143.JavaMail.zimbra@fws.fr> (raw)
In-Reply-To: <20201202171102.03c7f2e2@batzmaru.gol.ad.jp>
----- Le 2 Déc 20, à 9:11, Christian Balzer chibi@gol.com a écrit :
> Hello,
>
> yes I know that migrating back to an older version is not guaranteed but
> I'm rather confused as to why this happens.
>
> Firstly this, more details below:
> ---
> 2020-12-02 16:34:08 start migrate command to tcp:10.0.0.11:60000
> 2020-12-02 16:34:09 migration status error: failed
> 2020-12-02 16:34:09 ERROR: online migrate failure - aborting
> 2020-12-02 16:34:09 aborting phase 2 - cleanup resources
> 2020-12-02 16:34:09 migrate_cancel
> 2020-12-02 16:34:11 ERROR: migration finished with problems (duration 00:00:08)
> TASK ERROR: migration problems
> ---
>
> That's all I get, where would one find the exact issue?
>
> Now for the details, in the previous minor upgrade we saw a similar issue,
> but that only affected VMs which had been created on an upgraded node, old
> ones were fine to move in both ways.
> OK, that was because of new features int he VM definition not present on
> the old version, understandable.
>
> With this one on a (more frequently updated) test cluster 6.3 to 6.2
> migrations also works, the test cluster old nodes are at
> pve-manager (6.2-12), the one with issues are pve-manager (6.2-6).
> I however see nothing in the changelogs which would explain this difference.
>
> In general being able to live migrate back to a node with the previous
> version is a very desirable situation, since if there are issues/bugs (on
> the VM level) with the new version there no longer is an impact free way
> of reverting if this functionality is not present.
>
That's most likely the QEMU version 5.1 on the 6.3 node vs QEMU 5.0 on the 6.2 one.
There's no migration support from newer to older, only from older to newer.
Cheers,
Daniel
--
[ https://www.firewall-services.com/ ]
Daniel Berteaud
FIREWALL-SERVICES SAS, La sécurité des réseaux
Société de Services en Logiciels Libres
Tél : +33.5 56 64 15 32
Matrix: @dani:fws.fr
[ https://www.firewall-services.com/ | https://www.firewall-services.com ]
next prev parent reply other threads:[~2020-12-02 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 8:11 Christian Balzer
2020-12-02 8:17 ` Daniel Berteaud [this message]
2020-12-02 8:47 ` Christian Balzer
2020-12-02 8:54 ` Daniel Berteaud
2020-12-02 18:33 ` alexandre derumier
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=20758633.47066.1606897064143.JavaMail.zimbra@fws.fr \
--to=daniel@firewall-services.com \
--cc=pve-user@lists.proxmox.com \
/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