[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1026176] [NEW] unable to boot squashfs through mtd dev
From: |
Vincent de RIBOU |
Subject: |
[Qemu-devel] [Bug 1026176] [NEW] unable to boot squashfs through mtd device |
Date: |
Wed, 18 Jul 2012 14:49:38 -0000 |
Public bug reported:
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,
** Affects: qemu
Importance: Undecided
Status: New
** Tags: 1.1.1
--
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:
New
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
- [Qemu-devel] [RFC v9 00/27] virtio: virtio-blk data plane, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 01/27] virtio-blk: Remove virtqueue request handling code, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 03/27] virtio-blk: Data plane thread event loop, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 02/27] virtio-blk: Set up host notifier for data plane, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 04/27] virtio-blk: Map vring, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 15/27] notifier: Add a function to set the notifier, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 05/27] virtio-blk: Do cheapest possible memory mapping, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 07/27] virtio-blk: Put dataplane code into its own directory, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 09/27] virtio-blk: Add Linux AIO queue, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 10/27] virtio-blk: Stop data plane thread cleanly, Stefan Hajnoczi, 2012/07/18
- [Qemu-devel] [RFC v9 23/27] virtio-blk: Stub out SCSI commands, Stefan Hajnoczi, 2012/07/18