On second though - this is not something that needs to be configured by the deployer - it's on always, and just a matter of whether you use it or not.
It's a feature that can be taken advantage of when creating flavours, and should probably be documented there, with caveats about which hypervisors support it at current.
On second though - this is not something that needs to be configured by the deployer - it's on always, and just a matter of whether you use it or not.
It's a feature that can be taken advantage of when creating flavours, and should probably be documented there, with caveats about which hypervisors support it at current.