From: Saul Wold <sgw@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] Setup for VMDK to use Direct Disk
Date: Tue, 27 Mar 2012 11:16:10 -0700 [thread overview]
Message-ID: <4F7203EA.4030104@linux.intel.com> (raw)
In-Reply-To: <1443918.kuu0Jnlh65@helios>
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
bitbake.
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.
> Cheers,
> Paul
>
next prev parent reply other threads:[~2012-03-27 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 5:42 [PATCH 0/6] Setup for VMDK to use Direct Disk Saul Wold
2012-03-27 5:42 ` [PATCH 1/6] self-hosted-image: pre-populate the builder user with poky source Saul Wold
2012-03-28 15:35 ` Cui, Dexuan
2012-03-28 21:07 ` Saul Wold
2012-03-29 7:15 ` Cui, Dexuan
2012-03-28 20:45 ` Paul Eggleton
2012-03-28 21:08 ` Saul Wold
2012-03-27 5:42 ` [PATCH 2/6] image-vmdk: Add symbolic link for a short named vmdk image Saul Wold
2012-03-27 5:42 ` [PATCH 3/6] boot-directdisk: Fix Block Calcuation Saul Wold
2012-03-27 5:42 ` [PATCH 4/6] vmdk: Update for direstdisk Saul Wold
2012-03-27 5:42 ` [PATCH 5/6] builder: Enable auto starting of Hob Saul Wold
2012-03-27 5:43 ` [PATCH 6/6] image_types: remove duplicate setting of -i for inode count Saul Wold
2012-03-27 14:37 ` [PATCH 0/6] Setup for VMDK to use Direct Disk Paul Eggleton
2012-03-27 18:16 ` Saul Wold [this message]
2012-03-27 20:21 ` Paul Eggleton
2012-03-27 20:45 ` João Henrique Freitas
2012-03-28 15:21 ` Cui, Dexuan
2012-03-30 14:17 ` Paul Eggleton
2012-03-30 21:16 ` Cui, Dexuan
2012-03-31 5:11 ` Cui, Dexuan
2012-04-01 10:28 ` Cui, Dexuan
2012-04-01 19:43 ` Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F7203EA.4030104@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox