From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [CONSOLIDATED PULL 02/17] runqemu-internal: qemu fails to run on ext2 image
Date: Fri, 22 Jun 2012 15:00:43 -0700 [thread overview]
Message-ID: <9020c3a1a7cbaffe24b5f3d0e08ef7becfff7b7b.1340402353.git.sgw@linux.intel.com> (raw)
In-Reply-To: <cover.1340402353.git.sgw@linux.intel.com>
In-Reply-To: <cover.1340402353.git.sgw@linux.intel.com>
From: Kang Kai <kai.kang@windriver.com>
[Yocto 2579]
When set DISTRO to poky-tiny, only ext2 image is created. But
runqemu-internal doesn't set QEMUOPTIONS for ext2 image that make qemu
fail to boot.
Fix it for qemux86 arch since poky-tiny can only build for qemux86 now.
Signed-off-by: Kang Kai <kai.kang@windriver.com>
---
scripts/runqemu-internal | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
index c8e3186..041464d 100755
--- a/scripts/runqemu-internal
+++ b/scripts/runqemu-internal
@@ -319,7 +319,7 @@ fi
if [ "$MACHINE" = "qemux86" ]; then
QEMU=qemu
QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -vga vmware -enable-gl"
- if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then
+ if [ "$FSTYPE" = "ext2" -o "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then
KERNCMDLINE="vga=0 root=/dev/hda rw mem=$QEMU_MEMORY $KERNEL_NETWORK_CMD"
QEMUOPTIONS="$QEMU_NETWORK_CMD -hda $ROOTFS $QEMU_UI_OPTIONS"
fi
--
1.7.7.6
next prev parent reply other threads:[~2012-06-22 22:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 22:00 [CONSOLIDATED PULL 00/17] Misc Fixes & Updates Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 01/17] cml1.bbclass: Only delay exit if the command fails Saul Wold
2012-06-22 22:00 ` Saul Wold [this message]
2012-06-22 22:00 ` [CONSOLIDATED PULL 03/17] mtd-utils: do not stage headers in sysroot Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 04/17] gpgme: updated to 1.3.2 Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 05/17] gcc-4.6: Retire into toochain-layer Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 06/17] eglibc-2.13: Retire into toolchain layer Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 07/17] gcc: Remove csl gcc recipes Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 08/17] gzip: upgrade to 1.5 Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 09/17] sudo: upgrade to 1.8.5p2 Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 10/17] bitbake.conf/abi_version.conf: Update to use BasicHash signature generator Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 11/17] linux-firmware: update to main repo on kernel.org Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 12/17] kconfig-frontends: New recipe Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 13/17] uclibc: Fix packaging to match the new package order Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 14/17] qemu.inc: Fix packageconfig options Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 15/17] qemu-git: Move to tip of git Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 16/17] qemu_git: set empty PACKAGECONFIG Saul Wold
2012-06-22 22:00 ` [CONSOLIDATED PULL 17/17] distrodata: Fix missed VARIABLE name change Saul Wold
2012-06-24 18:18 ` [CONSOLIDATED PULL 00/17] Misc Fixes & Updates Saul Wold
2012-06-25 15:55 ` Richard Purdie
2012-06-25 21:14 ` Khem Raj
2012-06-29 12:26 ` Richard Purdie
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=9020c3a1a7cbaffe24b5f3d0e08ef7becfff7b7b.1340402353.git.sgw@linux.intel.com \
--to=sgw@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