|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-users
[Xen-users] Cannot detach block-devices
 
Hello.
I have some strange phenomenoma after I tried to detach and afterwards
reattach a block-device to a domU. The problems occured after some
problems with the underlying iscsi device that is accessed in dom0 and
via Xen attached to the domU.
I played around with "xm block-detach" "xm block-attach" and now I have
the following situation:
xm block-list gives me this output: 
[root@dom0]# xm block-list 19
Vdev  BE handle state evt-ch ring-ref BE-path
2050    0    0     4      52     8     /local/domain/0/backend/vbd/19/2050  
2053    0    0     4      53     9     /local/domain/0/backend/vbd/19/2053  
2054    0    0     4      54     10    /local/domain/0/backend/vbd/19/2054  
2055    0    0     4      55     11    /local/domain/0/backend/vbd/19/2055  
2056    0    0     4      56     12    /local/domain/0/backend/vbd/19/2056  
2057    0    0     4      57     13    /local/domain/0/backend/vbd/19/2057  
2065    0    0     4      58     14    /local/domain/0/backend/vbd/19/2065  
2066    0    0     4      59     15    /local/domain/0/backend/vbd/19/2066  
2081    0    0     4      60     16    /local/domain/0/backend/vbd/19/2081  
2145    0    0     4      62     18    /local/domain/0/backend/vbd/19/2145  
2161    0    0     4      63     19    /local/domain/0/backend/vbd/19/2161  
2177    0    0     4      64     20    /local/domain/0/backend/vbd/19/2177  
2128    0    0     1      -1     -1    /local/domain/0/backend/vbd/19/2128  
2129    0    0     1      -1     -1    /local/domain/0/backend/vbd/19/2129  
2193    0    0     1      -1     -1    /local/domain/0/backend/vbd/19/2193  
2209    0    0     1      -1     -1    /local/domain/0/backend/vbd/19/2209  
2225    0    0     1      -1     -1    /local/domain/0/backend/vbd/19/2225  
[root@dom0]# 
The entries with "evt-ch" and "ring-ref" = "-1" are the entries
belonging to the corresponding device.
xenstore-ls gives e.g.:
[root@dom0]# xenstore-ls /local/domain/0/backend/vbd/19/2225
domain = "domU"
frontend = "/local/domain/19/device/vbd/2225"
format = "raw"
dev = "sdl1"
state = "2"
params = "/dev/sdi1"
mode = "w"
online = "1"
frontend-id = "19"
type = "phy"
physical-device = "8:81"
hotplug-status = "connected"
[root@dom0]# 
"xm block-detach 19 2225" gives no output and has no visible effect.
With the --force options it says:
[root@dom0]# xm block-detach 19 2225 -f
Error: Device 2225 not connected
Usage: xm block-detach <Domain> <DevId> [-f|--force]
Destroy a domain's virtual block device.
[root@dom0]#
xend log the following during this operation:
[2009-07-03 13:55:11 xend.XendDomainInfo 1194] DEBUG (XendDomainInfo:1235) Check
ingif 'vbd' device 2225 is really a'tap' device
Btw: I cannot see this block device in the domU.
Another strange thing: "xm list" does not show this domU anymore! In xend.log 
it says:
[2009-07-03 13:58:46 xend 1194] WARNING (XMLRPCServer:66) Failed to
query SXPR for domain <domain id=19 name=domU memory=23000> 
In "xm top" it is still there and running.
Anybody having some ideas how to fix this?
Thanks a lot,
Ralf
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread> |  
- [Xen-users] Cannot detach block-devices,
Ralf Schulze <=
  
 |  
  
 | 
    | 
  
  
    |   | 
    |