ipxe failes to boot in efi mode due to incomplete ipxe script
This bug report will be marked for expiration in 19 days if no further activity occurs. (find out why)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Incomplete
|
Medium
|
Unassigned | ||
3.6 |
Incomplete
|
Medium
|
Unassigned |
Bug Description
Out of the box booting using ipxe ends with kernel panic (see screenshot). It can be worked around by putting
initrd=boot-initrd
to command line option. However I think this should be addressed in the ipxe script template.
Please see
https:/
for reference.
Steps to reproduce:
1. Create Hyper-V machine, version 2 (efi). Optional: verify that regular PXE boot works.
2. Mount dvd image from https:/
3. Commisioning ends with kernel panic.
Default script that does not work:
root@maas:~# curl http://
#!ipxe
kernel http://
imgargs boot-kernel nomodeset ro root=squash:http://
initrd http://
boot
root@maas:~#
What works:
root@laptop:~# cat /var/log/kern.log |grep Command
Jan 9 10:19:14 laptop kernel: [ 0.000000] Command line: boot-kernel nomodeset ro root=squash:http://
root@laptop:~#
Regards!
Michal Kielkowski
summary: |
- ipxe mode failes to boot in efi mode due to incomplete ipxe script + ipxe failes to boot in efi mode due to incomplete ipxe script |
Changed in maas: | |
status: | New → Triaged |
Changed in maas: | |
importance: | Undecided → High |
Changed in maas: | |
assignee: | nobody → Jack Lloyd-Walters (lloydwaltersj) |
Changed in maas: | |
assignee: | Jack Lloyd-Walters (lloydwaltersj) → nobody |
Changed in maas: | |
milestone: | none → 3.5.0 |
Changed in maas: | |
milestone: | 3.5.0 → 3.5.x |
tags: | added: bug-council |
no longer affects: | maas/3.5 |
Hi, just wanted to add that we encounter the same issue on some of our machines. What all machines have in common is that they use an external 10GiB NIC (Aquantia) with EFI boot. Both HTTP and PXE options are failing, for PXE we receive the same output as in the image attached.
Is there a way for a manual fix? Which files do I need to edit in order to add the missing parameter (AMD64 machines)? dist-packages/ provisioningser ver/... " or similar.
We are using DEB version of MAAS, so I guess the path should be "/lib/python3/
Best regards,
Samuel Knobloch