The storage backends use sm-config for various bits of per-vdi info. We shouldn't...

Signed-off-by: Jon Ludlam <Jonathan.Ludlam@eu.citrix.com>

diff --git a/ocaml/xapi/xapi_vdi.ml b/ocaml/xapi/xapi_vdi.ml
index 80a95e5ed3bde46472641a4c62e858c2be5efb90..5520cf9552e07252a7f961a716ff66efa4b6c39c 100644 (file)
--- a/ocaml/xapi/xapi_vdi.ml
+++ b/ocaml/xapi/xapi_vdi.ml
@@ -447,7 +447,7 @@ let clone ~__context ~vdi ~driver_params =
       ~read_only:a.Db_actions.vDI_read_only
       ~other_config:a.Db_actions.vDI_other_config
       ~xenstore_data:a.Db_actions.vDI_xenstore_data
-      ~sm_config:a.Db_actions.vDI_sm_config ~tags:[]
+      ~sm_config:[] ~tags:[]
     in
     (try
        (* Remove the vdi_clone from the SR's current operations, this prevents the whole
@@ -488,7 +488,7 @@ let copy ~__context ~vdi ~sr =
           ~read_only:src.API.vDI_read_only
           ~other_config:src.API.vDI_other_config
           ~xenstore_data:src.API.vDI_xenstore_data
-          ~sm_config:src.API.vDI_sm_config ~tags:[] in
+          ~sm_config:[] ~tags:[] in
     if src.API.vDI_on_boot = `reset then begin
                try Client.VDI.set_on_boot ~rpc ~session_id ~self:result ~value:(`reset) with _ -> ()
        end;