The init=/some/path linux kernel command line must match an executable present in the disk image. Have you passed the init= option?
BTW, your email shows on my spam, I think you haven't configured your email client to authenticate correctly, ensure that you can send emails across two test accounts you own. On Thu, May 10, 2018 at 6:13 AM, Li Zhao <xm...@yahoo.com> wrote: > Hi, All, > I followed Jason's website > (http://www.lowepower.com/jason/setting-up-gem5-full-system.html) and built > a kernel version 4.8.13 (disk image is from CentOS7) and was able to boot it > on Qemu. However when I tried to boot it from gem5, I got the error of "No > working init found". The following has more information. Does anyone have > any clue? > > Thanks a lot. > > ...... > > mce: Unable to init device /dev/mcelog (rc: -5) > > microcode: no support for this CPU vendor > > EXT4-fs (hda1): mounting ext3 file system using the ext4 subsystem > > random: fast init done > > EXT4-fs (hda1): mounted filesystem with ordered data mode. Opts: (null) > > VFS: Mounted root (ext3 filesystem) on device 3:1. > > devtmpfs: error mounting -2 > > Freeing unused kernel memory: 996K (ffffffff81892000 - ffffffff8198b000) > > Write protecting the kernel read-only data: 8192k > > Freeing unused kernel memory: 1852K (ffff880001431000 - ffff880001600000) > > Freeing unused kernel memory: 440K (ffff880001792000 - ffff880001800000) > > Kernel panic - not syncing: No working init found. Try passing init= option > to kernel. See Linux Documentation/init.txt for guidance. > > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.13 #1 > > Hardware name: , BIOS 06/08/2008 > > 0000000000000001 ffffffff811e2d0e 00000000000000ac ffff88001fc14c00 > > ffffffff810ad6bf 0000ffff00000008 ffff88001ec57f50 ffff88001ec57ef0 > > ffff88001fc14c80 ffff88001e4e3000 ffff880000000000 ffff88001f7bcc00 > > Call Trace: > > [<ffffffff811e2d0e>] ? dump_stack+0x5e/0x7a > > [<ffffffff810ad6bf>] ? panic+0xd6/0x212 > > [<ffffffff81424b0d>] ? kernel_init+0xeb/0xee > > [<ffffffff814295ff>] ? ret_from_fork+0x1f/0x40 > > [<ffffffff81424a22>] ? rest_init+0x69/0x69 > > Kernel Offset: disabled > > ---[ end Kernel panic - not syncing: No working init found. Try passing > init= option to kernel. See Linux Documentation/init.txt for guidance. > > > > > > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
