From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: 3.0.3rc3 qcow image created with qemu-img not usable? Date: Thu, 12 Oct 2006 08:02:51 -0500 Message-ID: <452E3CFB.5030702@us.ibm.com> References: <452DFFE9.20606@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <452DFFE9.20606@gmx.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Timo Benk Cc: xen-devel List-Id: xen-devel@lists.xenproject.org You cannot attach block devices to Domain-0. Furthermore, you cannot attach non-raw file-based block devices to paravirtual domains. Regards, Anthony Liugoir Timo Benk wrote: > Hi, > > i am new to the qcow image format, so please forgive me if the following > is just totally stupid:-) > > I try to use a qcow formatted image in Xen created by qemu-img. > > # qemu-img create -f qcow /tmp/test.img 1G > > Then i try to attach that image to Domain-0. > > # xm block-attach Domain-0 tap:qcow:/tmp/test.img /dev/xvda1 w 0 > > No error message so far, but ... > > # mount /dev/xvda1 /mnt > mount: special device /dev/xvda1 does not exist > > # xm block-list Domain-0 > Vdev BE handle state evt-ch ring-ref BE-path > 51714 0 0 3 23 8 > /local/domain/0/backend/tap/0/51714 > > # xm block-detach Domain-0 /dev/xvda1 > > # xm block-list Domain-0 > Vdev BE handle state evt-ch ring-ref BE-path > 51714 0 0 3 23 8 > /local/domain/0/backend/tap/0/51714 > > qcow images created with qcow-create are working without any problems. > > And a few additional questions i have: > > - Is qcow encryption supported? > - is qcow compression supported? > > Greetings, > -timo >