Update: found an answer to question 1) I made before, updating for everyone 
here. 

I was extracting the tarballs with the graphical interface. But I noticed that 
the extensions between the old and new guest binaries were different, (.tar.xz 
and .tar.bz2). In fact, that was causing corruption to my kernel files (not the 
download). 

Extracting with
$ bzip2 -d aarch-system-201901106.tar.bz2
and
$ tar xvf aarch-system-201901106.tar
solved broken output with readelf. So future readers, don't be lazy as I am and 
use `--help` if you don't remember the flags to extract on the different tools 
instead of using the GUI. 

So I'm back with the 
http://dist.gem5.org/dist/current/arm/aarch-system-201901106.tar.bz2 version. 

Question 2 remains, though. Although with a slightly different preamble until 
reaching the error.

./build/ARM/gem5.opt configs/example/arm/starter_fs.py --kernel 
/home/pedro/Projects/gem5/fs_files/aarch-system-201901106/binaries/vmlinux.arm64
 --disk-image /home/pedro/Projects/gem5/fs_files/ubuntu-18.04-arm64-docker.img 
--root /dev/vda

causes
   [.....]
        [    0.205260] gem5_energy_ctrl_mc: gem5_mc_init: DVFS handler in 
energy controller is disabled,                         ARM gem5 multi-cluster 
cpufreq driver                         will not be registered
        [    0.205399] usbcore: registered new interface driver usbhid
        [    0.205401] usbhid: USB HID core driver
        [    0.205424] NET: Registered protocol family 17
        [    0.206020] List of all partitions:
        [    0.206023] fe00         1953125 vda 
        [    0.206023]  driver: virtio_blk
        [    0.206027]   fe01         1952997 vda1 93d4895b-01
        [    0.206028] 
        [    0.206031] No filesystem could mount root, tried: 
        [    0.206032]  ext3
        [    0.206034]  ext4
        [    0.206036]  ext2
        [    0.206037]  squashfs
        [    0.206039]  vfat
        [    0.206041]  fuseblk
        [    0.206042] 
        [    0.206046] Kernel panic - not syncing: VFS: Unable to mount root fs 
on unknown-block(254,0)
        [    0.206049] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0+ #1
        [    0.206051] Hardware name: V2P-CA15 (DT)
        [    0.206053] Call trace:
        [    0.206056]  dump_backtrace+0x0/0x1c0
        [    0.206058]  show_stack+0x14/0x20
        [    0.206061]  dump_stack+0x8c/0xac
        [    0.206063]  panic+0x130/0x288
        [    0.206066]  mount_block_root+0x22c/0x294
        [    0.206068]  mount_root+0x140/0x174
        [    0.206071]  prepare_namespace+0x138/0x180
        [    0.206074]  kernel_init_freeable+0x1c0/0x1e0
        [    0.206076]  kernel_init+0x10/0x108
        [    0.206079]  ret_from_fork+0x10/0x18
        [    0.206081] Kernel Offset: disabled
        [    0.206083] CPU features: 0x21c06492
        [    0.206085] Memory Limit: 2048 MB
        [    0.206088] ---[ end Kernel panic - not syncing: VFS: Unable to 
mount root fs on unknown-block(254,0) ]---

So I'm currently stuck at this 'mount' problem. I'll try to search that up here 
in the list, but again, any help is appreciated.
Thank you.
Pedro.
_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to