qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

QEMU boot kernel for ppc e300c3 problem


From: Ali Vatankhah
Subject: QEMU boot kernel for ppc e300c3 problem
Date: Sat, 4 Sep 2021 15:29:59 +0430

I am new to QEMU. I built a Linux kernel 4.14 and rootfs for MPC8308 (this CPU has e300c3 ppc core with Yocto (thud version) and it works on real hardware well.
When I run this command to run kernel with QEMU:

qemu-system-ppc -kernel vmlinux.bin -nographic

it prints this output and hangs up with 100% CPU usage on one CPU core:

>> =============================================================
>> OpenBIOS 1.1 [Mar 16 2021 08:16]
>> Configuration device id QEMU version 1 machine id 2
>> CPUs: 1
>> Memory: 128M
>> UUID: 00000000-0000-0000-0000-000000000000
>> CPU type PowerPC,750
milliseconds isn't unique.
Welcome to OpenBIOS v1.1 built on Mar 16 2021 08:16
>> [ppc] Kernel already loaded (0x01000000 + 0x00509db4) (initrd 0x00000000 + 0x00000000)
>> [ppc] Kernel command line:
>> switching to new context:
OF stdout device is: /pci@80000000/mac-io@10/escc@13000/ch-a@13020
Preparing to boot Linux version 4.14.202-yocto-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 Sat Sep 4 09:23:51 UTC 2021
Detected machine type: 00000400
command line:
memory layout at init:
  memory_limit : 00000000 (16 MB aligned)
  alloc_bottom : 0150e000
  alloc_top    : 08000000
  alloc_top_hi : 08000000
  rmo_top      : 08000000
  ram_top      : 08000000
found display   : /pci@80000000/QEMU,VGA@1, opening... done
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0150f000 -> 0x0150f552
Device tree struct  0x01510000 -> 0x01517000
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x01000000 ...

I installed qemu, qemu-system, qemu-system-ppc and openbios-ppc packages on a host that is Ubuntu 18.04 VMware with x86_64. I also installed qemu 6.1.0 from source but nothing changed. Also I enabled Platform support ---> Support booting from Open firmware or yaboot kernel option. Attached is the defconfig file used for compiling the kernel.
Can anyone help me understand why this happens? or could you tell me if QEMU supports e300 core well or not? and if yes how can I test e300 with an example?

Thanks.

Attachment: .config
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]