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-devel

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

To: Julian Chesterfield <jac90@xxxxxxxxx>
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: Fri, 10 Nov 2006 16:17:01 +0200
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 10 Nov 2006 06:17:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <ab5e402899c3a334735d24815f36eaac@xxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
Julian Chesterfield wrote:

Roland,

Can you also verify whether there's an active tapdisk process running in Dom0 for each tap:{aio,qcow} vbd. We are aware of a bug with the qcow implementation that we hope to submit a fix for very soon. It's likely that you are seeing the same issue.

To answer your question, yes, it does appear that a tapdisk process is still running (this is after the dom-U has hung):

[root@dom0-0-50-45-5d-6a-bc ~]# ps -aef | grep tapdisk
root 4135 1 0 15:42 ? 00:00:01 tapdisk /dev/xen/tapctrlwrite1 /dev/xen/tapctrlread1

There is only one tap device, and the pid is the same as the single candidate while the dom-U was still reachable.

The hand seems to occur on the first (significant?) disk write inside the dom-U. For example:

-bash-3.00# dd if=/dev/zero of=./test-10MB bs=1k count=$((10*1024))

Has hung the dom-U, and I can no longer console or ssh into the dom-U.

Interestingly, on the dom-U, the qcow file has shrunk from its pervious peak of > 1TB, and is now appearing modestly as:

[root@dom0-0-50-45-5d-6a-bc ~]# ls -als /mnt/instance_image_store_0/
total 1564432
     4 drwxr-xr-x  2 root root       4096 Nov 10 15:42 .
     8 drwxr-xr-x  8 root root       4096 Nov  7 17:56 ..
1563132 -rw-r--r--  1 root root 1599078400 Nov 10 15:42 2
  1288 -rw-r--r--  1 root root    2466816 Nov 10 16:09 2.qcow

It's all very confusing. I'd love it to work, of course. Let me know what I can do to help with a diagnosis.

I'm running on the (binary) PAE-enabled 3.0.3 release.

Thanks and kind regards
Roland

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