Your disk isn't getting set up by the kernel either at all, or at a device name different from what you're (through the config scripts) specifying in the kernel's command line. Either the disk is failing to get set up (check for messages earlier in the console output), or it's getting named something other than /dev/sda1. /dev/sda1 is pretty likely correct and so I suspect there's a different issue, but if that's it it's easy to fix.
On Thu, Sep 12, 2019 at 12:30 PM Iago . <iagosilvestr...@hotmail.com> wrote: > I am trying to verify computational load of an LQR code on my UAV project, > to do so I am using gem5 to simulate different platforms where the code can > run. > I've been trying to use the ARM Full-System Files, but running the gem5 > simulation through: > build/ARM/gem5.opt configs/example/fs.py > --disk-image=/home/labvant/fs/disks/aarch32-ubuntu-natty-headless.img > --kernel=/home/labvant/fs/binaries/vmlinux.vexpress_gem5_v1 > > But I've tried a couple different versions and it always results in warn: > Kernel panic in simulated kernel. Accessing the simulated system I find > that the error occurs here: > > [ 0.256914] VFS: Cannot open root device "sda1" or unknown-block(0,0): > error -6 > [ 0.256919] Please append a correct "root=" boot option; here are the > available partitions: > [ 0.257044] Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > > Any ideas on how I could solve this problem. > _______________________________________________ > 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
