Home 零对冲(ZeroHedge)每日HackerNews

Go-boot：基于Go的UEFI裸机启动管理器
Go-boot: bare metal Go UEFI boot manager

原始链接: https://github.com/usbarmory/go-boot

## go-boot: 一个TamaGo UEFI 唯一内核 go-boot 是一个适用于AMD64平台的TamaGo唯一内核，提供UEFI Shell和操作系统加载器。它允许直接与UEFI API交互，并支持启动各种操作系统，包括EFI应用程序、Linux内核（通过UAPI引导加载条目配置）以及通过其UEFI引导管理器启动Windows。未来的开发计划包括引导透明度支持。 该系统提供一个命令行界面，包含文件管理、系统信息、网络（可选SNP/go-net支持）和内存访问等实用工具。它可以通过环境变量进行配置，例如`IMAGE_BASE`、`DEFAULT_LINUX_ENTRY`和`CONSOLE`。 go-boot可以使用TamaGo编译器构建，并通过UEFI Shell、systemd-boot等引导管理器或`efibootmgr`部署。它也可以在QEMU中进行测试，并通过GDB提供调试选项。该项目提供硬件兼容性列表（HCL），其中包含各种平台的推荐`IMAGE_BASE`值。

## Go-boot：基于Go的UEFI引导管理器 一个名为“Go-boot”的新项目（github.com/usbarmory）在Hacker News上引起关注，它创建了一个基于Go语言的裸机UEFI引导管理器。本质上，它展示了Go编程语言在低级系统编程中的可行性——传统上由C和Rust主导的领域。 该项目的创建者以USB Armory和TamaGo项目而闻名，他们构建Go-boot部分是为了*证明* Go可以处理此类任务，从而反驳了人们对其在裸机编程中适用性的怀疑。除了证明这一点之外，它还旨在提供一个比标准、通常笨拙的UEFI shell更易于使用的替代方案。 该项目突出了Go在可靠性和安全性至关重要的场景中的潜力，为系统级开发提供了一种不同的方法。
相关文章
原文

The go-boot project is a TamaGo unikernel implementing a UEFI Shell and OS loader for AMD64 platforms, allowing UEFI API interaction and OS loading.

The OS loading functionality supports launching of:

  • . EFI application images
  • l Linux kernels, with configuration parsed from Linux Userspace API (UAPI) boot loader entries
  • w Windows UEFI boot manager

The support of boot-transparency is planned for future releases.

Andrea Barisani [email protected]

The default operation is to present an UEFI shell and its help, the ⏎ shortcut (identically to l or linux) boots the default UAPI entry set at compile time (see Compiling).

Shell> go-boot.efi

initializing EFI services
initializing console (text)

go-boot • tamago/amd64 (go1.24.1) • UEFI x64

.               <path>                   # load and start EFI image
build                                    # build information
cat             <path>                   # show file contents
clear                                    # clear screen
cpuid           <leaf> <subleaf>         # show CPU capabilities
date            (time in RFC339 format)? # show/change runtime date and time
efivar          (verbose)?               # list UEFI variables
dns             <host>                   # resolve domain
exit,quit                                # exit application
halt,shutdown                            # shutdown system
info                                     # runtime information
linux,l         (loader entry path)?     # boot Linux kernel image
linux,l,\r                               # `l \loader\entries\arch.conf`
log                                      # show runtime logs
ls              (path)?                  # list directory contents
lspci                                    # list PCI devices
memmap          (e820)?                  # show UEFI memory map
mode            <mode>                   # set screen mode
net             <ip> <mac> <gw> (debug)? # start UEFI networking
peek            <hex offset> <size>      # memory display (use with caution)
poke            <hex offset> <hex value> # memory write   (use with caution)
protocol        <registry format GUID>   # locate UEFI protocol
reset           (cold|warm)?             # reset system
stack                                    # goroutine stack trace (current)
stackall                                 # goroutine stack trace (all)
stat            <path>                   # show file information
uefi                                     # UEFI information
uptime                                   # show system running time
windows,win,w                            # launch Windows UEFI boot manager

