From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [Build App RFC 4/5] vmdk: Update for direstdisk
Date: Mon, 26 Mar 2012 11:31:04 -0700 [thread overview]
Message-ID: <4F70B5E8.10101@linux.intel.com> (raw)
In-Reply-To: <6a68cf7d22e94be417215b12cac4cf1c5b9baefa.1332744104.git.sgw@linux.intel.com>
The conversion to directdisk is necessary due to the limitation in the
mkdosfs version we carry and larger filesystems. Please note in the
commit message so readers can know WHY the change was made.
On 03/25/2012 11:47 PM, Saul Wold wrote:
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/classes/image-vmdk.bbclass | 15 ++++++++++++---
> 1 files changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/meta/classes/image-vmdk.bbclass b/meta/classes/image-vmdk.bbclass
> index 9d596cd..736d1d7 100644
> --- a/meta/classes/image-vmdk.bbclass
> +++ b/meta/classes/image-vmdk.bbclass
> @@ -1,15 +1,23 @@
>
> NOISO = "1"
> +
> +SYSLINUX_ROOT = "root=/dev/hda2 "
> SYSLINUX_PROMPT = "0"
> SYSLINUX_TIMEOUT = "1"
> SYSLINUX_LABELS = "boot"
> +LABELS_append = " ${SYSLINUX_LABELS} "
> +
> +# need to define the dependency and the ROOTFS for directdisk
> +do_bootdirectdisk[depends] += "${IMAGE_BASENAME}:do_rootfs"
> +ROOTFS ?= "${DEPLOY_DIR_IMAGE}/${IMAGE_BASENAME}-${MACHINE}.ext3"
>
> # creating VMDK relies on having a live hddimg so ensure we
> # inherit it here.
> -inherit image-live
> +#inherit image-live
A development artifact I presume? No need to leave the old image type
commented out. Should probably also remove the comment as with
directdisk that is no longer the case - right?
> +inherit boot-directdisk
>
> create_vmdk_image () {
> - qemu-img convert -O vmdk ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.hddimg ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.vmdk
> + qemu-img convert -O vmdk ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.hdddirect ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.vmdk
> ln -s ${IMAGE_NAME}.vmdk ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.vmdk
>
> }
> @@ -18,7 +26,8 @@ python do_vmdkimg() {
> bb.build.exec_func('create_vmdk_image', d)
> }
>
> -addtask vmdkimg after do_bootimg before do_build
> +#addtask vmdkimg after do_bootimg before do_build
Ditto.
> +addtask vmdkimg after do_bootdirectdisk before do_build
> do_vmdkimg[nostamp] = "1"
>
> do_vmdkimg[depends] += "qemu-native:do_populate_sysroot"
Thanks,
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-03-26 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 6:47 [Build App RFC 0/5] Review Request for Build Appliance Saul Wold
2012-03-26 6:47 ` [Build App RFC 1/5] self-hosted-image: pre-populate the builder user with poky source Saul Wold
2012-03-26 6:47 ` [Build App RFC 2/5] image-vmdk: Add symbolic link Saul Wold
2012-03-26 18:23 ` Darren Hart
2012-03-26 6:47 ` [Build App RFC 3/5] boot-directdisk: Fix Block Calcuation Saul Wold
2012-03-26 18:26 ` Darren Hart
2012-03-26 6:47 ` [Build App RFC 4/5] vmdk: Update for direstdisk Saul Wold
2012-03-26 18:31 ` Darren Hart [this message]
2012-03-26 6:47 ` [Build App RFC 5/5] builder: Enable auto starting of Hob 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=4F70B5E8.10101@linux.intel.com \
--to=dvhart@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox