Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bogdan Cristea <cristeab@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Creating a filesystem for QEMU
Date: Fri, 13 Nov 2009 16:46:42 +0200	[thread overview]
Message-ID: <200911131646.42695.cristeab@gmail.com> (raw)
In-Reply-To: <a038bef50911130559i31605c47k57d27e91d95b28f8@mail.gmail.com>

On Friday 13 November 2009 15:59:46 you wrote:
> On Fri, Nov 13, 2009 at 8:18 AM, Bogdan Cristea <cristeab@gmail.com> wrote:
> > On Thursday 12 November 2009 16:46:32 you wrote:
> >> I've just started doing the same thing myself.  After a bit of googling
> >> the trick I found was to ask buildroot to generate a cpio target file
> >> system. Start with the i386_defconfig or i686_defconfig and set
> >> BR2_TARGET_ROOTFS_CPIO=y (or use "make menuconfig" an find the cpio
> >> option under the "Target file system" menu)
> >>
> >> Making use of qemus ability to replace the bootloader you can invoke
> >> qemu with
> >>     qemu -kernel output/images/bzImage \
> >>          -initrd output/images/rootfs.i686.cpio
> >
> >     I have tried this approach, but it does not seem to work. First
> > inconvenient is that rootfs.i686.cpio file is very large (600 MB) and
> > when using the above command I only get a black screen from QEMU while
> > the entire computer seems to be slower.
> >    Lionel, suggested other approaches but till now I have no luck. Trying
> > to obtain first a cloop root filesystem and then convert that to a QEMU
> > format seem to work and the file size is small (3 MB), but still when
> > using that disk image, QEMU is not able to recognize any root partition.
> >    If you have any other suggestion it would be helpful.
> 
> I'd double check your configuration. I must admit I started hacking
> away without looking at the i686_defconfig. But I've got a rootfs
> thats only 3M and a kernel thats just under 4M. I've attached my
> buildroot config (.config) and kernel config (i386_defconfig) for your
> reference.
> 
> Also when you are hacking away re-configuring buildroot doesn't know
> to remove something up if you've de-selected it so you may need to
> manually clean out output/target/ manually (or start from fresh each
> time).
> 

when using your .config file my compilation fails due to a missing patch file
mpfr-2.4.1.patch. What is the role of that patch ?

  parent reply	other threads:[~2009-11-13 14:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 14:23 [Buildroot] Creating a filesystem for QEMU Bogdan Cristea
2009-11-12 14:58 ` Lionel Landwerlin
2009-11-12 15:03   ` Bogdan Cristea
2009-11-12 15:14     ` Lionel Landwerlin
2009-11-12 15:22     ` Mark Constable
2009-11-12 15:04 ` Chris Packham
     [not found] ` <4AFC1FC8.3020305@gmail.com>
2009-11-13 13:18   ` Bogdan Cristea
2009-11-13 13:56     ` Lionel Landwerlin
2009-11-13 13:57       ` Lionel Landwerlin
2009-11-13 14:03         ` Chris Packham
2009-11-13 14:10           ` Lionel Landwerlin
     [not found]     ` <a038bef50911130559i31605c47k57d27e91d95b28f8@mail.gmail.com>
2009-11-13 14:46       ` Bogdan Cristea [this message]
2009-11-13 15:14         ` Chris Packham
2009-11-13 17:45           ` Bogdan Cristea

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=200911131646.42695.cristeab@gmail.com \
    --to=cristeab@gmail.com \
    --cc=buildroot@busybox.net \
    /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