From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: changeset:6989 vm sticking around in shutdown state Date: Thu, 22 Sep 2005 09:13:11 -0400 Message-ID: <1127394791.23958.283.camel@pluto.linsolutions.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7BIT Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List List-Id: xen-devel@lists.xenproject.org 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