WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: [Xen-devel] tap:qcow causes dom-U to hang in 3.0.3

To: Roland Paterson-Jones <roland@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] tap:qcow causes dom-U to hang in 3.0.3
From: Roland Paterson-Jones <roland@xxxxxxxxxxxx>
Date: Tue, 14 Nov 2006 12:50:14 +0200
Cc: Julian Chesterfield <jac90@xxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 14 Nov 2006 02:50:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45599614.3040103@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4551EEC3.3010308@xxxxxxxxxxxx> <20061108151133.GE3507@xxxxxxxxxxxxxxxxxxxxxx> <4552DF8D.6060600@xxxxxxxxxxxx> <ab5e402899c3a334735d24815f36eaac@xxxxxxxxx> <455485FF.7040809@xxxxxxxxxxxx> <1a16a93e920ce8db7c8ed8cd908a876b@xxxxxxxxx> <45599614.3040103@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
Roland Paterson-Jones wrote:

Julian Chesterfield wrote:


There's a bunch of DPRINTFs in the code which send debug output to syslog. You can play with syslog settings to switch on the debug messages and direct them to a log file.

Here is another clue from syslog. Below is the full log, but the hang seems to accur when the following log messages are triggered (there's a bunch of them at the end):

Nov 14 11:59:47 dom0-0-50-45-5d-6a-bc TAPDISK: AIO_LOCK or iocb_free_count (0) failed[869040]

And when I try to 'xm destroy' the instance after it hangs, I get a slew of the following :

Nov 14 12:41:35 dom0-0-50-45-5d-6a-bc kernel: blk_tap: invalid kernel buffer -- could not remap it
Nov 14 12:41:35 dom0-0-50-45-5d-6a-bc kernel: blk_tap: Reached Fail_flush
Nov 14 12:41:35 dom0-0-50-45-5d-6a-bc kernel: blk_tap: BLKTAP_INVALID_HANDLE

This is the inverse of the error messages I see when I build the user-land tools myself. In the above it's the kernel buffer that can't be re-mapped. With my user-land tools it's the user buffer that can't be remapped. I wonder (but have no idea) whether this is related to PAE at all.

Roland

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