From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nathan Gamber <ngamber@liquidweb.com>
Subject: xm shutdown times out with 2.6.36-rc5 kernel
Date: Fri, 24 Sep 2010 11:15:19 -0400
Message-ID: <4C9CC087.70902@liquidweb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=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

  Hello,

I recently had to upgrade my Ubuntu 10.04 domUs to a 2.6.36-rc5 kernel 
for various reasons (a main one being the mainlined pv drivers), and I'm 
no longer able to use xm shutdown. After a while, I see the following in 
xend.log:

[2010-09-24 15:02:10 2405] INFO (XendDomainInfo:1939) Domain shutdown 
timeout expired: name=TXJYEJ id=12

Watching dmesg within the child instance, I see nothing logged there. 
The parent dom0 is running xen 3.4.2. Is this a known issue, am I doing 
something wrong, or?

-Nathan