Blame SOURCES/0003-vddk-Add-comment-about-my-experiment-with-PrepareFor.patch

b61625
From 1041402b8d919bd794ee0ca72017fa6e04d4675b Mon Sep 17 00:00:00 2001
b61625
From: "Richard W.M. Jones" <rjones@redhat.com>
b61625
Date: Tue, 24 Jul 2018 15:35:20 +0100
b61625
Subject: [PATCH] vddk: Add comment about my experiment with PrepareForAccess.
b61625
b61625
(cherry picked from commit ba593d2dfa3b3ccd4073f7bad7bcd2d67ce23b64)
b61625
---
b61625
 plugins/vddk/vddk.c | 5 +++--
b61625
 1 file changed, 3 insertions(+), 2 deletions(-)
b61625
b61625
diff --git a/plugins/vddk/vddk.c b/plugins/vddk/vddk.c
b61625
index 748f1b3..54b95fb 100644
b61625
--- a/plugins/vddk/vddk.c
b61625
+++ b/plugins/vddk/vddk.c
b61625
@@ -370,8 +370,9 @@ vddk_open (int readonly)
b61625
   }
b61625
 
b61625
   /* XXX Some documentation suggests we should call
b61625
-   * VixDiskLib_PrepareForAccess here.  However we need the true VM
b61625
-   * name to do that.
b61625
+   * VixDiskLib_PrepareForAccess here.  It may be required for
b61625
+   * Advanced Transport modes, but I could not make it work with
b61625
+   * either ESXi or vCenter servers.
b61625
    */
b61625
 
b61625
   DEBUG_CALL ("VixDiskLib_ConnectEx",
b61625
-- 
b61625
1.8.3.1
b61625