[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] changeset:6989 vm sticking around in shutdown state


  • To: xen-devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>
  • Date: Thu, 22 Sep 2005 09:13:11 -0400
  • Delivery-date: Thu, 22 Sep 2005 13:10:47 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

changeset:6989 
FC4, Tyan 2462 SMP Athlon

Had a domU get stuck in shutdown state after issuing an init 0 from its
console.

Issuing an xm destroy had no affect.

On a good note, the memory assigned to it was given back and I cloned
the config with a new name and the domU was recreated. Also the 
xend-debug.log is very quite, meaning not a single line written to it.

It took a few restarts of that particular domU to make it happen.

Questions?

Is their any difference between issuing an init 0 at a domU's console
versus doing an xm shutdown from the domO?


Looking over the xend.log nothing is jumping out at me, what should I be
looking for if indeed their is something that should be their with
relation to the vm sticking around?


Best Regards,
Ted



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.