Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] I: Configure buildroot for xen
Date: Wed, 17 Apr 2013 11:02:36 +0200	[thread overview]
Message-ID: <20130417110236.054b83b0@skate> (raw)
In-Reply-To: <1366188139.51067.YahooMailClassic@web171906.mail.ir2.yahoo.com>

Dear Luisa Posani,

> BR_TARGET_ROOTFS_TAR
> BR_TARGET_ROOTFS_CPIO
> BR_TARGET_ROOTFS_INITRAMFS
> 
> 
> xen and I launched with the command
> 
> xen-create-image --fs=ext3 --initrd=rootfs.cpio --kernel = bzImage --install-method = tar --install-source = rootfs.tar -- hostname = test -- verbose --force

rootfs.cpio and rootfs.tar generated by Buildroot contain the same
thing: the root filesystem generated by Buildroot.

I believe the xen-create-image --initrd option is to pass an initrd
that is not the root filesystem, such as what is done typically in
Linux distributions, where the initrd contains a temporary root
filesystem used to load the appropriate kernel modules and device
firmwares to make the system operate, before switching to the real root
filesystem.

So just get rid of --initrd=rootfs.cpio, I think it should work. It
will directly mount the ext3 filesystem as your root filesystem and
that's it.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-04-17  9:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17  8:42 [Buildroot] I: Configure buildroot for xen Luisa Posani
2013-04-17  9:02 ` Thomas Petazzoni [this message]
2013-04-17  9:44   ` Luisa Posani
2013-04-17 12:27   ` Luisa Posani
2013-04-17 15:33   ` Luisa Posani
2013-04-17 15:36     ` Thomas Petazzoni

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=20130417110236.054b83b0@skate \
    --to=thomas.petazzoni@free-electrons.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