如何在Qemu中启动FreeBSD镜像？附已尝试的失败命令

Hey there! I’ve helped a bunch of folks get FreeBSD images running in QEMU after they work on EC2, so let’s walk through fixing your issue step by step. The commands you tried are missing a few key pieces—let’s break down what’s wrong and how to fix it.

Why Your Previous Commands Failed #

• When you use -kernel kernel or -kernel loader, QEMU expects those files to exist on your host system, not inside the disk image. Unless you’ve extracted them from disk.img, those commands won’t find the right files.
• Even if you did extract them, you weren’t specifying the root disk or proper boot parameters that FreeBSD needs to mount its filesystem.

The Easiest Fix: Let QEMU Boot Directly from the Disk Image #

This is the simplest approach—just let QEMU simulate the full boot process like EC2 does.

For BIOS-Based FreeBSD Images #

Run this command (it tells QEMU to use your disk as the primary hard drive, enables serial console output, and disables graphics):

qemu-system-x86_64 -hda disk.img -nographic -serial mon:stdio

For UEFI-Based FreeBSD Images #

If your EC2 image uses UEFI (common for newer FreeBSD versions), you’ll need to specify a UEFI firmware file (most Linux distros package this as ovmf):

# On Debian/Ubuntu, install OVMF first: sudo apt install ovmf
qemu-system-x86_64 -hda disk.img -nographic -serial mon:stdio -bios /usr/share/OVMF/OVMF_CODE.fd

If You Must Use the Kernel/Loader Directly #

If you want to manually specify the kernel or loader (for debugging, etc.), first extract them from the disk image:

1. Mount the disk image on your FreeBSD host:

# Attach the image to a memory disk
mdconfig -a -t vnode -f disk.img
# Check partitions (look for the root filesystem, usually a UFS or ZFS partition)
gpart show md0
# Mount the root partition (replace md0p2 with your actual root partition)
mount /dev/md0p2 /mnt

2. Copy the loader and kernel to your working directory:

cp /mnt/boot/loader .
cp /mnt/boot/kernel/kernel .
# Unmount and detach the image
umount /mnt
mdconfig -d -u 0

3. Now use the loader to boot:

qemu-system-x86_64 -kernel loader -nographic -append 'bootdisk=ada0 console=ttyS0' -hda disk.img

Or boot directly with the kernel:

qemu-system-x86_64 -kernel kernel -nographic -append 'root=ada0 ro console=ttyS0' -hda disk.img

Key Notes #

• Replace ada0 with the correct disk device name if your image uses a different one (check /etc/fstab inside the image if you’re unsure).
• The -serial mon:stdio flag ensures you get the console output in your terminal, which is critical for debugging boot issues.

内容的提问来源于stack exchange，提问作者Steven P