It was possible that WdfRequestComplete was called on a cancelled
request.

The MessageId parameter was used to decide if the interrupt should be
handled as a queue notification. The problem was that a value of zero
caused skipping setting the interruprt as serviced.

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

Signed-off-by: Joseph Hindin <yhindin@rehat.com>

The balloon's service didn't take any action on SERVICE_CONTROL_SHUTDOWN
notification. This caused a BSOD when the verifier was used on the balloon
driver because the service didn't exit and kept an open file handle to
the driver.

The device's hardward id was too short and because of that Windows didn't
load the driver if the device was hot-plugged in a different address.

The WHQL test "DF - Reinstall with IO Before and After" failed when
it installed the driver without uninstalling it first. This cause the
coinstaller CNG provider registration to fail with a name collision
error.

The registation was changed to override existing information.

Signed-off-by: Joseph Hindin <yhindin@rehat.com>
(cherry picked from commit b07fe167)

Conflicts:
	vioscsi/vioscsi.c

Signed-off-by: Iuliu Rus <iuliur@google.com>

based on 23de1376b695c28432fbbc55584644188c4e51ef
commit 23de1376b695c28432fbbc55584644188c4e51ef
Author: Julius Rus <iuliur@google.com>
Date:   Sun Oct 19 16:12:16 2014 -0700

    Only enable hotplug if the host advertises it.

Signed-off-by: Iuliu Rus <iuliur@google.com>

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.

Signed-off-by: Iuliu Rus <iuliur@google.com>

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.

Signed-off-by: Iuliu Rus <iuliur@google.com>

Signed-off-by: Iuliu Rus <iuliur@google.com>