All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] image_types: ensure .rootfs.ext3 is created before vmdk is created.
Date: Thu, 08 Mar 2012 23:30:14 -0800	[thread overview]
Message-ID: <4F59B186.6090009@linux.intel.com> (raw)
In-Reply-To: <6d24f6bd75d4c9da78368d3cae9dbbc8a470b2b6.1331277565.git.dexuan.cui@intel.com>

On 03/08/2012 11:19 PM, Dexuan Cui wrote:
> In the case of self-hosted-image.bb, IMAGE_FSTYPES = "vmdk", so the
> variables alltypes and subimages don't contain ext3, and  .rootfs.ext3
> won't be created, and finally the generated .hddimg and .vmdk don't have
> an actual rootfs -- the size of the .vmdk file is only about 9MB.
>
> [YOCTO #2067]
>
> Signed-off-by: Dexuan Cui<dexuan.cui@intel.com>

Nice Catch!

Acked-by: Saul Wold <sgw@linux.intel.com>

Sau!
> ---
>   meta/classes/image_types.bbclass |    6 ++++++
>   1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
> index 8b82018..e92f519 100644
> --- a/meta/classes/image_types.bbclass
> +++ b/meta/classes/image_types.bbclass
> @@ -26,13 +26,19 @@ def get_imagecmds(d):
>       # Live and VMDK images will be processed via inheriting
>       # bbclass and does not get processed here.
>       # vmdk depend on live images also depend on ext3 so ensure its present
> +    # Note: we need to ensure ext3 is in alltypes, otherwise, subimages may
> +    # not contain ext3 and the .rootfs.ext3 file won't be created.
>       if "vmdk" in types:
>           if "ext3" not in types:
>               types.append("ext3")
> +        if "ext3" not in alltypes:
> +            alltypes.append("ext3")
>           types.remove("vmdk")
>       if "live" in types:
>           if "ext3" not in types:
>               types.append("ext3")
> +        if "ext3" not in alltypes:
> +            alltypes.append("ext3")
>           types.remove("live")
>
>       if d.getVar('IMAGE_LINK_NAME', True):



  reply	other threads:[~2012-03-09  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  7:19 [PATCH 0/1] a fix to 2067 Dexuan Cui
2012-03-09  7:19 ` [PATCH 1/1] image_types: ensure .rootfs.ext3 is created before vmdk is created Dexuan Cui
2012-03-09  7:30   ` Saul Wold [this message]
2012-03-09  7:40     ` Cui, Dexuan
2012-03-13 16:26 ` [PATCH 0/1] a fix to 2067 Saul Wold

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=4F59B186.6090009@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.