* Not mounting rootfs
@ 2014-03-12 2:54 Flavio Ceolin
2014-03-12 12:25 ` Valdis.Kletnieks at vt.edu
0 siblings, 1 reply; 2+ messages in thread
From: Flavio Ceolin @ 2014-03-12 2:54 UTC (permalink / raw)
To: kernelnewbies
Hi folks,
I trying to boot a kernel with a rootfs generated with buildroot under
qemu but with any success, the output is:
[ 0.814014] Magic number: 6:562:333
[ 0.814522] tty tty54: hash matches
[ 0.815121] rtc_cmos 00:00: setting system clock to 2014-03-11 14:19:08 UTC (1394547548)
[ 0.820886] List of all partitions:
[ 0.821097] No filesystem could mount root, tried:
[ 0.821399] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 0.821877] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.0-rc5-ARCH-00265-gb01d4e6 #1
[ 0.822184] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 0.822550] ffffffffffffffff ffff880007107df8 ffffffff814f7bc4 ffffffff816e5af0
[ 0.822903] ffff880007107e70 ffffffff814f4749 ffffffff00000010 ffff880007107e80
[ 0.823216] ffff880007107e20 ffff880007107e28 ffff880007107e90 0000000000000012
[ 0.823421] Call Trace:
That is the way I'm invoking qemu:
qemu-system-x86_64 -boot c -m 128 -nographic -kernel ./path/to/bzImage
-hda ./buildroot-2013.05/output/images/rootfs.ext2 -append
"root=/dev/ram0 console=ttyS0 init=/sbin/init"
Any tip is extremely welcome :)
---
Flavio Ceolin
^ permalink raw reply [flat|nested] 2+ messages in thread
* Not mounting rootfs
2014-03-12 2:54 Not mounting rootfs Flavio Ceolin
@ 2014-03-12 12:25 ` Valdis.Kletnieks at vt.edu
0 siblings, 0 replies; 2+ messages in thread
From: Valdis.Kletnieks at vt.edu @ 2014-03-12 12:25 UTC (permalink / raw)
To: kernelnewbies
On Tue, 11 Mar 2014 23:54:25 -0300, Flavio Ceolin said:
> Any tip is extremely welcome :)
> [ 0.820886] List of all partitions:
tip 1: What would you expect to see here that isn't here? That's right,
an output of what partitions it found.
-hda ./buildroot-2013.05/output/images/rootfs.ext2
seems to have misfired.
Either that, or '-append "root=/dev/ram0' and ram0 doesn't point at
a root file system. You might want to decide whether ram0 or ext2 is
where you want taht root to be....
> [ 0.821097] No filesystem could mount root, tried:
> [ 0.821399] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140312/5c69b42f/attachment.bin
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-03-12 12:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-12 2:54 Not mounting rootfs Flavio Ceolin
2014-03-12 12:25 ` Valdis.Kletnieks at vt.edu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).