[Xen-changelog] If block-create didn't work, then chances are block-destroy doesn't work

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID 058e8087d36ab686e3ea7a873edf66d094b986d9
# Parent  f056b0cc171e2dade56b40ca9e464f9103849b38
If block-create didn't work, then chances are block-destroy doesn't work 
either right :-)

In this case, XendDomain.py is just calling a function that doesn't 
exist (device_destroy instead of device_delete).

Signed-off-by: Anthony Liguori <aliguori@xxxxxxxxxx>

diff -r f056b0cc171e -r 058e8087d36a tools/python/xen/xend/server/controller.py
--- a/tools/python/xen/xend/server/controller.py        Sat Aug 13 09:06:20 2005
+++ b/tools/python/xen/xend/server/controller.py        Sat Aug 13 09:06:44 2005
@@ -325,7 +325,7 @@
         return self.destroyed
 
     def getDevice(self, id, error=False):
-        dev = self.devices.get(id)
+        dev = self.devices.get(int(id))
         if error and not dev:
             raise XendError("invalid device id: " + str(id))
         return dev

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