FWIW - I think we should just be failing the guest and provide a non-criptic message. That's the only way to ensure that there is a clear unambiguos semantics of the extra specs we have introduced.
Allowing partial support will lead to even more confusion from the users.
We skip the missing capabilities already (and that is fine because we don't want to be crashing the compute service) but when we detect that a capability was requested that cannot be unambiguously executed.
We may even want to do this at the scheduler level.
FWIW - I think we should just be failing the guest and provide a non-criptic message. That's the only way to ensure that there is a clear unambiguos semantics of the extra specs we have introduced.
Allowing partial support will lead to even more confusion from the users.
We skip the missing capabilities already (and that is fine because we don't want to be crashing the compute service) but when we detect that a capability was requested that cannot be unambiguously executed.
We may even want to do this at the scheduler level.