Description of problem:
  When i shutdown a xen domU (from inside the domU or via "xm shutdown") the
  domain does not get destroyed and still holds it's assigned memory until i 
  use "xm list". So unattended halts and boots will end up in dead domains
  blocking RAM.


Version-Release number of selected component (if applicable):
  xen-2-20050522
  kernel-xen0-2.6.11-1.1369_FC4
  kernel-xenU-2.6.11-1.1369_FC4


How reproducible:
  Always


Steps to Reproduce:
  xm shutdown domain
  # wait for "Power down."
  xm info | grep free_memory
  # wait as long as you like
  xm info | grep free_memory
  xm list
  sleep 2
  xm list
  xm info | grep free_memory


Actual results:
  The halted domain gets destroyed shortly after the first "xm list". Until 
  then, it's kept in state "s" ("shutdown"), memory still assigned.


Expected results:
  The halted domain gets destroyed (and memory freed) shortly after the domU
  kernel stops.


Additional info:
  I think this bug was discussed on xen-devel, so maybe it's fixed upstrem. 
  Example session:

  [root@crusher PW]# xm create -c bering
  Using config file "/etc/xen/bering".
  ...
  bering# halt
  ...
  Power down.
  # type Ctrl-]
  
  [root@crusher PW]# xm info | grep free_memory
  free_memory            : 231
  [root@crusher PW]# sleep 120

  [root@crusher PW]# xm info | grep free_memory
  free_memory            : 231
  [root@crusher PW]# xm list
  Name              Id  Mem(MB)  CPU  State  Time(s)  Console
  Domain-0           0      245    0  r----   1273.2        
  bering2            8       16    0  ---s-      0.5    9608
  [root@crusher PW]# xm list
  Name              Id  Mem(MB)  CPU  State  Time(s)  Console
  Domain-0           0      245    0  r----   1274.6        
  [root@crusher PW]# xm info | grep free_memory
  free_memory            : 247