All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Laszlo Ersek <lersek@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: edk2-devel@lists.sourceforge.net,
	qemu devel list <qemu-devel@nongnu.org>,
	BALATON Zoltan <balaton@eik.bme.hu>
Subject: Re: [Qemu-devel] [edk2] syslinux vs. OVMF
Date: Tue, 26 May 2015 17:36:01 +0300	[thread overview]
Message-ID: <556484D1.2040608@msgid.tls.msk.ru> (raw)
In-Reply-To: <5527A093.30904@redhat.com>

10.04.2015 13:06, Laszlo Ersek wrote:
> On 04/10/15 10:14, Gerd Hoffmann wrote:
>>   Hi,
>>
>>> In summary, please ask Gerd to rebuild the ipxe binaries that are
>>> bundled with upstream qemu such that they include those two iPXE patches
>>> of ours (see the last reference).
>>
>> https://www.kraxel.org/cgit/qemu/log/?h=rebase/roms-next
>>
>> Can you give this a try?
> 
> Thank you for this update, I tested it.
> 
> (1) I reproduced the issue, so that I could be sure that the fix wasn't
> meaningless. Indeed the bug reproduces with the iPXE binaries bundled
> with upstream qemu.
> 
[]
> * e1000 results:
> - OVMF        loads shim.efi    via network
> - shim.efi    loads grubx64.efi via network
> - grubx64.efi loads grub.cfg    via network
> - grubx64.efi loads vmlinuz     via network
> - grubx64.efi loads initrd.img  via network
> - guest kernel boots
> 
> So, I think the update is fine in general...

However, after the update of efi roms in qemu, the original problem
of booting syslinux in OVMF still persists.  I received several
private messages asking whenever I succeeded in resolving the
original prob outlined at

 http://www.syslinux.org/archives/2014-November/022804.html

and I always referred to this thread, until someone told me that
the update does not fix the issue.  Now I verified it locally,
and no, I still can't use syslinux with OVMF with qemu efi roms,
getting exactly the same output as I've seen on Nov-2014.
As you checked, grub loads, but apparently syslinux still doesn't.

Is it a different issue perhaps?

Thanks,

/mjt

  parent reply	other threads:[~2015-05-26 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.GSO.2.01.1504062122470.1832@mono>
     [not found] ` <5523E12E.8010103@redhat.com>
     [not found]   ` <1428653687.11559.5.camel@nilsson.home.kraxel.org>
2015-04-10 10:06     ` [Qemu-devel] [edk2] syslinux vs. OVMF Laszlo Ersek
2015-04-10 11:04       ` [Qemu-devel] virtio-net regression [was: syslinux vs. OVMF] Laszlo Ersek
2015-04-10 14:36         ` Laszlo Ersek
2015-04-10 19:56           ` Laszlo Ersek
2015-05-26 14:36       ` Michael Tokarev [this message]
2015-05-26 16:49         ` [Qemu-devel] [edk2] syslinux vs. OVMF Laszlo Ersek
2015-05-26 17:04           ` Michael Tokarev
2015-05-26 18:38             ` Laszlo Ersek
2015-05-26 20:17               ` BALATON Zoltan
2015-05-26 20:27                 ` Michael Tokarev
2015-05-26 20:42                   ` BALATON Zoltan
2015-05-26 21:31             ` Michael Tokarev

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=556484D1.2040608@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=balaton@eik.bme.hu \
    --cc=edk2-devel@lists.sourceforge.net \
    --cc=kraxel@redhat.com \
    --cc=lersek@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.