From a63fae38cd6b72dfd1fb2d0d6aa50cdc9b1ff6e1 Mon Sep 17 00:00:00 2001 From: Jon Ludlam Date: Fri, 24 Sep 2010 17:32:28 +0100 Subject: [PATCH] The storage backends use sm-config for various bits of per-vdi info. We shouldn't copy that when cloning/copying a VDI. Signed-off-by: Jon Ludlam --- ocaml/xapi/xapi_vdi.ml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ocaml/xapi/xapi_vdi.ml b/ocaml/xapi/xapi_vdi.ml index 80a95e5e..5520cf95 100644 --- 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; -- 2.39.5