Tuesday, October 11, 2011

VM in Hyper-V Could not be Initialize

Part of knowledge sharing, have you wondering what does the error below give you? Event id 3040 or 3430, does this give you an indication. Think mostly the first thing you will check on google what it mean. Mostly the first thing we do will be check whether the INTEL VT is enable and the next step would be checking configuration.


Just for knowledge sharing, the problem could be minor configuration due to the permission as what have been documented http://support.microsoft.com/kb/2249906.

But there is one more findings you might see this is interesting, as you know HYPER-V is hardware assist type and it is fully depending on the CPU capabilities, does that mean we need to blame INTEL? :). Probably not ^^.

Let me share with you, this problem would only happen if the CPU support the new instruction set from 256 set instruction set extension on top of the SSE. The CPU capabilities is document on http://software.intel.com/en-us/avx/.

So what it mean to us?Is that mean each time when there is a new release of the processor we should not plan for upgrade or we don't use the latest CPU. To be frank,we just need to know more detail what would be the requirement and keep our HYPER-V to the latest patches.

On my lab, I am running I5 2500 INTEL Processor. On the previous testing, I do apply the workaround which have been documented in http://support.microsoft.com/kb/2517374.

The good news is the latest Microsoft Service Pack 1 have fix the problem!!!.

Hope this will give some information to you guys who face the problem.




No comments:

Post a Comment