blob: 37e9aadd077a8ef95f8a6a3b416c767d46c2882c (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
guest userspace process core dump after raspi2 kernel boot
Host info:
==========
x86-64, Ubuntu 18.04, QEMU 4.0.0 (downloaded tarball from main site)
Guest info:
===========
ARM7l, Raspbian OS off the main raspberry pi site
QEMU command:
=============
qemu-system-arm -M raspi2 -kernel bootpart/kernel7.img -dtb bootpart/bcm2709-rpi-2-b.dtb -drive file=2019-07-10-raspbian-buster.img,format=raw,if=sd -append "rw earlyprintk console=ttyAMA0,115200 fsck.repair=yes rootwait memtest=1 loglevel=8 dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2" -serial stdio
kernel7.img and bcm2709-rpi-2-b.dtb were obtained by the following commands:
guestfish --ro -a 2019-07-10-raspbian-buster.img -m /dev/sda1
><fs> copy-out / bootpart/
><fs> quit
Output:
=======
https://pastebin.com/fL1eXhV0
References:
===========
https://translatedcode.wordpress.com/2016/11/03/installing-debian-on-qemus-32-bit-arm-virt-board/
https://translatedcode.wordpress.com/2018/04/25/debian-on-qemus-raspberry-pi-3-model/
The core dump error can occur at both times, before logging in and after logging in, in this case I have given the output after logging in to show the initial processes running.
Also please let me know if I using any kernel flags incorrectly
|