RE: [Xen-devel] Re: How to use qcow image with ioemu-remote?

["Li, Haicheng" <haicheng.li@xxxxxxxxx>]

Ian,

Thanks for your reply. it should be a bug.

This image is qcow image not qcow2 image: 
`file ia32e_rhel5u1.qcow` shows: ia32e_rhel5u1.qcow: QEMU Copy-On-Write
disk image version 1, size 1 + 1073741824

With "disk = [ 'tap:qcow2:/vm-img/ia32e_rhel5u1.qcow,hda,w' ]", also
failed to create guest with qemu log:
Strip off blktap sub-type prefix to /vm-img/ia32e_rhel5u1.qcow (drv
'qcow2')
qemu: type (image format) 'qcow2' unknown for vbd
'/local/domain/13/device/vbd/768/phantom_vbd' or image
'/vm-img/ia32e_rhel5u1.qcow'

So I filed a bug to track this issue:
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1304.
 


Ian Jackson wrote:
> Li, Haicheng writes ("How to use qcow image with ioemu-remote?"):
>> Seems syntax like `disk = [
>> 'tap:qcow:/vm-img/ia32e_rhel5u1.qcow,hda,w' ] doesn't work. What's
>> the syntax to use qcow with ioemu-remote? 
> 
> Hrm.  That's probably actually a qcow2 image so you might try
> `tap:qcow2:...'.
> If that works then all is good - although it produces a config file
> difference between ioemu and ioemu-remote, that config file difference
> is only in a field that was introduced in this release cycle anyway.
> 
> If that doesn't work then there's a bug.  Please let me know - if
> it is in fact a bug I'll try to reproduce it.
> 
> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



-- haicheng

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