blob: 25d7c9852fae9119f35d5a0a2176ef2753877c36 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
boot: 0.806
i386: 0.770
mistranslation: 0.748
device: 0.746
kernel: 0.728
semantic: 0.662
graphic: 0.636
performance: 0.624
user-level: 0.511
architecture: 0.470
debug: 0.452
permissions: 0.425
register: 0.423
files: 0.417
network: 0.395
x86: 0.387
ppc: 0.387
peripherals: 0.379
assembly: 0.358
PID: 0.351
VMM: 0.292
vnc: 0.275
socket: 0.262
TCG: 0.259
virtual: 0.254
hypervisor: 0.251
risc-v: 0.245
arm: 0.221
KVM: 0.197
unable to boot squashfs through mtd device
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,
Triaging old bug tickets... QEMU 1.1 is pretty much outdated, can we close this bug nowadays? Can you still reproduce the issue with the latest version of QEMU?
[Expired for QEMU because there has been no activity for 60 days.]
|