Quoting Jiri Denemark (2018-07-12 06:59:18)
> On Mon, Jul 09, 2018 at 22:56:47 -0500, Chris Venteicher wrote:
> > Renamed variable in CPUModelInfo such that
> > props_migratable_valid is true when properties in CPUModelInfo
> > have been updated to accurately indicate if property is / isn't
> >
On Mon, Jul 09, 2018 at 22:56:47 -0500, Chris Venteicher wrote:
> Renamed variable in CPUModelInfo such that
> props_migratable_valid is true when properties in CPUModelInfo
> have been updated to accurately indicate if property is / isn't
> migratable.
>
> Property migratability is not returned
Quoting Collin Walling (2018-07-11 18:25:00)
> Not sure if I agree with the renaming here.
>
> From what I understand, "if a cpu property is not migratable, then the
> cpu model is also not migratable".
>
> So I think the original naming scheme is fine.
Very much welcome the feedback here
Not sure if I agree with the renaming here.
>From what I understand, "if a cpu property is not migratable, then the
cpu model is also not migratable".
So I think the original naming scheme is fine.
On 07/09/2018 11:56 PM, Chris Venteicher wrote:
> Renamed variable in CPUModelInfo such that
>
Renamed variable in CPUModelInfo such that
props_migratable_valid is true when properties in CPUModelInfo
have been updated to accurately indicate if property is / isn't
migratable.
Property migratability is not returned directly in QMP messages but
rather is sometimes calculated within Libvirt
