[Xen-changelog] [xen-3.1-testing] [Xend] Fix problem when destroying VMs using the Xen-API

["Xen patchbot-3.1-testing" <patchbot-3.1-testing@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1196957672 0
# Node ID 912279dd383616d6031b7f646a3f5e47c76e02d9
# Parent  c6776b6da8ee887ef42875afb856ae5b800c4dc1
[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@xxxxxxxxxx>
xen-unstable changeset:   15587:00fabe66d79e46de1d1318fd545ddbde734a8137
xen-unstable date:        Fri Jul 13 13:43:29 2007 +0100
---
 tools/python/xen/xend/XendDomainInfo.py |    1 +
 1 files changed, 1 insertion(+)

diff -r c6776b6da8ee -r 912279dd3836 tools/python/xen/xend/XendDomainInfo.py
--- a/tools/python/xen/xend/XendDomainInfo.py   Wed Nov 14 23:35:43 2007 +0000
+++ b/tools/python/xen/xend/XendDomainInfo.py   Thu Dec 06 16:14:32 2007 +0000
@@ -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()
 

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