[Xend] Fix problem when destroying VMs using the Xen-API

When domains are destroyed/suspend-resume/migration using the Xen-API
things break due to the domid not having been reset. This patch fixes
this. This is the best place I found for fixing this problem. I could
not push this line into _stateSet() for the case of DOM_STATE_HALTED
and left a comment regarding this.

Signed-off-by: Stefan Berger <stefanb@us.ibm.com>
xen-unstable changeset:   15587:00fabe66d79e46de1d1318fd545ddbde734a8137
xen-unstable date:        Fri Jul 13 13:43:29 2007 +0100

diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py
index dc349aa613f4730e12b2456d54b3dc4c3d3c8790..f43d1a90b1edf4cb85572c85f21040eb9149eacf 100644 (file)
--- a/tools/python/xen/xend/XendDomainInfo.py
+++ b/tools/python/xen/xend/XendDomainInfo.py
@@ -1660,6 +1660,7 @@ class XendDomainInfo:
                 log.exception("Removing domain path failed.")
 
             self._stateSet(DOM_STATE_HALTED)
+            self.domid = None  # Do not push into _stateSet()!
         finally:
             self.refresh_shutdown_lock.release()