> uefi
UEFI Revision ......: 2.70
Firmware Vendor ....: Lenovo
Firmware Revision ..: 0x1560
Runtime Services  ..: 0x90e2eb98
Boot Services ......: 0x6bd17690
Frame Buffer .......: 1920x1200 @ 0x4000000000
Configuration Tables: 0x8f426018
  ee4e5898-3914-4259-9d6e-dc7bd79403cf (0x8db6dc98)
  dcfa911d-26eb-469f-a220-38b7dc461220 (0x8b037018)
...

> memmap
Type Start            End              Pages            Attributes
02   0000000090000000 0000000090000fff 0000000000000001 000000000000000f
...

> linux \loader\entries\arch.conf
loading boot loader entry \loader\entries\arch.conf
go-boot exiting EFI boot services and jumping to kernel
Linux version 6.13.6-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20250207, GNU ld (GNU Binutils) 2.44)
...

Go Reference

The list of supported hardware is available in the project wiki HCL.

The list provides test IMAGE_BASE values to pass while Compiling.

Build the TamaGo compiler (or use the latest binary release):

wget https://github.com/usbarmory/tamago-go/archive/refs/tags/latest.zip
unzip latest.zip
cd tamago-go-latest/src && ./all.bash
cd ../bin && export TAMAGO=`pwd`/go

The following environment variables configure the go-boot.efi executable build:

  • IMAGE_BASE: must be set (in hex) within a memory range available in the target UEFI environment for the unikernel allocation, the HCL or memmap command from an UEFI Shell can provide such value, when empty a common default value is set.

  • DEFAULT_EFI_ENTRY: defines the . shortcut entry path for EFI image loading, it defaults to \efi\boot\bootx64.efi when unspecified.

  • DEFAULT_LINUX_ENTRY: defines the linux,l,\r shortcut loader entry path for Linux kernel image booting, it defaults to \loader\entries\arch.conf when unspecified.

  • CONSOLE: set to either com1 or text (default) controls the output console to either serial port or UEFI console.

  • NET: set to either 0 (default) or 1 controls enabling of UEFI networking support (see UEFI networking).

Build the go-boot.efi executable:

git clone https://github.com/usbarmory/go-boot && cd go-boot
make efi IMAGE_BASE=10000000 CONSOLE=text

The go-boot.efi application executable, built after Compiling, can be loaded from an UEFI Shell or boot manager, the following example shows an entry for systemd-boot:

# /boot/loader/entries/go-boot.conf
title Go Boot
efi /EFI/Linux/go-boot.efi

The following example shows creation of an EFI boot entry using efibootmgr:

efibootmgr -C -L "go-boot" -d $DISK -p $PART -l '\EFI\go-boot.efi'

With NET=1 passed in the environment builds include UEFI networking support through the Simple Network Protocol (SNP) and go-net.

On such builds the net and dns commands become available and make qemu will require a tap0 interface.

The net command takes an IP address in CIDR notation, a fixed MAC address or : to automatically generate a random MAC, and a gateway IP address as arguments.

The optional debug strings can be passed as final argument to net to enable Go profiling server and an unauthenticated SSH console exposing the UEFI shell.

> net 10.0.0.1/24 : 10.0.0.2 debug
starting debug servers:
        http://10.0.0.1:80/debug/pprof
        ssh://10.0.0.1:22
network initialized (10.0.0.1/24 da:e7:ac:e2:5e:05)

> dns golang.org
[142.251.209.17 2a00:1450:4002:410::2011]

QEMU supported targets can be executed under emulation, using the Open Virtual Machine Firmware as follows:

make qemu OVMFCODE=<path to OVMF_CODE.fd>

With NET=1 tap0 should be configured as follows (Linux example):

ip tuntap add dev tap0 mode tap group <your user group>
ip addr add 10.0.0.2/24 dev tap0
ip link set tap0 up

An emulated target can be debugged with GDB using make qemu-gdb, this will make qemu waiting for a GDB connection that can be launched as follows:

gdb -ex "target remote 127.0.0.1:1234"

Breakpoints can be set in the usual way:

The following example demonstrates how to create, and deploy, a UEFI-bootable image for cloud deployments:

go-boot | https://github.com/usbarmory/go-boot Copyright (c) The go-boot authors. All Rights Reserved.

These source files are distributed under the BSD-style license found in the LICENSE file.

联系我们 contact @ memedata.com