On 31.10.2025 11:22, Roger Pau Monné wrote: > On Tue, Oct 28, 2025 at 04:32:17PM +0100, Jan Beulich wrote: >> Both patches also want 'x86/CPU: extend is_forced_cpu_cap()'s "reach"' in >> place. >> >> 1: disable RDSEED on Fam17 model 47 stepping 0 >> 2: disable RDSEED on most of Zen5 > > For both patches: don't we need to set the feature in the max policy > to allow for incoming migrations of guests that have already seen the > feature?
No, such guests should not run on affected hosts (unless overrides are in place), or else they'd face sudden malfunction of RDSEED. If an override was in place on the source host, an override will also need to be put in place on the destination one. Jan
