From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Failed live migration on Supermicro with EPYCv1 - what's going on here?
Date: Mon, 23 Oct 2023 07:54:12 +0000 [thread overview]
Message-ID: <f2a9bf7df276fddd2d0679defed376beb785e9fc.camel@groupe-cyllene.com> (raw)
In-Reply-To: <D60E11E5-5680-4B42-8755-D3BF052C6548@volny.cz>
you should really avoid to use "host" for live migration, and use the
correct qemu model (EPYC-v1 for example).
Are you sure that both CPU have exactly the same microcode version ?
(same supermicro bios version or same amd-microcode package if you
have installed it )
-------- Message initial --------
De: Jan Vlach <janus@volny.cz>
Répondre à: Proxmox VE user list <pve-user@lists.proxmox.com>
À: Proxmox VE user list <pve-user@lists.proxmox.com>
Objet: Re: [PVE-User] Failed live migration on Supermicro with EPYCv1 -
what's going on here?
Date: 22/10/2023 15:00:13
Hi,
I’m using “host” there as both the CPU and HW platform (Supermicro
H11DSU-iN) are the same.
JV
> On 20. 10. 2023, at 15:56, DERUMIER, Alexandre
> <alexandre.derumier@groupe-cyllene.com> wrote:
>
> Hi,
>
> what is the cpu model of the vms ?
>
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2023-10-23 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 9:52 Jan Vlach
2023-10-20 13:56 ` DERUMIER, Alexandre
2023-10-22 13:00 ` Jan Vlach
2023-10-23 7:54 ` DERUMIER, Alexandre [this message]
2023-11-20 15:21 ` Jan Vlach
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=f2a9bf7df276fddd2d0679defed376beb785e9fc.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