All of lore.kernel.org
 help / color / mirror / Atom feed
From: Launchpad Bug Tracker <1026176@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1026176] Re: unable to boot squashfs through mtd device
Date: Sun, 02 Apr 2017 04:17:24 -0000	[thread overview]
Message-ID: <20170402041724.11031.20470.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20120718144939.31209.59720.malonedeb@gac.canonical.com

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1026176

Title:
  unable to boot squashfs through mtd device

Status in QEMU:
  Expired

Bug description:
  Hi,

  I have built latest qemu archive qemu-1.1.1 to be sure of up to date source code.
  I have then built buildroot squashfs image, which can be used correctly with cmdline like:

  qemu-system-i386 -m 64 -k fr -boot c -kernel images/bzImage -drive
  if=ide,file=images/rootfs.squashfs  -append "root=/dev/sda"

  Then I wanted to modify cmdline to use real MTD device, like:

  qemu-system-i386 -m 64 -k fr -boot c -kernel images/bzImage -drive
  if=mtd,file=images/rootfs.squashfs  -append "root=/dev/mtdblock0".

  But nothing was good under kernel.
  Even if mtd0 is reported through qemu interface (Ctrl Alt+2), no device can be found under kernel even if all drivers are built to use it.

  Is this feature okay on qemu-1.1.1 ??
  did I do mistake in my cmdline??

  thank you for your help.
  regards,

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1026176/+subscriptions

      parent reply	other threads:[~2017-04-02  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 14:49 [Qemu-devel] [Bug 1026176] [NEW] unable to boot squashfs through mtd device Vincent de RIBOU
2017-01-31  9:12 ` [Qemu-devel] [Bug 1026176] " Thomas Huth
2017-04-02  4:17 ` Launchpad Bug Tracker [this message]

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=20170402041724.11031.20470.malone@loganberry.canonical.com \
    --to=1026176@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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.