Reboot request keys should be volatile

When a driver makes a reboot request it should use a volatile registry key.
The monitor service will explicitly remove the key prior to reboot but,
if the reboot is initiated in some other way and the key is non-volatile,
the monitor service will then needlessly prompt for a second reboot.

Signed-off-by: Paul Durrant <paul.durrant@citrix.com>

diff --git a/src/xenvif/driver.c b/src/xenvif/driver.c
index 43a9c7b895816ff45d7d87582f51e8593aed0b14..8bc097afc5a758d2d2b0ba1d2f3c479d5b9c4445 100644 (file)
--- a/src/xenvif/driver.c
+++ b/src/xenvif/driver.c
@@ -206,7 +206,7 @@ __DriverRequestReboot(
 
     status = RegistryCreateSubKey(RequestKey,
                                   __MODULE__,
-                                  REG_OPTION_NON_VOLATILE,
+                                  REG_OPTION_VOLATILE,
                                   &SubKey);
     if (!NT_SUCCESS(status))
         goto fail3;