On Tue, 2026-05-26 at 10:26 +0300, Michael Tokarev wrote: > On 11.05.2026 15:48, Zishun Yi wrote: > > Currently, the Machine Security Configuration Register (mseccfg) > > was > > missing from the live migration state. This omission causes the > > register > > to be reset to zero on the destination host after migration. > > > > Fixed by adding vmstate_mseccfg subsection > > > > This vulnerability was discovered and reported by SpecHunter, an > > AI-driven architecture specification analysis tool. > > > > Link: > > https://github.com/yizishun/rv-isa-sec/blob/a22e4459cd026ae970791dfbd9cfe5d110fbd46b/output/riscv-isa-manual/pr-1879/qemu.txt#L121 > > Signed-off-by: Zishun Yi <[email protected]> > > This change has been nominated for inclusion into previous stable > releases by Alistar. However I've a concern here: can we add new > fields to older machine descriptions this way, and stay migratable?
I was under the impression that we could, but as I write this I start to think that no we can't. We don't have to backport this then > > I understand riscv machine is not versioned. How does migration work > in the first place? As in the virt machine isn't versioned? or `vmstate_riscv_cpu` isn't versioned? Alistair > > Thanks, > > /mjt > >
