Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: qemu + initramfs
Date: Mon, 24 Aug 2015 14:05:12 +0200	[thread overview]
Message-ID: <1440417912.3543.20.camel@intel.com> (raw)
In-Reply-To: <1440417012.3543.16.camel@intel.com>

On Mon, 2015-08-24 at 13:50 +0200, Patrick Ohly wrote:
> Hello!
> 
> I just tried to boot a custom image under qemu with
> core-image-minimal-initramfs included in the kernel. For that, I added
> to my local.conf:
>         
>         INITRAMFS_IMAGE = "core-image-minimal-initramfs"
>         INITRAMFS_IMAGE_BUNDLE = "1"
> 
> The extended kernel now gets built fine with the normal "bitbake
> <image>".

Speaking of qemu and core-image-minimal-initramfs, that initramfs isn't
really suitable as it stands. It uses init-live-boot, which expects to
boot from removable media instead of the fixed disk provided by qemu.

Is there anything more suitable or do I have to roll my own init script
entirely, perhaps based on initramfs-framework?

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2015-08-24 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 11:50 qemu + initramfs Patrick Ohly
2015-08-24 12:05 ` Patrick Ohly [this message]
2015-08-24 15:36   ` Christopher Larson
2015-08-25 12:27 ` Patrick Ohly

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=1440417912.3543.20.camel@intel.com \
    --to=patrick.ohly@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