From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Re: 3.0.3rc3 qcow image created with qemu-img not usable? Date: Thu, 12 Oct 2006 08:59:21 -0500 Message-ID: <452E4A39.9080807@us.ibm.com> References: <452DFFE9.20606@gmx.de> <452E3CFB.5030702@us.ibm.com> <452E4054.1090306@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: <452E4054.1090306@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 Timo Benk wrote: > Anthony Liguori wrote: > >> You cannot attach block devices to Domain-0. Furthermore, you cannot >> attach non-raw file-based block devices to paravirtual domains. >> > I can and Xen can do so too :-) > Sorry, I forgot about blktap... blktap requires a certain cluster size for qcow images IIRC. That's probably why qemu-img doesn't work. Regards, Anthony Liguori > I just followed the description in [1]. > > And the point is as i have explained: it works with qcow-create created > images but not with qemu-img created images. > > I do not know if that is by design or a bug. > > IMHO the Xen qcow format is compatible with qemu so it should work. > > [1]http://xenbits.xensource.com/xen-3.0.3-testing.hg/tools/blktap/README > > Greetings, > -timo >