From: "Alain Péan" <alain.pean@c2n.upsaclay.fr>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] PVE 7.2 unstability
Date: Thu, 12 May 2022 17:12:59 +0200 [thread overview]
Message-ID: <7d6f9cc7-1dfe-63aa-b166-64d7f9b4c816@c2n.upsaclay.fr> (raw)
In-Reply-To: <mailman.152.1652367475.362.pve-user@lists.proxmox.com>
Le 12/05/2022 à 16:57, Eneko Lacunza via pve-user a écrit :
> Finally we have worked around this issue downgrading to kernel 5.13:
>
> apt-get install proxmox-ve=7.1-1; apt-get remove
> pve-kernel-5.15.35-1-pve (+reboot)
>
> No need to downgrade pve-qemu-kvm no qemu-server .
>
> Sadly VMs running on kernel 5.15.35-1 will crash on live migration :-(
Hi Eneko,
It is strange, as I don't see anybody saying they saw this problem on
the forum :
https://forum.proxmox.com/threads/proxmox-ve-7-2-released.108970/page-3
Also, I installed a few weeks ago the kernel 3.15.30-1 that was
available for test on PVE 7.1, on my production servers, that solved for
me another problem (windows VM not rebooting correctly), and I don't see
the problem you encountered.
# uname -r
5.15.30-1-pve
I will test the upgrade shortly.
Alain
--
Administrateur Système/Réseau
C2N Centre de Nanosciences et Nanotechnologies (UMR 9001)
Boulevard Thomas Gobert (ex Avenue de La Vauve), 91120 Palaiseau
Tel : 01-70-27-06-88 Bureau A255
next parent reply other threads:[~2022-05-12 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.119.1652279766.362.pve-user@lists.proxmox.com>
[not found] ` <mailman.131.1652340849.362.pve-user@lists.proxmox.com>
[not found] ` <1b089826-050a-35ca-20b8-611f8bf64cf0@binovo.es>
[not found] ` <mailman.152.1652367475.362.pve-user@lists.proxmox.com>
2022-05-12 15:12 ` Alain Péan [this message]
[not found] ` <mailman.156.1652373323.362.pve-user@lists.proxmox.com>
2022-05-12 17:23 ` Gilberto Ferreira
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=7d6f9cc7-1dfe-63aa-b166-64d7f9b4c816@c2n.upsaclay.fr \
--to=alain.pean@c2n.upsaclay.fr \
--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