[Xen-devel] [PATCH] xend: Fix vbd/tapdisk device destruction

[Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>]

Hi,

When I repeated creating and shutting off a guest domain, I detected 
that processes of tapdisk2 were left.  Then I saw the following error 
message in xend.log.

# xm create vm2
Using config file "/etc/xen/vm2".
Started domain vm2 (id=1)
# xm shutdown vm2
# xm create vm2
Using config file "/etc/xen/vm2".
Started domain vm2 (id=2)
# xm shutdown vm2
# xm create vm2
Using config file "/etc/xen/vm2".
Started domain vm2 (id=3)
# xm shutdown vm2
# xm create vm2
Using config file "/etc/xen/vm2".
Started domain vm2 (id=4)
# xm shutdown vm2
# ps aux | grep tapdisk2
root      3814  0.0  0.3   2748  2748 ?        SL   16:13   0:00 
/usr/sbin/tapdisk2 -n aio:/xen/root-vm2.img
root      4021  0.0  0.3   2752  2752 ?        SL   16:17   0:00 
/usr/sbin/tapdisk2 -n aio:/xen/root-vm2.img
root      4193  0.0  0.3   2748  2748 ?        SL   16:20   0:00 
/usr/sbin/tapdisk2 -n aio:/xen/root-vm2.img
root      4366  0.0  0.3   2748  2748 ?        SL   16:25   0:00 
/usr/sbin/tapdisk2 -n aio:/xen/root-vm2.img
root      4537  0.0  0.0   3892   668 pts/0    S+   16:33   0:00 grep tapdisk2

[2009-06-22 14:36:21 3626] DEBUG (XendDomainInfo:2221) Removing vbd/769
[2009-06-22 14:36:21 3626] DEBUG (XendDomainInfo:1137) 
XendDomainInfo.destroyDevice: deviceClass = tap, device = vbd/769
[2009-06-22 14:36:21 3626] ERROR (XendDomainInfo:2228) Device release failed: 
vm2; tap; vbd/769
Traceback (most recent call last):
  File "usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2222, 
in _releaseDevices
    self.destroyDevice(true_devclass, dev, False);
  File "usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1154, 
in destroyDevice
    path = self.getDeviceController(deviceClass).readBackend(dev, 
\047params\047)
  File "usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line 
467, in readBackend
    raise VmError("Device %s not connected" % devid)
VmError: Device 769 not connected


This patch solves the problem.  And the patch solves the detected 
problem by Ryan.

Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>

Best regards,
 Kan

Attachment: devicePath_Blktap.patch
Description: Binary data

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