Bug 46669 - u-boot-qemu не может загрузить regular-jeos-systemd-aarch64.img в QEMU
Summary: u-boot-qemu не может загрузить regular-jeos-systemd-aarch64.img в QEMU
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: u-boot-qemu (show other bugs)
Version: unstable
Hardware: aarch64 Linux
: P5 normal
Assignee: Sergey Bolshakov
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-27 16:00 MSK by Иван Зелинский
Modified: 2023-06-27 18:08 MSK (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Иван Зелинский 2023-06-27 16:00:04 MSK
ОС запускается с использованием бинарника из u-boot-qemu-2022.07-alt1.aarch64.rpm.

ОС не запускается с использованием бинарника из u-boot-qemu-2023.04-alt1.aarch64.rpm!


Образ ОС:
http://nightly.altlinux.org/sisyphus-aarch64/snapshots/20230621/regular-jeos-systemd-20230621-aarch64.img.xz
$ gost12sum regular-jeos-systemd-20230621-aarch64.img.xz
abb4a8cc5568320e462498c6d1ca957f29047853a1c38b2b0bdfc01393eb0c6d regular-jeos-systemd-20230621-aarch64.img.xz

Запускается при помощи скрипта (https://www.altlinux.org/Regular/arm#%D0%97%D0%B0%D0%BF%D1%83%D1%81%D0%BA_%D0%B2_QEMU):
#!/bin/sh
UBOOT_BIN=qemu_arm64/u-boot.bin
IMAGE=system.img
exec qemu-system-aarch64 \
	-machine virt -cpu cortex-a57 -m 2048 -smp 4 \
	-bios $UBOOT_BIN \
	-drive if=none,id=sda,format=raw,file=$IMAGE  \
	-device virtio-blk-device,drive=sda \
	-device virtio-keyboard -device virtio-tablet \
	-net nic -net user,hostfwd=tcp::2297-:22 \
	-device virtio-gpu-gl,xres=1366,yres=768 -nographic -display sdl,gl=on

Лог из терминала:
$ ./qemu_aarch64.sh 


U-Boot 2023.04 (Apr 04 2023 - 10:41:12 +0000)

DRAM:  2 GiB
Core:  51 devices, 14 uclasses, devicetree: board
Flash: 64 MiB
Loading Environment from Flash... *** Warning - bad CRC, using default environment

In:    pl011@9000000
Out:   pl011@9000000
Err:   pl011@9000000
Net:   eth0: virtio-net#32
Hit any key to stop autoboot:  0 
Scanning for bootflows in all bootdevs
Seq  Method       State   Uclass    Part  Name                      Filename
---  -----------  ------  --------  ----  ------------------------  ----------------
Scanning global bootmeth 'efi_mgr':
Scanning bootdev 'fw-cfg@9020000.bootdev':
fatal: no kernel available
No working controllers found
scanning bus for devices...
Unknown seq -1 for label 'scsi'
Scanning bootdev 'virtio-blk#31.bootdev':
  0  distro       ready   virtio       2  virtio-blk#31.bootdev.par /boot/extlinux/extlinux.conf
** Booting bootflow 'virtio-blk#31.bootdev.part_2' with distro
ALTLinux Boot Options
1:	linux
2:	6.1.34-std-def-alt1
3:	6.3.8-un-def-alt1
Enter choice: 1:	linux
Retrieving file: ../vmlinuz
Skipping linux for failure retrieving kernel
2:	6.1.34-std-def-alt1
Retrieving file: ../vmlinuz-6.1.34-std-def-alt1
Skipping 6.1.34-std-def-alt1 for failure retrieving kernel
3:	6.3.8-un-def-alt1
Retrieving file: ../vmlinuz-6.3.8-un-def-alt1
Skipping 6.3.8-un-def-alt1 for failure retrieving kernel
Boot failed (err=-14)
Unknown seq -1 for label 'nvme'
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (1 ms)
Scanning bootdev 'virtio-net#32.bootdev':
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (0 ms)
*** Warning: no boot file name; using '0A00020F.img'
Using virtio-net#32 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename '0A00020F.img'.
Load address: 0x40400000
Loading: *
TFTP error: 'Access violation' (2)
Not retrying...
No more bootdevs
---  -----------  ------  --------  ----  ------------------------  ----------------
(1 bootflow, 1 valid)
=>
Comment 1 Repository Robot 2023-06-27 18:08:33 MSK
u-boot-qemu-2023.04-alt2 -> sisyphus:

 Tue Jun 27 2023 Sergey Bolshakov <sbolshakov@altlinux.ru> 2023.04-alt2
 - fix relative path boot (closes: 46669)