Hi Lingxiang, I think the problem is "No filesystem could mount root". This could be caused by a couple of things that I can think of.
1. There is something wrong with your disk image. Have you tried booting with it in qemu? 2. You don't have the filesystem driver compiled into the kernel. Since gem5 takes a kernel binary, you have to compile all of the drivers you need to boot into the kernel (not modules). I would try to get things working in qemu then move over to gem5. This blogpost may help some: http://www.lowepower.com/jason/setting-up-gem5-full-system.html Cheers, Jason On Thu, Apr 20, 2017 at 12:52 AM Lingxiang Wang <[email protected]> wrote: > Dear all, > > I need to build a custom kernel based on litmus^rt and custom disk > image because of the research requirement. The kernel version is Linux > 4.9.13, and it is downloaded from litmus^rt. And the disk image is built by > my own. I used ubuntu-base 17.04 files to create it. And I have to use the > latest kernel version. But when I try to boot the image, I went to this: > > [ 0.711362] List of all partitions: > [ 0.711369] No filesystem could mount root, tried: [ 0.711376] > [ 0.711385] Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > [ 0.711398] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.13+ #1 > [ 0.711407] Hardware name: , BIOS 06/08/2008 > [ 0.711415] 0000000000000000 ffffffff8134a922 ffff88001dcb3000 > ffffc900000cbea0 > [ 0.711434] ffffffff81180afd 0000000000000010 ffffc900000cbeb0 > ffffc900000cbe48 > [ 0.711452] 00000000b0d51c2b ffffc900000cbe58 ffffc900000cbeb8 > 0000000000000012 > [ 0.711469] Call Trace: > [ 0.711480] [<ffffffff8134a922>] ? dump_stack+0x5c/0x7a > [ 0.711492] [<ffffffff81180afd>] ? panic+0xe4/0x22d > [ 0.711506] [<ffffffff81d7b4f1>] ? mount_block_root+0x281/0x2bd > [ 0.711520] [<ffffffff81d7a87b>] ? set_debug_rodata+0xc/0xc > [ 0.711533] [<ffffffff81d7b6ba>] ? prepare_namespace+0x12b/0x161 > [ 0.711546] [<ffffffff81d7b15c>] ? kernel_init_freeable+0x1db/0x1eb > [ 0.711560] [<ffffffff8160b100>] ? rest_init+0x90/0x90 > [ 0.711572] [<ffffffff8160b10a>] ? kernel_init+0xa/0x100 > [ 0.711585] [<ffffffff81619035>] ? ret_from_fork+0x25/0x30 > [ 0.711598] Kernel Offset: disabled > [ 0.711608] ---[ end Kernel panic - not syncing: VFS: Unable to mount > root fs on unknown-block(0,0) > > This is the command I used to boot the system: > build/X86/gem5.opt configs/example/fs.py\ > --kernel=litmus-rt/vmlinux \ > --disk-image=litmusrt.img > > Thanks! > > -- > Lingxiang Wang > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
