I highly recommend utilizing the fix proposed in the original comment,
because it "just works"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE
> I think there's a bug in the iPXE network driver, but now it only
applies to bare-metal users essentially.
Yes, yes it does :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable
** Changed in: maas
Milestone: 2.5.x => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage notifications about this bug
** Changed in: maas
Milestone: 2.5.0rc1 => 2.5.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage notifications about this
** Changed in: maas
Milestone: 2.5.0beta2 => 2.5.0rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage notifications about
** Changed in: maas
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage notifications about
This bug was fixed in the package ipxe - 1.0.0+git-20180124.fbe8c52d-
0ubuntu2.1
---
ipxe (1.0.0+git-20180124.fbe8c52d-0ubuntu2.1) bionic; urgency=medium
* Build ROMs for QEMU with CONFIG=qemu (LP: #1789319)
-- Julian Andres Klode Mon, 10 Sep 2018 14:56:17
+0200
** Changed in:
I've verified that the updated ipxe package fixes virsh UEFI deployments
wtih MAAS. I tested commissioning, and deploying both Ubuntu 18.04 and
CentOS 7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified that -ubuntu2 fails and -ubuntu2.1 from proposed works by
running the command specified in the test case in a bionic system.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification
Hello Lee, or anyone else affected,
Accepted ipxe into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ipxe/1.0.0+git-20180124.fbe8c52d-
0ubuntu2.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new
Ugh. Let's try to make this clear. Nothing here does http boot. There
are three scenarios, all do PXE TFTP booting:
(1) iPXE network stack replaces firmware one - caused this bug
(2) iPXE without replacing firmware's network stack (CONFIG=qemu) - this works
fine
(3) No iPXE, use OVMF's native
Isn't iPXE what implements TFTP PXE boot? When I tried Julian's command
kvm tries UEFI HTTP boot which isn't currently implemented in MAAS and
is blocked by lack of grub support(LP:1787630).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes, I think there's a bug in the iPXE network driver, but now it only
applies to bare-metal users essentially. If that is a problem to anyone
in practice, I'd suggest opening a new bug for that (or directly going
upstream, maybe); so we can use this one to track the fix for MAAS VM
stuff.
--
Isn't that just a workaround? There is still an underlying bug in the
iPXE network driver isn't there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using
This bug was fixed in the package ipxe - 1.0.0+git-20180124.fbe8c52d-
0ubuntu4
---
ipxe (1.0.0+git-20180124.fbe8c52d-0ubuntu4) cosmic; urgency=medium
* Build ROMs for QEMU with CONFIG=qemu (LP: #1789319)
-- Julian Andres Klode Mon, 10 Sep 2018 14:56:17
+0200
** Changed in:
** Changed in: ipxe (Ubuntu Bionic)
Status: New => In Progress
** Description changed:
- libvirt supports creating virtual machines running in UEFI mode and uses
- iPXE to enable network booting. When MAAS gives shimx64.efi, as it does
- on all UEFI systems, to iPXE it chainloads grub but
I just uploaded -0ubuntu4 (and -0ubuntu3 earlier to fix FTBFS), that
enables CONFIG=qemu for our qemu roms. This means QEMU will work fine,
but grub/efi binaries and the CD-ROM images would still fail to load
grub via shim I think. Not sure there's much that can be done there.
** Changed in: ipxe
Thanks Laszlo, ipxe built with CONFIG=qemu successfully makes shim load
grub.
** Changed in: shim (Ubuntu)
Status: Triaged => Invalid
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ipxe (Ubuntu)
Status: Triaged => In Progress
--
You received
I could successfully chainload grub from shim by using virtio-net and
disabling iPXE. Minimal reproducer:
sudo kvm -bios /usr/share/OVMF/OVMF_CODE.fd -device virtio-net,netdev=n1
-netdev user,id=n1,tftp=/boot/efi/EFI/ubuntu,bootfile=shimx64.efi
-global virtio-net-pci.romfile=""
if I remove the
I may be able to provide some information here, about iPXE. (Corrections
welcome, obviously!)
iPXE can be built in a number of ways. Two of those are: (1) as a UEFI
*driver* that is presented in a NIC's PCI ROM BAR (i.e., as part of a
PCI expansion ROM), (2) as a UEFI *application* that can be
** Changed in: maas
Milestone: 2.5.0beta1 => 2.5.0beta2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage notifications
With systemd-boot instead of grub, it simply fails, pretendign the file
does not exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
I reproduced this using:
$ kvm -bios /usr/share/OVMF/OVMF_CODE.fd -device e1000,netdev=n1 -netdev
user,id=n1,tftp=/boot/efi,bootfile=/EFI/ubuntu/grubx64.efi
and manually booting shim from the iPXE commandline which then tries to
chainload grubx64.efi.
iPXE> boot
** Tags added: id-5b85855515a6063ed300711d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage notifications about this bug go
** Changed in: maas
Milestone: None => 2.5.0beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage notifications about
On Tue, Aug 28, 2018 at 07:31:14PM -, Andres Rodriguez wrote:
> isn't this the same issue as
> https://bugs.launchpad.net/maas/+bug/1711203
No, this failure is unrelated to secureboot and appears to be specific to
the ovmf UEFI firmware implementation
--
You received this bug notification
isn't this the same issue as
https://bugs.launchpad.net/maas/+bug/1711203
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage
One thing to add, this happens *before* any GRUB configuration is
loaded. The machine requests an address over DHCP, bootx64.efi(the shim)
over TFTP, and then grubx64.efi over TFTP. Nothing else is requested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If anything, TBH it's unlikely to be shim /or/ grub; seeing as
netbooting on hardware just works; but we should have a good look at
shim and grub anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error message shown by shim in the screenshot is:
Malformed binary after Attribute Certificate Table
datasize: ? SumOfBytesHashed: ? SecDir->Size: ?
hashsize: ? SecDir->VirtualAddress: 0x002E6088
Something is wrong here. These '?' are the result of a printf %u format
string... that
I can reproduce. This looks to be something in grub that shim doesn't
appear to like.
** No longer affects: ipxe (Ubuntu)
** Package changed: shim-signed (Ubuntu) => grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
Sorry forgot to include the failure screenshot.
** Attachment added: "libvirt UEFI iPXE failure with shimx64.efi"
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1789319/+attachment/5181784/+files/maas-test-5-failure.png
--
You received this bug notification because you are a
So, what is the failure mode here? Just not finding the binaries?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage
When I configure the machine to network boot iPXE is used to try to boot
the machine via TFTP. If I go into the UEFI firmware on the virtual
machine I can see there are two options to network boot. The first is
PXEv4, the second is HTTPv4. It doesn't seem that booting HTTPv4 uses
iPXE however that
** Attachment added: "libvirt UEFI machine PXE booting using iPXE"
https://bugs.launchpad.net/maas/+bug/1789319/+attachment/5181603/+files/maas-test-5-ipxe.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "libvirt UEFI boot configuration"
https://bugs.launchpad.net/maas/+bug/1789319/+attachment/5181604/+files/maas-test-5-firmware.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "libvirt machine configuration"
https://bugs.launchpad.net/maas/+bug/1789319/+attachment/5181602/+files/maas-test-5.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
I don't understand what iPXE has to do with anything here. If you are
running a virtual machine in UEFI mode, you have a full UEFI firmware
implementation which directly supports dhcp netboot without any
involvement of iPXE. And I am unaware of any issues with netbooting
ovmf to
** Description changed:
libvirt supports running in UEFI mode and uses iPXE to enable network
booting. When MAAS gives shimx64.efi, as it does on all UEFI systems, to
iPXE it chainloads grub but fails to the grub prompt. If I modify MAAS
to give grubx64.efi instead of shimx64.efi UEFI
39 matches
Mail list logo
