On 10/1/25 23:59, Pierrick Bouvier wrote:
On 1/10/25 13:29, Philippe Mathieu-Daudé wrote:
On 10/1/25 17:30, Peter Maydell wrote:
On Thu, 19 Dec 2024 at 18:32, Pierrick Bouvier
<pierrick.bouv...@linaro.org> wrote:
Signed-off-by: Pierrick Bouvier <pierrick.bouv...@linaro.org>
---
docs/system/arm/virt.rst | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/docs/system/arm/virt.rst b/docs/system/arm/virt.rst
index d25275c27ce..9f1457cf9a2 100644
--- a/docs/system/arm/virt.rst
+++ b/docs/system/arm/virt.rst
+VM migration is not guaranteed when using ``-cpu max``, as features
supported
+may change between QEMU versions. To ensure your VM can be
migrated, it is
+recommended to use another cpu model instead.
This paragraph is good, though -- that 'max' doesn't work for migration
is important, and we should definitely document that.
Ah yes, I've been there. 2 close-by comments:
- 'max' is not restricted to the 'virt' ARM machine, but this document
is about it, what about other ARM machines?
- More generally, "max" CPU won't migrate easily (in different versions)
on all target archs.
Not sure where to document that; maybe a generic chapter that can be
included in a board.rst template?
It's a good point.
Maybe somewhere in docs/devel/migration, where versioning is mentioned?
Yep. docs/devel/migration/compatibility.rst sounds the best place.
