|  |  | 
  
    |  |  | 
 
  |   |  | 
  
    |  |  | 
  
    |  |  | 
  
    |   xen-users
[Xen-users] Long delay between xen/HVM domU shutdown and releasing	vbd ( 
| 
Hi,
I have a running LVM-DRBD-Xen-HVM/Win2k3 cluster-stack under debian/
lenny managed by heartbeat/crm.
At takeover/failover heartbeat first is stopping my HVM-domU with 
success apparently: 
-------------- corresponding heartbeat log line -----------------
greatmama-n2 lrmd: [3382]: info: RA output: 
(xendom_infra_win:stop:stdout) Domain infra-win2003sbs terminated All 
domains terminated 
---------------------------------
But it seems regarding VBDs (drbd) are not released at this time. 
xend.log and investigation at manual domU shutdown shows a delay about 
(exactly?) 5 mins between success of xen RA in stopping the domU and 
finally releasing the vbd and performing poweroff :( 
How can I speed up this? Or better: Why returns 'xm shutdown  <dom-id> -w'
Domain <dom-id> terminated
All domains terminated
prior releasing all devices?
THX for any hints
Robert
------- xend.log --------------
[2009-07-24 13:53:35 3143] DEBUG (XendDomainInfo:467)
XendDomainInfo.shutdown(poweroff)
[2009-07-24 13:53:35 3143] DEBUG (XendDomainInfo:1092)
XendDomainInfo.handleShutdownWatch
[2009-07-24 13:58:35 3143] INFO (XendDomainInfo:1283) Domain has
shutdown: name=infra-win2003sbs id=17 reason=poweroff.
[2009-07-24 13:58:35 3143] DEBUG (XendDomainInfo:1897)
XendDomainInfo.destroy: domid=17
[2009-07-24 13:58:35 3143] DEBUG (XendDomainInfo:1914)
XendDomainInfo.destroyDomain(17)
[2009-07-24 13:58:36 3143] DEBUG (XendDomainInfo:1529) Destroying device
model
[2009-07-24 13:58:36 3143] DEBUG (XendDomainInfo:1536) Releasing devices
[2009-07-24 13:58:36 3143] DEBUG (XendDomainInfo:1542) Removing vif/0
[2009-07-24 13:58:36 3143] DEBUG (XendDomainInfo:590)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2009-07-24 13:58:36 3143] DEBUG (XendDomainInfo:1542) Removing vbd/768
[2009-07-24 13:58:36 3143] DEBUG (XendDomainInfo:590)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
--------------- xm info -----------------------------
host                   : greatmama-n1
release                : 2.6.26-2-xen-amd64
version                : #1 SMP Sun Jun 21 08:09:04 UTC 2009
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2333
hw_caps                : 
bfebfbff:20000800:00000000:00000140:000ce3bd:00000000:00000001 
total_memory           : 4093
free_memory            : 3100
node_to_cpu            : node0:0-3
xen_major              : 3
xen_minor              : 2
xen_extra              : -1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.3.1 (Debian 4.3.1-2)
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Sat Jun 28 09:32:18 UTC 2008
xend_config_format     : 4
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 | 
 
| <Prev in Thread] | Current Thread | [Next in Thread> |  | 
[Xen-users] Long delay between xen/HVM domU shutdown and releasing	vbd (drbd),
"Robert Zöhrer | pronet.at" <=
 |  |  | 
  
    |  |  |