RE: linux doesn't boot with secure=on option (arm64 virt)

[Chan Kim]

 

Hi, Could anyone explain to me what ‘secure=on’ option means?

Doesn’t it mean the virtual hardware machine has security features implemented? (that’s what I understand)

And if we have the security feature implemented in the real machine, should I be running qemu always with seure=on?

Thanks!

Chan Kim

 

From: Chan Kim <ckim@etri.re.kr>
Sent: Saturday, February 19, 2022 10:20 AM
To: 'qemu-discuss' <qemu-discuss@nongnu.org>
Subject: linux doesn't boot with secure=on option (arm64 virt)

 

Hello all

 

When I use this command(secure=off),

../qemu-6.2.0/build-baremetal/aarch64-softmmu/qemu-system-aarch64 -machine virt,gic-version=max,secure=off,virtualization=true -cpu max -kernel ../../LinuxDevDrv/linux-5.4.21/arch/arm64/boot/Image -m 2048M -nographic

the linux kernel boots ok to the shell prompt.

 

But if I change it to this (secure=on),

../qemu-6.2.0/build-baremetal/aarch64-softmmu/qemu-system-aarch64 -machine virt,gic-version=max,secure=on,virtualization=true -cpu max -kernel ../../LinuxDevDrv/linux-5.4.21/arch/arm64/boot/Image -m 2048M -nographic

Linux doesn’t boot and get’s stuck in somewere in setup_arch inside start_kerne.

Below is the back trace of linux.

#0  __init_single_page (pfn=<optimized out>, nid=<optimized out>, zone=<optimized out>, page=<optimized out>)

    at mm/page_alloc.c:1343

#1  memmap_init_zone (size=<optimized out>, nid=<optimized out>, zone=<optimized out>, start_pfn=730027, context=MEMMAP_EARLY,

    altmap=0xffffff80bd4f7248) at mm/page_alloc.c:5913

#2  0xffffffc010488ba8 in memmap_init (size=<optimized out>, nid=<optimized out>, zone=<optimized out>,

    start_pfn=<optimized out>) at mm/page_alloc.c:6022

#3  0xffffffc010475594 in free_area_init_core (pgdat=<optimized out>) at mm/page_alloc.c:6807

#4  free_area_init_node (nid=<optimized out>, zones_size=<optimized out>, node_start_pfn=<optimized out>,

    zholes_size=<optimized out>) at mm/page_alloc.c:6900

#5  0xffffffc010465c5c in zone_sizes_init (min=<optimized out>, max=<optimized out>) at arch/arm64/mm/init.c:236

#6  0xffffffc010465a48 in bootmem_init () at arch/arm64/mm/init.c:458

#7  0xffffffc010463ee8 in setup_arch (cmdline_p=0xffffffc0105d3fa8) at arch/arm64/kernel/setup.c:337

#8  0xffffffc010460488 in start_kernel () at init/main.c:614

#9  0x0000000000000000 in ?? ()

Is this normal, or do I have any problem with the command or in my Image file?

Thank you,

 

Chan Kim