mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-10-30 09:53:10 +00:00
virDriverFeatureIsGlobal: Handle VIR_DRV_FEATURE_NETWORK_UPDATE_HAS_CORRECT_ORDER
The fix was on RPC level so everything should advertise it. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
This commit is contained in:
parent
963ac787c4
commit
5c95340100
@ -357,10 +357,14 @@ virDriverFeatureIsGlobal(virDrvFeature feat,
|
|||||||
* At this point everything supports them and thus also drivers need to
|
* At this point everything supports them and thus also drivers need to
|
||||||
* always advertise this feature */
|
* always advertise this feature */
|
||||||
case VIR_DRV_FEATURE_TYPED_PARAM_STRING:
|
case VIR_DRV_FEATURE_TYPED_PARAM_STRING:
|
||||||
|
/* Feature flag exposes that the accidental switching of order of arguments
|
||||||
|
* in the public API trampoline virNetworkUpdate is known. Updated clients
|
||||||
|
* thus use the correct ordering with an updated server. All drivers must
|
||||||
|
* signal support for this feature. */
|
||||||
|
case VIR_DRV_FEATURE_NETWORK_UPDATE_HAS_CORRECT_ORDER:
|
||||||
*supported = 1;
|
*supported = 1;
|
||||||
return true;
|
return true;
|
||||||
|
|
||||||
case VIR_DRV_FEATURE_NETWORK_UPDATE_HAS_CORRECT_ORDER:
|
|
||||||
case VIR_DRV_FEATURE_FD_PASSING:
|
case VIR_DRV_FEATURE_FD_PASSING:
|
||||||
case VIR_DRV_FEATURE_MIGRATION_V2:
|
case VIR_DRV_FEATURE_MIGRATION_V2:
|
||||||
case VIR_DRV_FEATURE_MIGRATION_V3:
|
case VIR_DRV_FEATURE_MIGRATION_V3:
|
||||||
|
Loading…
Reference in New Issue
Block a user