From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nathan March <nathan@gt.net>
Subject: Xenwatch crash on migration
Date: Mon, 05 Dec 2011 12:40:29 -0800
Message-ID: <4EDD2C3D.3090807@gt.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/options/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

Running into an intermittant issue where the domU xenwatch thread gets 
stuck in D mode on migration:

root        17  0.0  0.0      0     0 ?        D    Sep13   0:00  \_ 
[xenwatch]

It was in S before attempting the migration and once it goes into D the 
only option is to destroy the VM.

Dom0 - xen 4.1.1, kernel 3.0.3
Domu - kernel 2.6.32.27, 64bit pvops

Haven't found any indication of an error anywhere, not sure how to debug 
further since I can't attach to the thread with anything.

Possibly related to "xen/pv-on-hvm kexec: prevent crash in 
xenwatch_thread() when stale watch events arrive"?

- Nathan

-- 
Nathan March<nathan@gt.net>
Gossamer Threads Inc. http://www.gossamer-threads.com/
Tel: (604) 687-5804 Fax: (604) 687-5806