On Thu, 18 Jan 2024 at 12:58, Fabiano Rosas <faro...@suse.de> wrote: > > Peter Maydell <peter.mayd...@linaro.org> writes: > > > On Wed, 17 Jan 2024 at 21:24, Fabiano Rosas <faro...@suse.de> wrote: > >> Peter Maydell <peter.mayd...@linaro.org> writes: > > The "max" CPU is a moving target, so you shouldn't expect > > to be able to migrate across QEMU versions using it: > > it can have different features and thus different ID > > register values between versions (as well as potentially > > different actual-register-state if the added feature adds > > new state). > > We're adding a test for migrating across QEMU versions to stop these > sort of breakages happening. If 'max' is not suitable for that scenario, > would there be another cpu you recommend to use? Otherwise aarch64 will > have to remain uncovered for migration across QEMU versions. > > There's no clear statement on what kinds of combinations we support for > migration, but anything that's actually tested is more likely to be > considered supported.
Any fixed defined CPU is a reasonable choice. I suggest neoverse-n1. I don't think 'max' is expected to migrate cross-version on any CPU architecture; this isn't Arm-specific. thanks -- PMM
