Get correct CPU index to make sure MQ in netkvm.

It might be Windows OS version specific. At WIn2008R2, KeGetProcessorIndexFromNumber would return INVALID_PROCESSOR_INDEX if PROCESS_NUMBER.Reserved is not zero. This bug effectively prevent NETKVM to use egress MQ and ingress RSS feature.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=77606984
Increase MessageNumberLimit for netkvm

netkvm driver only ask for at most 4 msi msg which is too little for a 8 core or 16 core VM. Bump it to 32.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=77958555
Setup correct Msg Index for ingress queue and egress queue for netkvm

Looking at GetPathByMessageId() routine which is used by ISR to find the relevant queue, messageId being set in ParaNdis_ConfigureMSIXVectors() is wrong, and would cause ISR to process the wrong queue.

Prior to the change, packet is often missed (delayed) even for TCP handshake because the ISR is polling the wrong queue for incoming packets.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=77958627
Merge branch 'moe_writing_branch_from_ac63b314e49e9057c7e213a332de1db386508f5b'