[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] a problem with using qcow2 format image files as virtual disks


At 2012-02-15 22:46:09,"Philipp Hahn" <hahn@xxxxxxxxxxxxx> wrote:
>On Wednesday 15 February 2012 14:58:39 hxkhust wrote:
>> In most cases we use image files as virtual disks under the
>> full-virtualization situation.On the version 4.1.2 of xen,I do the
>> following command:
>> qemu-img-xen create -b myqcow1.img -f qcow2 myqcow2.img 20000M
>> >> (I also use "diks = ['tap:qcow2:/....../myqcow2.img,xvda,w']",but it failed
>> too)

>Last time I checked 
>blktap2 has no qcow2 support, only qcow1, vhd and some other formats.
>Philipp Hahn           Open Source Software Engineer      hahn@xxxxxxxxxxxxx
>Univention GmbH        Linux for Your Business        fon: +49 421 22 232- 0
>Mary-Somerville-Str.1  D-28359 Bremen                 fax: +49 421 22 232-99
>                                                   http://www.univention.de/
Under that directory there is no block-qcow2.c indeed.With "disk = ['tap2:tapdisk:qcow2:/....../myqcow1.img,xvda,w']" configured in the configure file myqcow1.hvm, however,myqcow1.img could be used to create a VM just using "xl create myqcow1.hvm".Only myqcow2.img could not be used to create a VM normally with the error "no bootable device found" happening.that is weird...
(I just would like to use multi-layer image files to create VMs.Either qcow format or qcow2 format is right.)

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.