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

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

To: Roland Paterson-Jones <roland@xxxxxxxxxxxx>
Subject: [Xen-users] Re: [Xen-devel] tap:qcow causes dom-U to hang in 3.0.3
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Wed, 8 Nov 2006 15:11:33 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 08 Nov 2006 07:12:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4551EEC3.3010308@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4551EEC3.3010308@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Wed, Nov 08, 2006 at 04:50:43PM +0200, Roland Paterson-Jones wrote:

> Hi all
> 
> I have had some success with the new blktap support in Xen 3.0.3. In 
> particular, the loopback drop-in, tap:aio: works somewhat reliably.
> 
> However, I am really interested in copy-on-write support, and hence have 
> been trying tap:qcow:. This has had limited success, in that dom-U's 
> appear to launch. However, as soon as I try to console or ssh into the 
> dom-U's they apparently freeze, and I can get no further with them.
> 
> I have managed to 'xm terminate' the frozen dom-U's, but this leaves 
> xend in some inconsistent state. All further 'xm xxx' commands barf with 
> the following error:
> 
> [root@dom0]# xm list
> Error: Device 2050 not connected
> Usage: xm list [options] [Domain, ...]
> 
> Curiously, it seems that device 2050 was a secondary block device 
> exposed using phy:.
> 
> So, any advice on how to debug this?

Could we see your /var/log/xen/*  and the output of xenstore-ls?

Thanks,

Ewan.

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