On Thu, Sep 22, 2022 at 12:24:09PM +0100, Daniel P. Berrangé wrote: > On Thu, Sep 22, 2022 at 12:14:54PM +0200, Gerd Hoffmann wrote: > > In case phys bits are functional and can be used by the guest (aka > > host-phys-bits=on) add a fw_cfg file carrying the value. This can > > be used by the guest firmware for address space configuration. > > > > The value in the etc/phys-bits fw_cfg file should be identical to > > the phys bits value published via cpuid leaf 0x80000008. > > > > This is only enabled for 7.2+ machine types for live migration > > compatibility reasons. > > Is this going to have any implications for what mgmt apps must > take into account when selecting valid migration target hosts ? > > Historically, apps have tended to ignore any checks for phys > bits between src/dst migration hosts and hoped for the best. > > Will this new behaviour introduce / change any failure scenarios > where the target host has fewer phys bits than the src host, that > mgmt apps need to be made aware of ? No. This will basically inform the guest that host-phys-bits has been enabled (and pass the number of bits). So the firmware can make use of the available address space instead of trying to be as conservative as possible to avoid going beyond the (unknown) limit. The phys-bits config itself is not touched. take care, Gerd
