Re-introduce mistakenly dropped frontend state logic...

...from commit c9b6e56e "Cope with unexpected initial backend states" to
handle a backend that is already connected (for cases where Windows is
booted via iSCSI).

Signed-off-by: Eytan Heidingsfeld <eytanh@gmail.com>
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>

diff --git a/src/xenvif/frontend.c b/src/xenvif/frontend.c
index b682b2ca1460195f24981b9aee8a8e5e6851da12..0fbd64036a3d0a37fd64fd8f07ebd5d3f1419114 100644 (file)
--- a/src/xenvif/frontend.c
+++ b/src/xenvif/frontend.c
@@ -1535,6 +1535,11 @@ FrontendPrepare(
                                    XenbusStateInitialising);
             break;
 
+        case XenbusStateConnected:
+            FrontendSetXenbusState(Frontend,
+                                   XenbusStateClosing);
+            break;
+
         case XenbusStateClosing:
             FrontendSetXenbusState(Frontend,
                                    XenbusStateClosed);