On 21.01.2015 11:15, Daniel P. Berrange wrote:
On Wed, Jan 21, 2015 at 11:08:54AM +0100, Michal Privoznik wrote:
On 20.01.2015 17:37, Daniel P. Berrange wrote:
For stateless, client side drivers, it is never correct to
probe for secondary drivers. It is only ever appropriate to
use the
On 20.01.2015 17:37, Daniel P. Berrange wrote:
For stateless, client side drivers, it is never correct to
probe for secondary drivers. It is only ever appropriate to
use the secondary driver that is associated with the
hypervisor in question. As a result the ESX HyperV drivers
have both been
On Wed, Jan 21, 2015 at 11:08:54AM +0100, Michal Privoznik wrote:
On 20.01.2015 17:37, Daniel P. Berrange wrote:
For stateless, client side drivers, it is never correct to
probe for secondary drivers. It is only ever appropriate to
use the secondary driver that is associated with the
For stateless, client side drivers, it is never correct to
probe for secondary drivers. It is only ever appropriate to
use the secondary driver that is associated with the
hypervisor in question. As a result the ESX HyperV drivers
have both been forced to do hacks where they register no-op
