[OE-core] [PATCH 0/6] Setup for VMDK to use Direct Disk
sgw at linux.intel.com
Tue Mar 27 20:16:10 CEST 2012
On 03/27/2012 07:37 AM, Paul Eggleton wrote:
> On Monday 26 March 2012 22:42:54 Saul Wold wrote:
>> Updated comments per Darren's request, added cleanup to
>> image-types to only use one -i (inode-count) parameter.
> I tried this series on my build machine, but do_rootfs failed with "genext2fs:
> not enough memory for filesystem".
Yes, there is an issue with genext2fs needing memory to build the
filesystem first. I noted in another email thread that the Debian build
system had so resort to dd, mkfs.ext3, mounting and copying. The issue
with that is that it requires root privileges which is forbidden with
genext2fs combines the making and copying of the fs into one process, if
there is a way to populate the filesystem image with the bits without
root privs that's what we need to look towards.
This is turning into a non-trivial problem.
I am beginning to think that we might have to have 2 vmdk images for the
build appliance to work correctly. 1 for the rootfs and the second for
the build space (10G-20G) with DL_DIR populated.
> The machine has 6GB RAM and 8GB swap. The rootfs directory is 15GB.
> I guess this might have something to do with my DL_DIR not being clean
> beforehand (since it seems to be copying it into the rootfs in its entirety).
I have created a clean DL_DIR to work with by doing a world fetch and
then using that DL_DIR to build into the image.
More information about the Openembedded-core