[Openembedded-architecture] Wic support for vmdk/qcow2/vdi image types

[Patrick Ohly]

On Fri, 2017-02-17 at 17:13 +0530, Vignesh Raman wrote:
> Currently wic doesn't support vmdk/qcow2/vdi images.
> 
> I have taken vmdk as example below to explain how wic support can be added.
> 
> qemu-img convert is used to create vmdk image in image-vm.bbclass. To
> create vmdk image, 'vmdk' needs to be added to IMAGE_FSTYPES
> IMAGE_FSTYPES += "vmdk"
> 
> vmdk image is created by converting hdddirect image type with qemu-img
> convert in image-vm.bbclass
> qemu-img convert -O $type ${IMGDEPLOYDIR}/${IMAGE_LINK_NAME}.hdddirect
> ${IMGDEPLOYDIR}/${IMAGE_NAME}.$type
> 
> vmdk images is implemented as main FSTYPES. In order for wic to
> support vmdk images, current vmdk image generation could be
> reimplemented as conversion type.
> If we implement vmdk conversion, then we can use IMAGE_FSTYPES +=
> 'wic.vmdk' to produce vmdk image from hdddirect images.
> So hdddirect image is created using the kickstart file (wks) and then
> the image is converted to wic.vmdk using qemu-img convert.
> 
> This applies to qcow2 and vdi images as well and it could be
> reimplemented as conversion types.
> 
> Can we implement vmdk/qcow2/vdi conversion to add wic support or can
> this be done in any other way? Thanks for any pointers.

There's a bug open about that:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10204

I think it's perfectly doable and will simplify the code, but it'll
require some testing. The bug is currently assigned to me for "future"
work; if someone wants to work on it, feel free to take it from me.

Not sure about the timing, though. Cut-off date for 2.3 M3 is Feb. 27,
2017.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.