All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: mike tancsa <mike@sentex.net>, kvm@vger.kernel.org
Subject: Re: Guest migration between different Ryzen CPU generations
Date: Thu, 9 Jun 2022 16:01:38 +0200	[thread overview]
Message-ID: <0fa08623-22c3-d6c6-d068-4582bd8d2424@redhat.com> (raw)
In-Reply-To: <48353e0d-e771-8a97-21d4-c65ff3bc4192@sentex.net>

On 5/31/22 19:00, mike tancsa wrote:
> On Ubuntu 22 LTS, with the original kernel from release day, I can 
> migrate VMs back and forth between a 3700x and a 5800x without issue
> On Ubuntu 22 LTS with everything up to date as of mid May 2022, I can 
> migrate from the 3700X to the 5800x without issue. But going from the 
> 5800x to the 3700x results in a migrated VM that either crashes inside 
> the VM or has the CPU pegged at 100% spinning its wheels with the guest 
> frozen and needing a hard reset. This is with --live or without and with 
> --unsafe or without. The crash / hang happens once the VM is fully 
> migrated with the sender thinking it was successfully sent and the 
> receiver thinking it successfully arrived in.
> On stock Ubuntu 22 (5.15.0-33-generic) I can migrate back and forth to 
> Ubuntu 20 as long as the hardware / cpu is identical (in this case, 3700x)
> On Ubuntu 22 LTS with everything up to date as of mid May 2022 with 
> 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22. I 
> can migrate VMs back and forth that have as its CPU def EPYC or 
> EPYC-IBPB. If the def (in my one test case anyways) is Nehalem then I 
> get a frozen VM on migration back to the 3700X.
Hi, this is probably related to the patch at 
https://www.spinics.net/lists/stable/msg538630.html, which needs a 
backport to 5.15 however.

Note that using Intel definitions on AMD or vice versa is not going to 
always work, though in this case it seems to be a regression.

Paolo

  parent reply	other threads:[~2022-06-09 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 17:00 Guest migration between different Ryzen CPU generations mike tancsa
2022-06-02 12:42 ` Igor Mammedov
2022-06-02 15:09   ` mike tancsa
2022-06-02 21:46     ` Sean Christopherson
2022-06-03 13:18       ` mike tancsa
2022-06-03 15:09         ` Sean Christopherson
2022-06-09 14:01 ` Paolo Bonzini [this message]
2022-06-09 14:08   ` mike tancsa
2022-06-09 14:31     ` Paolo Bonzini

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=0fa08623-22c3-d6c6-d068-4582bd8d2424@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mike@sentex.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.