[Xen-users] Devices held in dom0 prevent domU restart

[Andy Smith <andy@xxxxxxxxxxxxxx>]

Hi,

On one of my servers, a user had to destroy a domU and the network
interface in dom0 did not get removed.  It still appears in
"ifconfig" and in "ip link" output.  I suspect the block devices are
still held as well.

"xenstore-ls /local/domain/0/backend" shows many entries for vbd and
vif for the particular domU that is not actually running, e.g.:

vbd = ""
 1 = ""
  51713 = ""
   domain = "testkl"
   frontend = "/local/domain/1/device/vbd/51713"
   uuid = "d3248bc8-bbb2-1c82-15f2-f734edcb3331"
   dev = "xvda1"
   state = "5"
   params = "vg00/testkl_root"
   mode = "w"
   online = "0"
   frontend-id = "1"
   type = "phy"
   physical-device = "fe:4"
   hotplug-status = "connected"
   sectors = "2097152"
   info = "0"
   sector-size = "512"
  51714 = ""
   domain = "testkl"
   frontend = "/local/domain/1/device/vbd/51714"
   uuid = "8b09ed06-dde4-f352-d4c3-a3efc98321cf"
   dev = "xvda2"
   state = "5"
   params = "vg00/testkl_swap"
   mode = "w"
   online = "0"
   frontend-id = "1"
   type = "phy"
   physical-device = "fe:6"
   hotplug-status = "connected"
   sectors = "2097152"
   info = "0"
   sector-size = "512"
  51715 = ""
   domain = "testkl"
   frontend = "/local/domain/1/device/vbd/51715"
   uuid = "a9d749fe-5dc7-5fde-f921-1f2bfa9444f3"
   dev = "xvda3"
   state = "5"
   params = "vg00/testkl_data"
   mode = "w"
   online = "0"
   frontend-id = "1"
   type = "phy"
   physical-device = "fe:5"
   hotplug-status = "connected"
   sectors = "6291456"
   info = "0"
   sector-size = "512"
[...]
 133 = ""
  51713 = ""
   domain = "testkl"
   frontend = "/local/domain/133/device/vbd/51713"
   uuid = "0d00cba1-e888-647a-eec0-1f87b415e9da"
   dev = "xvda1"
   state = "5"
   params = "vg00/testkl_root"
   mode = "w"
   online = "0"
   frontend-id = "133"
   type = "phy"
  51714 = ""
   domain = "testkl"
   frontend = "/local/domain/133/device/vbd/51714"
   uuid = "b2bbfcfa-6974-32c2-0b54-355b7d08ed12"
   dev = "xvda2"
   state = "5"
   params = "vg00/testkl_swap"
   mode = "w"
   online = "0"
   frontend-id = "133"
   type = "phy"
 134 = ""
  51713 = ""
   domain = "testkl"
   frontend = "/local/domain/134/device/vbd/51713"
   uuid = "015524c6-a8d8-8a7c-adf4-599393218555"
   dev = "xvda1"
   state = "5"
   params = "vg00/testkl_root"
   mode = "w"
   online = "0"
   frontend-id = "134"
   type = "phy"
  51714 = ""
   domain = "testkl"
   frontend = "/local/domain/134/device/vbd/51714"
   uuid = "30d07dd7-1807-d6fe-f82f-afbd9a50d325"
   dev = "xvda2"
   state = "5"
   params = "vg00/testkl_swap"
   mode = "w"
   online = "0"
   frontend-id = "134"
   type = "phy"
[...]
vif = ""
 1 = ""
  0 = ""
   domain = "testkl"
   handle = "0"
   uuid = "f47ed50b-af99-1ec2-5130-7d68e87afc01"
   script = "/etc/xen/scripts/vif-route"
   ip = "192.168.194.206"
   state = "5"
   frontend = "/local/domain/1/device/vif/0"
   mac = "00:16:4e:02:00:00"
   vifname = "v-testkl"
   online = "0"
   frontend-id = "1"
   feature-sg = "1"
   feature-gso-tcpv4 = "1"
   feature-rx-copy = "1"
   hotplug-status = "connected"
[...]

The domU now cannot be restarted due to claimed hotplug errors.  Is
there any way to clear this up so that the domU can be started
again?

Cheers,
Andy

signature.asc
Description: Digital signature

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