unable to pxe boot with GPT partitions in image

[knalb]

I'm unable to pxe boot an image created with GPT partitions. I've tried multiple memdisk options, partition sizes and even the publicly available usb image. This problem does not happen when images are created with BSD style partitions. Is there something easy I'm missing? A cursory search of google hasn't really been helpful.

[DaElf]

Not sure what your pxe entry looks like so hard to say.

These are some helper rules to help create pxe entries.

https://github.com/DaElf/mfsbsd/blob/isilon-master/pxe.isi.mk

[knalb]

I've tried raw, bigraw, etc. I should have included this originally, but here's an example of what I have in a prod pxe menu:

LABEL BSD_INSTALLER
        MENU LABEL BSD_INSTALLER
        KERNEL memdisk
        APPEND initrd=DIRECTORY/bsd_installer.img bigraw

This is handed out via dhcp/gPXE(yes, I know, old)/tftp config that hasn't changed in years. It seems to work great for the BSD labeled ones. Note that in this example I have no global append, so the one from this entry passes initrd as if it were an initrd entry(according to the syslinux docs).

[rubenk]

I'm not sure if this helps you, but I've been able to pxe-boot mfsbsd-10.3-RELEASE-amd64.img with iPXE, both with memdisk and with sanboot

Here's my iPXE menu:
memdisk:

:mfsbsd
echo Starting MFSBSD
kernel memdisk harddisk raw 
initrd http://fikkie.home.rubenkerkhof.com/mfsbsd-10.3-RELEASE-amd64.img
boot || goto failed

sanboot:

:mfsbsd
echo Starting MFSBSD
sanboot http://fikkie.home.rubenkerkhof.com/mfsbsd-10.3-RELEASE-amd64.img
boot || goto failed

It's hard to tell what your issue is without more details. What is the exact failure you are seeing?

[knalb]

To be honest, it's been long enough that I don't remember where it was
failing exactly. I'm looking at rolling out iPXE to replace my aging gPXE
install everywhere in the next week or so, and I'll give it another shot.
Thanks!

On Fri, Jul 22, 2016 at 11:10 AM, Ruben Kerkhof notifications@github.com
wrote:

I'm not sure if this helps you, but I've been able to pxe-boot
mfsbsd-10.3-RELEASE-amd64.img with iPXE, both with memdisk and with sanboot

Here's my iPXE menu:
memdisk:

:mfsbsd
echo Starting MFSBSD
kernel memdisk harddisk raw
initrd http://fikkie.home.rubenkerkhof.com/mfsbsd-10.3-RELEASE-amd64.img
boot || goto failed

sanboot:

:mfsbsd
echo Starting MFSBSD
sanboot http://fikkie.home.rubenkerkhof.com/mfsbsd-10.3-RELEASE-amd64.img
boot || goto failed

It's hard to tell what your issue is without more details. What is the
exact failure you are seeing?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#69 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGKPUjp0HSFBRGWwK17oYmspJei-3Eeaks5qYPl3gaJpZM4IOEnt
.

[knalb]

BTW, I finally figured out what I was doing wrong. Somehow I failed to notice that while I had updated iPXE, I had missed the old syslinux binaries. Now that I'm not trying to use one from a decade ago, this works fine.

[bms]

When using mfsBSD with Cobbler, I use SYSLINUX's memdisk driver. Due to the HDD emulation this uses, this can be incompatible with some BIOSes. In particular, the version of SeaBIOS that ships with more recent QEMU/KVM needs to be downgraded. Some Dell systems are potentially affected, also.