following are the steps reproduce. Note: An issue related to not able to download after giving bitbake command due to proxy issue is already existing. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12804 1) Download the build appliance image from following link https://autobuilder.yocto.io/pub/releases/yocto-2.5.1.rc1/build-appliance/Yocto_Build_Appliance.zip 2) Extract the Yocto_Build_Appliance.zip 3) After extract .zip file Yocto_Build_Appliance.vmdk and Yocto_Build_Appliance.vmx 4) open this file in VMware( Yocto_Build_Appliance.vmx) or VirtualBox( Yocto_Build_Appliance.vmdk ) 5) after the booting image following commands need to be executed sudo ip link set eth0 down sudo ip link set eth0 up 5) after booting image in virtual environment run the following command bitbake core-image-minimal Expected Result: Build should be start and completed. Actual result: Build not stated ( stuck in parsing ).
so does this mean we need the fix in 12804 too? I just backported it
Is there something accessing the network during parsing? If so that may be a bug as it shouldn't be touching the network with the default config...
this issue still coming in Yocto 2.6 M3 rc1.
Anuj has tracked this down and has a patch out for it, its memory constraints recently added to the qemux86 image slowing the parser to a crawl.
Fixed in master with: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c08ea14816acb3056815bd3f5b0670c998b0435f May need sumo backport so leave with Armin?
pull into stable/sumo-nmut
Fixed in sumo: http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=sumo&id=5315ebeded2af486cf95c83ec988287202a3ae2a
fix merged