From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Paterson-Jones Subject: tap:qcow causes dom-U to hang in 3.0.3 Date: Wed, 08 Nov 2006 16:50:43 +0200 Message-ID: <4551EEC3.3010308@rolandpj.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: xen-users@lists.xensource.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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? Thanks and kind regards Roland