From: Laszlo Ersek <lersek@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: pbonzini@redhat.com, Peter Jones <pjones@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Booting a guest with OVMF
Date: Tue, 10 Jun 2014 19:26:47 +0200 [thread overview]
Message-ID: <53973FD7.1080601@redhat.com> (raw)
In-Reply-To: <20140610161048.GM8813@tesla>
On 06/10/14 18:10, Kashyap Chamarthy wrote:
> This is disk image #3:
>
> http://download.fedoraproject.org/pub/fedora/linux/updates/20/Images/x86_64/Fedora-x86_64-20-20140407-sda.qcow2
As I suspected, this disk image is inapproprite for UEFI virtual machines.
$ guestfish --ro -a Fedora-x86_64-20-20140407-sda.qcow2
><fs> launch
><fs> list-filesystems
/dev/sda1: ext4
It has no EFI system partition.
The image must have been prepared for BIOS machines. (For VMs that
implies SeaBIOS, not OVMF.)
-o-
For cases #1 and #2, I looked into
<http://people.freedesktop.org/~kay/installer/installer.sh>. It
- formats an EFI system partition as FAT32 alright,
- mounts it as "/run/installer-$ROOT/system/boot",
- does some other stuff,
- and then executes
chroot /run/installer-$ROOT/system/ gummiboot install --no-variables
I assume something goes wrong in this step (ie. the ESP won't contain
any gummiboot binary under EFI/BOOT/BOOTX64.EFI).
"install.sh" seems to support formatting regular files -- that should
allow you to both upload one for inspection (eg. with guestfish, see
above), and also to test it with qemu (without needing a USB stick).
Thanks
Laszlo
next prev parent reply other threads:[~2014-06-10 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 13:04 [Qemu-devel] Booting a guest with OVMF Kashyap Chamarthy
2014-06-10 15:18 ` Laszlo Ersek
2014-06-10 16:10 ` Kashyap Chamarthy
2014-06-10 16:26 ` Laszlo Ersek
2014-06-10 17:16 ` Kashyap Chamarthy
2014-06-10 17:30 ` Laszlo Ersek
2014-06-10 18:03 ` Kashyap Chamarthy
2014-06-10 17:26 ` Laszlo Ersek [this message]
2014-06-11 16:35 ` Laszlo Ersek
2014-06-11 18:11 ` Kashyap Chamarthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53973FD7.1080601@redhat.com \
--to=lersek@redhat.com \
--cc=kchamart@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pjones@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.