From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] EPYC ZEN gen1 migration success after installing amd64 microcode (FYI)
Date: Fri, 8 Sep 2023 16:47:55 +0000 [thread overview]
Message-ID: <ad4cfdb1b2ebb0e7257d47b5eb136c562fc3d835.camel@groupe-cyllene.com> (raw)
In-Reply-To: <9469FB55-A455-493E-8C65-CCCB3932BF63@volny.cz>
Hi,
I known that amd have disable some buggy features in zen cpu recently.
I'm always using amd64-microde && intel-microcode on my proxmox
servers,
but maybe it could be great to install them by default in proxmox iso
installation?
Le vendredi 08 septembre 2023 à 15:44 +0200, Jan Vlach a écrit :
> Hi proxmox users,
>
> just a quick heads up:
>
> I have cluster with AMD EPYC 7551P 32-Core Processor (single socket)
> and AMD EPYC 7281 16-Core Processor (dual socket). Both are ZEN gen1.
>
> I’m running 8-node PVE7 with ZFS underneath.
>
> Without enabling 'non-free’ and installing amd64-microcode (& reboot)
> the migration completed successfully, but VM was frozen. No
> networking, no console.
>
> After installing amd64-microcode, live migration works fine both
> ways.
>
> This wasn’t obvious for me, so just FYI, maybe it saves some time for
> somebody :)
>
> JV
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2023-09-08 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 13:44 Jan Vlach
2023-09-08 16:47 ` DERUMIER, Alexandre [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=ad4cfdb1b2ebb0e7257d47b5eb136c562fc3d835.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.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