<div dir="ltr"><div class="gmail_extra">Thanks Juro,</div><div class="gmail_extra"><br><div class="gmail_quote">On 8 May 2015 at 23:39, Juro Bystricky <span dir="ltr"><<a href="mailto:juro.bystricky@intel.com" target="_blank">juro.bystricky@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2bx" class="a3s" style="overflow:hidden">Yocto does not support VirtualBox sparse image VDI file format.<br>
This could be achieved by the attached patch. The support mimics<br>
the VMDK support for VMware. The only subtle difference is that<br>
qemu-native has be be built with uuid enabled, as VDI images<br>
need a valid UUID in order to be recognized by VirtualBox.<br>
<br>
[YOCTO #7374]</div></blockquote></div><br>This needs to be split up into logical patches. For example one to enable UUID into Qemu, one to add the new image type, another to update the checks.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>