3 of 3 people found this helpful
This was added to allow Discovery to run on HyperV in Azure. Assuming that you are not doing this then it is not a problem.
Hi Andrew, We would like to know why this module got failed during OS upgrade, is there a way? and how can we fix this? November month OS upgrade we have not come across this message. We experienced this module errors during upgrading the to the December release of OSU for Centos 7.
2 of 2 people found this helpful
It is looking for some HyperV specific things in the virtualised hardware. There is nothing to fix.