OK, no problem.
Saul also suggested merging image-vmdk and image-vdi classes into one class,
something like image-vm.bbclass. It is a bit more invasive (will modify the
existing vmdk
bbclass) , but it should be a cleaner implementation overall.
Juro
From: Burton, Ross [mailto:ross.bur...@intel.c
On 05/08/2015 03:39 PM, Juro Bystricky wrote:
Yocto does not support VirtualBox sparse image VDI file format.
This could be achieved by the attached patch. The support mimics
the VMDK support for VMware. The only subtle difference is that
qemu-native has be be built with uuid enabled, as VDI imag
Thanks Juro,
On 8 May 2015 at 23:39, Juro Bystricky wrote:
> Yocto does not support VirtualBox sparse image VDI file format.
> This could be achieved by the attached patch. The support mimics
> the VMDK support for VMware. The only subtle difference is that
> qemu-native has be be built with uui
