default wic creation plugin dont work with meta-acrn, not using IMAGE_BOOT_FILES

[pchand20]

seems meta-acrn have overwritten the default wic image creation plugin and it wont take any values from default OE variables set in yocto which are set for boot image creation. i.e IMAGE_BOOT_FILES variables is ignored or not used. while this variable is widely used in yocto OE core with default wic plugin. reference from here https://github.com/openembedded/openembedded-core/blob/master/scripts/lib/wic/plugins/source/bootimg-partition.py

could you make changes in acrn wic plugin so it follow and inherits the OE plugin variables.

[cheeyanglee]

EFI partition switched to IMAGE_EFI_BOOT_FILES, so it wont clash with IMAGE_BOOT_FILES when image build with both bootimg-partition and bootimg-efi.
openembedded/openembedded-core@945339e

[pchand20]

I think we are missing whole point here. what you have introduced is a new variable , but same time we ignored yocto provided environment for similar work. now if I have to adopt meta-acrn than I cannt use whatever is used in oe-core by using IMAGE_BOOT_FILES environment. if you want to add new plugin that fine but you shall also parse existing variable IMAGE_BOOT_FILES along side as default and a mechanism to exclude it. it similar saying that we change yocto defined TOPDIR to something else and now onward it wont work if you use our layer and distro. this will break exiting mechanism in yocto as soon as we add meta-acrn. we suppose not to do that. have you tried if installer type of mechanism will still work with this ? i.e crating a live boot image ?

[pchand20]

any update on this issue?

[saininav]

@pchand20 We were trying to fix ACRN wic installer issue in both gatesgarth and dunfell too. Could you please try wic installer by following https://github.com/intel/meta-acrn/blob/master-next/docs/getting-started.md#build-wic-installer-image