qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 18:26:50 +0200	[thread overview]
Message-ID: <539731CA.5040108@redhat.com> (raw)
In-Reply-To: <20140610161048.GM8813@tesla>

On 06/10/14 18:10, Kashyap Chamarthy wrote:
> On Tue, Jun 10, 2014 at 05:18:21PM +0200, Laszlo Ersek wrote:
>> On 06/10/14 15:04, Kashyap Chamarthy wrote:
>>> Heya,
>>>
>>> Laszlo pointed out OVMF packages for Fedora from here[1]. I tried a
>>> simple test using this[2] by installing Fedora onto a USB stick.
>>>
>>> Once Fedora is installed on the USB stick (/dev/sdb), and I attempt to
>>> boot into the USB device as below, I get the Fedora serial console
>>> login prompt just fine through a QEMU vnc display:
>>>
>>>     $ sudo qemu-system-x86_64 -machine accel=kvm -m 256 -bios \
>>>       /usr/share/OVMF/OVMFX64.fd  /dev/sdb)
>>>
>>>
>>> However, when I try with the below QEMU invocation, I get "Boot
>>> Failed. EFI Floppy":
>>>
>>>     $ sudo qemu-system-x86_64 -machine accel=kvm -m 512 -nographic \
>>>       -nodefconfig -nodefaults  -serial stdio \
>>>       -bios /usr/share/OVMF/OVMFX64.fd /dev/sdb
>>>     Boot Failed. EFI Floppy
>>>     Boot Failed. EFI Floppy 1
>>>
>>>
>>> Next, I tried booting into a Fedora disk image with the below QEMU
>>> invocation, and I get a UEFI interactive shell as below (after "Boot
>>> Failed. EFI Floppy"):
>>>
>>>     $ sudo qemu-system-x86_64 -machine accel=kvm -m 512 -nographic \
>>>       -nodefconfig -nodefaults  -serial stdio -bios /usr/share/OVMF/OVMFX64.fd \
>>>       -drive file=/var/lib/libvirt/images/Fedora-x86_64-20-20140407-sda.qcow2,if=ide,format=qcow2,cache=none
>>>     UEFI Interactive Shell v2.0
>>>     EDK II
>>>     UEFI v2.40 (EDK II, 0x00010000)
>>>     Mapping table
>>>          BLK2: Alias(s):
>>>               PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
>>>          BLK3: Alias(s):
>>>               PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)/HD(1,MBR,0x00014C24,0x7A1,0x3FF83D)
>>>          BLK0: Alias(s):
>>>               PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x0)
>>>          BLK1: Alias(s):
>>>               PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x1)
>>>
>>>     Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
>>>     Shell>
>>>
>>>
>>> Is this expected behavior?
>>>
>>>
>>>   [1] http://copr-be.cloud.fedoraproject.org/results/bonzini/ovmf/fedora-20-x86_64/edk2-20140328svn15376-4.fc20/
>>>   [2] http://people.freedesktop.org/~kay/installer/README
>>>
>>
>> Document [2] seems to imply that the disk image you write out to the USB
>> stick is a preinstalled (fixed media) Fedora system. 
> 
> The USB stick is created with Fedora Rawhide image using this
> script: http://people.freedesktop.org/~kay/installer/installer.sh
> 
>     $ sudo ./installer.sh /dev/sdb
> 
> Then, invoke QEMU.

That script is exactly what I don't want to run :) Can you upload the
result somewhere?

> This is disk image #3:
> 
>     http://download.fedoraproject.org/pub/fedora/linux/updates/20/Images/x86_64/Fedora-x86_64-20-20140407-sda.qcow2

OK, I'll try to check this out.

Thanks
Laszlo

  reply	other threads:[~2014-06-10 16: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 [this message]
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
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=539731CA.5040108@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).