From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christopher S. Aker" Subject: DomU stuck in "s" state in -unstable Date: Thu, 21 Apr 2005 19:28:23 -0500 Message-ID: <000e01c546d2$32c6e820$0201a8c0@hawk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Using yesterday's unstable: (domU): INIT: Switching to runlevel: 0 INIT: Sending processes the TERM signal ... Power down. Ok, good... [root@host27 xen]# xm destroy xen8 [root@host27 xen]# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 33589.1 xen8 24 0 1 ---s- 43.4 9624 /var/log/xend.log loops the following: DEBUG (XendDomain:244) XendDomain>reap> domain died name=xen8 id=24 DEBUG (XendDomain:247) XendDomain>reap> shutdown id=24 reason=poweroff DEBUG (XendDomain:487) domain_restart_schedule> 24 poweroff 0 INFO (XendDomain:564) Destroying domain: name=xen8 DEBUG (XendDomainInfo:673) Closing console, domain 24 INFO (XendRoot:112) EVENT> xend.domain.exit ['xen8', '24', 'poweroff'] INFO (XendRoot:112) EVENT> xend.domain.destroy ['xen8', '24'] -Chris