qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] QEMU + OVMF, bootable linux image


From: Jason Dickens
Subject: [Qemu-devel] QEMU + OVMF, bootable linux image
Date: Fri, 3 Feb 2017 13:20:44 -0500
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0

I am trying to create a raw Linux image that is bootable by QEMU using the OVMF firmware image.

Basically, I have used a standard Ubuntu ISO and a empty raw image. Executing qemu-system-x86_64 with the ISO as CD and the other image as a hardrive I have been able to install Ubuntu on the image, no problem.

However, when trying to boot the created image I simply get the UEFI shell?

I've noticed the following:

1. The ISO image which boots with OVMF in UEFI just fine has the following format (from fdisk):

Disk ubuntu-14.04.3-desktop-amd64.iso: 1006 MiB, 1054867456 bytes, 2060288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6a6216fc

Device                           Boot   Start     End Sectors Size Id Type
ubuntu-14.04.3-desktop-amd64.iso1 * 0 2060287 2060288 1006M 0 Empty ubuntu-14.04.3-desktop-amd64.iso2 2038760 2043303 4544 2.2M ef EFI (FAT-12/16/32)

2. The image created by the linux install has the following(from fdisk):

Disk ovmf_test_image: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 36240C48-C008-4619-BE31-26D271000490

Device              Start      End  Sectors  Size Type
ovmf_test_image1     2048  1050623  1048576  512M EFI System
ovmf_test_image2  1050624 12584959 11534336  5.5G Linux filesystem
ovmf_test_image3 12584960 20969471  8384512    4G Linux swap


Can someone help me understand the format requirements to boot using OVMF in UEFI mode? Clearly these two images are dramatically different. However, I would expect #2 to be the more modern method and more likely to work? As for QEMU command I use literally the same command switching only between the file names to get the different results it looks something like this:

qemu-system-x86_64 -drive file=ovmf_test_image,format=raw -m 4G --bios.bin -net none

Thanks,

Jason








reply via email to

[Prev in Thread] Current Thread [Next in Thread]