blob: 86a0aa61735af50af110e72c2b255892df212b1d (
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
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
graphic: 0.450
architecture: 0.395
device: 0.368
debug: 0.305
performance: 0.281
semantic: 0.253
permissions: 0.253
risc-v: 0.249
boot: 0.240
hypervisor: 0.239
ppc: 0.230
mistranslation: 0.213
vnc: 0.212
register: 0.205
PID: 0.197
kernel: 0.190
socket: 0.171
arm: 0.147
VMM: 0.144
user-level: 0.138
TCG: 0.124
x86: 0.121
network: 0.120
assembly: 0.120
files: 0.092
i386: 0.078
virtual: 0.069
peripherals: 0.041
KVM: 0.040
Unable to start CirrOS 0.5.1 on QEMU 7.0 with -M virt and -cpu max
Description of problem:
Steps to reproduce:
1. Fetch CirrOS image: ```wget https://github.com/cirros-dev/cirros/releases/download/0.5.1/cirros-0.5.1-aarch64-disk.img```
2. Run QEMU:
```
qemu-system-aarch64 -drive file=cirros-0.5.1-aarch64-disk.img -M virt -m 2048 \
-bios /usr/share/qemu-efi-aarch64/QEMU_EFI.fd -cpu max -nographic
```
Additional information:
When image boots, GRUB window appears for a second and then kernel/initramfs are loaded and booted:
```
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
```
When everything is fine we can see kernel output:
```
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd070]
[ 0.000000] Linux version 5.3.0-26-generic (buildd@bos02-arm64-028) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #28~18.04.1-Ubuntu SMP Wed Dec 18 16:41:01 UTC 2019 (Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13)
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: EFI v2.70 by EDK II
```
But on QEMU 7.0 with ```-M virt -cpu max``` we never get kernel output.
#
|