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:54:41 +0100 (CET) [thread overview]
Message-ID: <2120552064.47698.1606899281402.JavaMail.zimbra@fws.fr> (raw)
In-Reply-To: <20201202174718.0bdf3912@batzmaru.gol.ad.jp>
----- Le 2 Déc 20, à 9:47, Christian Balzer chibi@gol.com a écrit :
>>
> If that is really the case (qemu migrations between minor versions have
> worked in the past, at least sometimes), then this is actually worse.
>
> As I wrote, some 6.2 nodes don't have that issue and indeed they have qemu
> 5.1 which was brought in with 6.2-13.
> So no version upgrade flashing warning lights going off in your brain and
> if one had not upgraded all nodes, the same would have happened in a
> cluster that was nominally still 6.2?
> That's rather... scary.
>
If you got QEMU 5.1 with pve 6.2, I guess you're using either the pvetest or no-subscription repo. In which case, it's up to you to check for changelog and important version changes, as those repo are kinda "rolling updates"
If you want peace of mind on this front, you should pay access to the enterprise repo, which have more stable updates
Regards,
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:55 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
2020-12-02 8:47 ` Christian Balzer
2020-12-02 8:54 ` Daniel Berteaud [this message]
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=2120552064.47698.1606899281402.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