[Xen-devel] xend: managed configuration not saved after VIF/VBD_destroy

["Dube, Lutz" <lutz.dube@xxxxxxxxxxxxxx>]

XendAPI fix:

After VBD_destroy and VIF_destroy the managed config must be saved, otherwise

already deleted devices appear again in configuration after a xend restart.

 

Signed-off-by: Lutz.Dube@xxxxxxxxxxxxxx

 

diff -r 1a911fd65e52 -r 315952bf2259 tools/python/xen/xend/XendAPI.py

--- a/tools/python/xen/xend/XendAPI.py  Fri Dec 18 07:53:27 2009 +0000

+++ b/tools/python/xen/xend/XendAPI.py  Mon Dec 28 14:37:37 2009 +0100

@@ -2053,6 +2053,7 @@

 

         XendTask.log_progress(0, 100, vm.destroy_vbd, vbd_ref)

 

+        xendom.managed_config_save(vm)

         return xen_api_success_void()

 

     def _VBD_get(self, vbd_ref, prop):

@@ -2220,6 +2221,8 @@

             return xen_api_error(['HANDLE_INVALID', 'VIF', vif_ref])

 

         vm.destroy_vif(vif_ref)

+

+        xendom.managed_config_save(vm)

         return xen_api_success_void()

 

     def _VIF_get(self, ref, prop):

 

 

 

 

---

Kind regards

Lutz Dube

 

 

Attachment: xendapi_mgmt_save
Description: xendapi_mgmt_save

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel