All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: hddimg vs hdddirect?
Date: Thu, 17 Mar 2016 05:37:49 +0100	[thread overview]
Message-ID: <56EA349D.10107@mlbassoc.com> (raw)
In-Reply-To: <50f8e13e-bf3e-96b9-221b-3f6a92f948ee@noir.com>

On 03/16/2016 08:40 PM, K Richard Pixley wrote:
> What's the intended difference between hddimg and hdddirect?
>
> I'm confused about the intent here. The data flow in previous releases,
> even jethro, seems to be somewhat confused/broken so looking at the
> source code isn't really helping here.
>
> Is one intended to be a simple syslinux bootable image while the other
> is a "live" image with multiple boot choices?
>
> In master... How does one go about requesting either a vmdk of a live
> image or a directly bootable vmdk?

I'm not sure the difference between the .hddimg and .hdddirect.
I tried converting a .hddimg to .vdi or .vmdk using the VBoxManage
tool, but that didn't come up - there was a message about (paraphrased)
"waiting for removable media to become ready"  and the boot just hung up

However, I do know that .vmdk will boot easily with VirtualBox
Just add this to your local.conf
   IMAGE_FSTYPES += " vmdk"

Note: as mentioned in the documentation, you must use += as
IMAGE_FSTYPES_append will not do.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2016-03-17  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 19:40 hddimg vs hdddirect? K Richard Pixley
2016-03-17  4:37 ` Gary Thomas [this message]
2016-03-17 16:32   ` K Richard Pixley

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=56EA349D.10107@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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.