Erinn Looney-Triggs | 9 Jul 2012 22:17
Picon

UEFI PXE boot

Has anyone here had luck with UEFI based PXE booting in a Linux
environment?

I am essentially running into the same issue as this person here:
http://lists.us.dell.com/pipermail/linux-poweredge/2011-November/045603.html

Basically it will boot grab the grub image, transfer the vmlinuz and
initrd and then just hang, with this error:

Trying to allocate 923 pages for VMLINUZ
[Linux-EFI, setup=0x1039, size=0x39a2c0]
[Initrd, addr=0x7de51000, size=0x1cabcd5]

Any insights?

-Erinn

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Kaj Niemi | 10 Jul 2012 09:06
Favicon

Re: UEFI PXE boot

No luck I'm afraid, I spent about a week last winter to try to get it to work. I had a bunch of R510s that I wanted
to try to UEFI PXE boot but fortunately was able to skip that part as they had the 2 extra startup disks inside
(which were smaller and could be booted from without UEFI).

If you get it to boot successfully all the way please write it up somewhere. ;)

Kaj
-- 
Kaj J. Niemi
BaseN Corporation
<kajtzu <at> basen.net>
FI +358 45 63 12000
KSA +966 54 899 7789

On Jul 9, 2012, at 23:17, Erinn Looney-Triggs wrote:

> Has anyone here had luck with UEFI based PXE booting in a Linux
> environment?
> 
> I am essentially running into the same issue as this person here:
> http://lists.us.dell.com/pipermail/linux-poweredge/2011-November/045603.html
> 
> Basically it will boot grab the grub image, transfer the vmlinuz and
> initrd and then just hang, with this error:
> 
> Trying to allocate 923 pages for VMLINUZ
> [Linux-EFI, setup=0x1039, size=0x39a2c0]
> [Initrd, addr=0x7de51000, size=0x1cabcd5]
> 
> Any insights?
(Continue reading)

Jared_Dominguez | 11 Jul 2012 19:23
Picon
Favicon

RE: UEFI PXE boot

Did you check the errata mentioned on the bottom of that bug report? I've copied the link below.

http://rhn.redhat.com/errata/RHBA-2012-0892.html

--Jared

> -----Original Message-----
> From: linux-poweredge-bounces-Lists On Behalf Of Kaj Niemi
> Sent: Tuesday, July 10, 2012 2:06 AM
> To: Erinn Looney-Triggs
> Cc: linux-poweredge-Lists
> Subject: Re: UEFI PXE boot
> 
> No luck I'm afraid, I spent about a week last winter to try to get it to work. I
> had a bunch of R510s that I wanted to try to UEFI PXE boot but fortunately
> was able to skip that part as they had the 2 extra startup disks inside (which
> were smaller and could be booted from without UEFI).
> 
> If you get it to boot successfully all the way please write it up somewhere. ;)
> 
> 
> 
> Kaj
> --
> Kaj J. Niemi
> BaseN Corporation
> <kajtzu <at> basen.net>
> FI +358 45 63 12000
> KSA +966 54 899 7789
> 
(Continue reading)

Erinn Looney-Triggs | 11 Jul 2012 20:36
Picon

Re: UEFI PXE boot

On 07/11/2012 09:23 AM, Jared_Dominguez <at> DELL.com wrote:
> Did you check the errata mentioned on the bottom of that bug report? I've copied the link below.
> 
> http://rhn.redhat.com/errata/RHBA-2012-0892.html
> 
> --Jared
> 
>> -----Original Message-----
>> From: linux-poweredge-bounces-Lists On Behalf Of Kaj Niemi
>> Sent: Tuesday, July 10, 2012 2:06 AM
>> To: Erinn Looney-Triggs
>> Cc: linux-poweredge-Lists
>> Subject: Re: UEFI PXE boot
>>
>> No luck I'm afraid, I spent about a week last winter to try to get it to work. I
>> had a bunch of R510s that I wanted to try to UEFI PXE boot but fortunately
>> was able to skip that part as they had the 2 extra startup disks inside (which
>> were smaller and could be booted from without UEFI).
>>
>> If you get it to boot successfully all the way please write it up somewhere. ;)
>>
>>
>>
>> Kaj
>> --
>> Kaj J. Niemi
>> BaseN Corporation
>> <kajtzu <at> basen.net>
>> FI +358 45 63 12000
>> KSA +966 54 899 7789
(Continue reading)

Erinn Looney-Triggs | 17 Jul 2012 06:33
Picon

Re: UEFI PXE boot

On 07/11/2012 09:23 AM, Jared_Dominguez <at> DELL.com wrote:
> Did you check the errata mentioned on the bottom of that bug report? I've copied the link below.
> 
> http://rhn.redhat.com/errata/RHBA-2012-0892.html
> 
> --Jared
> 
>> -----Original Message-----
>> From: linux-poweredge-bounces-Lists On Behalf Of Kaj Niemi
>> Sent: Tuesday, July 10, 2012 2:06 AM
>> To: Erinn Looney-Triggs
>> Cc: linux-poweredge-Lists
>> Subject: Re: UEFI PXE boot
>>
>> No luck I'm afraid, I spent about a week last winter to try to get it to work. I
>> had a bunch of R510s that I wanted to try to UEFI PXE boot but fortunately
>> was able to skip that part as they had the 2 extra startup disks inside (which
>> were smaller and could be booted from without UEFI).
>>
>> If you get it to boot successfully all the way please write it up somewhere. ;)
>>
>>
>>
>> Kaj
>> --
>> Kaj J. Niemi
>> BaseN Corporation
>> <kajtzu <at> basen.net>
>> FI +358 45 63 12000
>> KSA +966 54 899 7789
(Continue reading)

Steven Dick | 18 Jul 2012 03:10
Picon

Re: UEFI PXE boot



On Tue, Jul 17, 2012 at 12:33 AM, Erinn Looney-Triggs <erinn.looneytriggs <at> gmail.com> wrote:
I am going to try iPXE/gPXE next.

I have booted UEFI systems just fine using the latest ipxe + syslinux as well as syslinux alone.
I have not tried it with grub.
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Erinn Looney-Triggs | 18 Jul 2012 06:30
Picon

Re: UEFI PXE boot

On 07/17/2012 05:10 PM, Steven Dick wrote:
> 
> 
> On Tue, Jul 17, 2012 at 12:33 AM, Erinn Looney-Triggs
> <erinn.looneytriggs <at> gmail.com <mailto:erinn.looneytriggs <at> gmail.com>> wrote:
> 
>     I am going to try iPXE/gPXE next.
> 
> 
> I have booted UEFI systems just fine using the latest ipxe + syslinux as
> well as syslinux alone.
> I have not tried it with grub.

Can you elaborate on that a bit, I am kind of new to the PXE world so I
am trying to figure it out. From my understanding something like Ipxe is
loaded which then loads the next stage in the system, however you are
saying that you can skip any intermediaries and go straight to syslinux,
how do you go about that? What hardware are you doing this on?

-Erinn

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Steven Dick | 18 Jul 2012 06:50
Picon

Re: UEFI PXE boot



On Wed, Jul 18, 2012 at 12:30 AM, Erinn Looney-Triggs <erinn.looneytriggs <at> gmail.com> wrote:
On 07/17/2012 05:10 PM, Steven Dick wrote:
> I have booted UEFI systems just fine using the latest ipxe + syslinux as
> well as syslinux alone.
> I have not tried it with grub.

Can you elaborate on that a bit, I am kind of new to the PXE world so I
am trying to figure it out. From my understanding something like Ipxe is
loaded which then loads the next stage in the system, however you are
saying that you can skip any intermediaries and go straight to syslinux,
how do you go about that? What hardware are you doing this on?


I've done this on all sorts of hardware, but admittedly, only one or two uefi machines.
I have some R710 machines, but I don't recall if UEFI is enabled on them.

iPXE is nice, but not necessary.  It loads an extra layer on top of the bios pxe layer; the iPXE layer supports protocols other than icky tftp (like http or iscsi for instance) and does some other fancy things.

But what you really need (with or without iPXE) is syslinux (aka pxelinux) or some other bootloader (grub) that can actually load an operating system.  It is possible to get syslinux to load a kernel and an initial ram disk and feed some kernel command line options to that kernel and get it all started.

If you use iPXE, you can load the kernel and initial ram disk via http, which is typically much faster than tftp, which is what syslinux will use by itself.  However, iPXE typically requires a second dhcp request, which slows things down a bit, so there is a tradeoff.

There is plenty of documentation on how to get this all to work on the ipxe web page, the gpxe web page, the syslinux web page, etc.

This page looks helpful: http://www.syslinux.org/wiki/index.php/PXELINUX

None of this really relates to UEFI except that you probably need a UEFI aware version of syslinux, but I'm not even totally sure how important that is.   This also isn't related to Dell PowerEdge, except that the PE line all has good pxe support in their bios.  At some point in time, I've probably pxe booted every poweredge server I have, and some of mine still do it every time they power up.
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Steven Dick | 18 Jul 2012 07:03
Picon

Re: UEFI PXE boot



On Wed, Jul 18, 2012 at 12:50 AM, Steven Dick <kg4ydw <at> gmail.com> wrote:
But what you really need (with or without iPXE) is syslinux (aka pxelinux) or some other bootloader (grub) that can actually load an operating system.


Let me clarify this somewhat.

I said you don't _need_ iPXE except to use http instead of tftp.
This isn't entirely true.  I have found that syslinux has some bugs in it, especially relating to loading very large images, and using iPXE seems to cover that up, as iPXE uses its own loader (with syslinux on top) that does a better job.  (But this only matters for booting memdisk with large ISOs, syslinux alone should be fine for just a kernel and an initrd.)

It is possible that iPXE similarly covers up UEFI problems with syslinux.
I have booted UEFI machines using ipxe + syslinux, but not syslinux alone.  (Just haven't tried.)  Also, the bugs I am seeing might be in bios, rather than syslinux itself, as syslinux would probably be using the bios pxe/tftp code to do its loading, or alternately, it would use ipxe's http or tftp code, and syslinux really wouldn't know the difference.



_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Erinn Looney-Triggs | 18 Jul 2012 21:51
Picon

Re: UEFI PXE boot

On 07/17/2012 09:03 PM, Steven Dick wrote:
> 
> 
> On Wed, Jul 18, 2012 at 12:50 AM, Steven Dick <kg4ydw <at> gmail.com
> <mailto:kg4ydw <at> gmail.com>> wrote:
> 
>     But what you really need (with or without iPXE) is syslinux (aka
>     pxelinux) or some other bootloader (grub) that can actually load an
>     operating system.
> 
> 
> Let me clarify this somewhat.
> 
> I said you don't _need_ iPXE except to use http instead of tftp.
> This isn't entirely true.  I have found that syslinux has some bugs in
> it, especially relating to loading very large images, and using iPXE
> seems to cover that up, as iPXE uses its own loader (with syslinux on
> top) that does a better job.  (But this only matters for booting memdisk
> with large ISOs, syslinux alone should be fine for just a kernel and an
> initrd.)
> 
> It is possible that iPXE similarly covers up UEFI problems with syslinux.
> I have booted UEFI machines using ipxe + syslinux, but not syslinux
> alone.  (Just haven't tried.)  Also, the bugs I am seeing might be in
> bios, rather than syslinux itself, as syslinux would probably be using
> the bios pxe/tftp code to do its loading, or alternately, it would use
> ipxe's http or tftp code, and syslinux really wouldn't know the difference.
> 
> 
> 

Ok thanks for the clarification. It looks to me likely at this point
that there are either issues with the BIOS PXE part or the grub/kernel
part and iPXE may fix it all. Right now I am travelling so I will be
testing this out next week, will post back to the list just for
completeness' sake.

-Erinn

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Erinn Looney-Triggs | 26 Jul 2012 18:53
Picon

Re: UEFI PXE boot

To continue on with this somewhat Red Hat support has now duplicated the
failure to PXE boot with UEFI enabled, on an R610 (in my testing r510
and r710 systems fail as well) and is working with Dell on a resolution
to the issue. No idea how long that will take.

-Erinn

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Spike_White | 26 Jul 2012 20:13
Picon
Favicon

RE: UEFI PXE boot

I'm not understanding how this is a bug in 11th gen servers.  Rather a limitation of that firmware's user interface.

PXE boot implies a BIOS boot.  I PXE-boot all the time at my house into CentOS, Ubuntu or OEL.  Using pxelinux
(with pxelinux.0 as my NBP).

Also, we have PXE boot set up in our labs for our server builds.  It's a more complicated back-end
infrastructure, but the same phases.  DHCP -> TFTP -> download NBP -> off to the races.

UEFI network boot is a different animal.    Luckily, UEFI network boots can re-use our existing DHCP/TFTP
infrastructure we've already set up.  But it's a totally different NBP and it's the boot client doing a UEFI
boot instead of a BIOS boot.  

Here's a good reference for re-using existing PXE infrastructure for a network UEFI boot:

    
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/s1-netboot-pxe-config-efi.html

So in this example, it's pxelinux/bootx64.efi that's the network boot program.  (Appears to be the
/install/images/efiboot.img out of the CentOS 6.2 DVD.)

On a 12th gen server (like a M620 or R620) you can go into boot manager (F11) and interactively select a UEFI
boot or a BIOS boot.  If you want PXE, you select BIOS boot.

On a 11th gen server (like a R710), F11 by default is the BIOS boot manager.  If you press F2 and go to Boot
settings, you can change the boot mode to UEFI.  Then if you reboot, F11 is the UEFI boot manager.  But then you
can't PXE boot (as PXE boot implies a BIOS boot).

Internally,  if attempting a UEFI network boot, a Dell 11g or 12g server sends this Vendor Class Identifier (VCI):

    PXEClient:ARCH:00007:UNDI:00301

If attempting a PXE boot, the client sends this VCI:

    PXEClient:Arch:00000:UNDI:002001

A smart DHCP server can key off that VCI and set up the DHCP option 67 (boot filename) appropriately.  As they
do in the example above.

Spike

Where 

> ------------------------------
> 
> Message: 2
> Date: Thu, 26 Jul 2012 08:53:39 -0800
> From: Erinn Looney-Triggs <erinn.looneytriggs <at> gmail.com>
> Subject: Re: UEFI PXE boot
> To: linux-poweredge <at> lists.us.dell.com
> Message-ID: <50117613.8000809 <at> gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> To continue on with this somewhat Red Hat support has now duplicated the
> failure to PXE boot with UEFI enabled, on an R610 (in my testing r510
> and r710 systems fail as well) and is working with Dell on a resolution
> to the issue. No idea how long that will take.
>
> -Erinn
Erinn Looney-Triggs | 26 Jul 2012 20:49
Picon

Re: UEFI PXE boot

On 07/26/2012 10:13 AM, Spike_White <at> Dell.com wrote:
> I'm not understanding how this is a bug in 11th gen servers.  Rather a limitation of that firmware's user interface.
> 
> PXE boot implies a BIOS boot.  I PXE-boot all the time at my house into CentOS, Ubuntu or OEL.  Using pxelinux
(with pxelinux.0 as my NBP).
> 
> Also, we have PXE boot set up in our labs for our server builds.  It's a more complicated back-end
infrastructure, but the same phases.  DHCP -> TFTP -> download NBP -> off to the races.
> 
> UEFI network boot is a different animal.    Luckily, UEFI network boots can re-use our existing DHCP/TFTP
infrastructure we've already set up.  But it's a totally different NBP and it's the boot client doing a UEFI
boot instead of a BIOS boot.  
> 
> Here's a good reference for re-using existing PXE infrastructure for a network UEFI boot:
> 
>     
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/s1-netboot-pxe-config-efi.html

> 
> So in this example, it's pxelinux/bootx64.efi that's the network boot program.  (Appears to be the
/install/images/efiboot.img out of the CentOS 6.2 DVD.)
> 
> On a 12th gen server (like a M620 or R620) you can go into boot manager (F11) and interactively select a UEFI
boot or a BIOS boot.  If you want PXE, you select BIOS boot.
> 
> On a 11th gen server (like a R710), F11 by default is the BIOS boot manager.  If you press F2 and go to Boot
settings, you can change the boot mode to UEFI.  Then if you reboot, F11 is the UEFI boot manager.  But then you
can't PXE boot (as PXE boot implies a BIOS boot).
> 
> Internally,  if attempting a UEFI network boot, a Dell 11g or 12g server sends this Vendor Class Identifier (VCI):
> 
>     PXEClient:ARCH:00007:UNDI:00301
> 
> If attempting a PXE boot, the client sends this VCI:
> 
>     PXEClient:Arch:00000:UNDI:002001
> 
> A smart DHCP server can key off that VCI and set up the DHCP option 67 (boot filename) appropriately.  As they
do in the example above.
> 
> Spike
> 
> 
> 
> Where 
> 
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 26 Jul 2012 08:53:39 -0800
>> From: Erinn Looney-Triggs <erinn.looneytriggs <at> gmail.com>
>> Subject: Re: UEFI PXE boot
>> To: linux-poweredge <at> lists.us.dell.com
>> Message-ID: <50117613.8000809 <at> gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> To continue on with this somewhat Red Hat support has now duplicated the
>> failure to PXE boot with UEFI enabled, on an R610 (in my testing r510
>> and r710 systems fail as well) and is working with Dell on a resolution
>> to the issue. No idea how long that will take.
>>
>> -Erinn
> 
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge <at> dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> 

Thanks for the explanation, I believe we are simply crossing at
terminology, which is my fault as UEFI boot in the very broad sense does
essentially the same thing as PXE boot, but this is a very simplistic
view and when I started this thread, honestly I didn't understand much
about, well, much.

So what is failing is a UEFI boot from RHEL 6.3. It may be hardware, it
may be software, it may be on Red Hat it may be on you folks where the
problem arises, however there is a problem in there, it simply doesn't
work.

I understand how to reuse the existing tftp/dhcp infrastructure to allow
UEFI booting, in fact I wrote a patch to cobbler that enables just this:
https://github.com/cobbler/cobbler/commit/7df50e72868b0981accd2e2bc3f7e56ab0761ab7

All that being said I don't understand the subtle nuances of how all
this comes together, and to be honest I might not have the energy to
track it all down. UEFI boot works, sort of, as I said in the original
message, though clearly I was getting the terminology wrong,
http://lists.us.dell.com/pipermail/linux-poweredge/2012-July/046617.html. Now
the system may well be beyond the point that the failure is anything but
Red Hats problem, as the UEFI boot has worked pulled in the NBP, loaded
it up and pulled in the vmlinuz and initrd, and it then fails to do,
well, anything.

Have you folks configured UEFI boot on the 12th generation servers to
work against RHEL (and I assume centos would be the same)? So far I
haven't been able to track down anyone who has it working unless they
are using i/gPXE as their NBP.

So apologies for screwing up the terminology, and thanks for setting me
on the right track with that, as I said I was pretty fresh to this at
the beginning.

Let me know if you have had success booting with UEFI using the grub
image and the normal chain on Dell 12th generation servers, if you
haven't tried, would you? If I am able to get more people to
confirm/deny this issue it would be great. As is all of my systems have
failed, I have tried grabbing different GRUB images, etc. all to no avail.

-Erinn

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Erinn Looney-Triggs | 26 Jul 2012 21:03
Picon

Re: UEFI PXE boot

On 07/26/2012 10:13 AM, Spike_White <at> Dell.com wrote:
> I'm not understanding how this is a bug in 11th gen servers.  Rather a limitation of that firmware's user interface.
> 
> PXE boot implies a BIOS boot.  I PXE-boot all the time at my house into CentOS, Ubuntu or OEL.  Using pxelinux
(with pxelinux.0 as my NBP).
> 
> Also, we have PXE boot set up in our labs for our server builds.  It's a more complicated back-end
infrastructure, but the same phases.  DHCP -> TFTP -> download NBP -> off to the races.
> 
> UEFI network boot is a different animal.    Luckily, UEFI network boots can re-use our existing DHCP/TFTP
infrastructure we've already set up.  But it's a totally different NBP and it's the boot client doing a UEFI
boot instead of a BIOS boot.  
> 
> Here's a good reference for re-using existing PXE infrastructure for a network UEFI boot:
> 
>     
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/s1-netboot-pxe-config-efi.html

> 
> So in this example, it's pxelinux/bootx64.efi that's the network boot program.  (Appears to be the
/install/images/efiboot.img out of the CentOS 6.2 DVD.)
> 
> On a 12th gen server (like a M620 or R620) you can go into boot manager (F11) and interactively select a UEFI
boot or a BIOS boot.  If you want PXE, you select BIOS boot.
> 
> On a 11th gen server (like a R710), F11 by default is the BIOS boot manager.  If you press F2 and go to Boot
settings, you can change the boot mode to UEFI.  Then if you reboot, F11 is the UEFI boot manager.  But then you
can't PXE boot (as PXE boot implies a BIOS boot).
> 
> Internally,  if attempting a UEFI network boot, a Dell 11g or 12g server sends this Vendor Class Identifier (VCI):
> 
>     PXEClient:ARCH:00007:UNDI:00301
> 
> If attempting a PXE boot, the client sends this VCI:
> 
>     PXEClient:Arch:00000:UNDI:002001
> 
> A smart DHCP server can key off that VCI and set up the DHCP option 67 (boot filename) appropriately.  As they
do in the example above.
> 
> Spike
> 
> 
> 
> Where 
> 
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 26 Jul 2012 08:53:39 -0800
>> From: Erinn Looney-Triggs <erinn.looneytriggs <at> gmail.com>
>> Subject: Re: UEFI PXE boot
>> To: linux-poweredge <at> lists.us.dell.com
>> Message-ID: <50117613.8000809 <at> gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> To continue on with this somewhat Red Hat support has now duplicated the
>> failure to PXE boot with UEFI enabled, on an R610 (in my testing r510
>> and r710 systems fail as well) and is working with Dell on a resolution
>> to the issue. No idea how long that will take.
>>
>> -Erinn
> 
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge <at> dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> 

And I apologize when I said if you could test on a 12th gen server I
meant 11th gen :). I don't have any 12th gen servers to test against at
this point.

-Erinn

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Spike_White | 26 Jul 2012 21:14
Picon
Favicon

RE: UEFI PXE boot

My team has not personally tested UEFI network boot yet -- I mentioned a "smart DHCP server can key off that
VCI ....".  Right now, (IMHO) a relatively dumb DHCP server is being used.  (*Not* dhcp3, I use it at my house
and it works great!).  

We have a call out now to our DHCP server vendor, how to have it send a different DHCP option 67 (boot filename)
based on boot client's VCI.  

But I'm guessing lots of these Dell PG guys on this mailing list have tested 12th gen servers doing UEFI net boots.

Spike

-----Original Message-----
From: Erinn Looney-Triggs [mailto:erinn.looneytriggs <at> gmail.com] 
Sent: Thursday, July 26, 2012 2:04 PM
To: White, Spike
Cc: linux-poweredge-Lists
Subject: Re: UEFI PXE boot

On 07/26/2012 10:13 AM, Spike_White <at> Dell.com wrote:
> I'm not understanding how this is a bug in 11th gen servers.  Rather a limitation of that firmware's user interface.
> 
> PXE boot implies a BIOS boot.  I PXE-boot all the time at my house into CentOS, Ubuntu or OEL.  Using pxelinux
(with pxelinux.0 as my NBP).
> 
> Also, we have PXE boot set up in our labs for our server builds.  It's a more complicated back-end
infrastructure, but the same phases.  DHCP -> TFTP -> download NBP -> off to the races.
> 
> UEFI network boot is a different animal.    Luckily, UEFI network boots can re-use our existing DHCP/TFTP
infrastructure we've already set up.  But it's a totally different NBP and it's the boot client doing a UEFI
boot instead of a BIOS boot.  
> 
> Here's a good reference for re-using existing PXE infrastructure for a network UEFI boot:
> 
>     
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/s1-netboot-pxe-config-efi.html

> 
> So in this example, it's pxelinux/bootx64.efi that's the network boot 
> program.  (Appears to be the /install/images/efiboot.img out of the 
> CentOS 6.2 DVD.)
> 
> On a 12th gen server (like a M620 or R620) you can go into boot manager (F11) and interactively select a UEFI
boot or a BIOS boot.  If you want PXE, you select BIOS boot.
> 
> On a 11th gen server (like a R710), F11 by default is the BIOS boot manager.  If you press F2 and go to Boot
settings, you can change the boot mode to UEFI.  Then if you reboot, F11 is the UEFI boot manager.  But then you
can't PXE boot (as PXE boot implies a BIOS boot).
> 
> Internally,  if attempting a UEFI network boot, a Dell 11g or 12g server sends this Vendor Class Identifier (VCI):
> 
>     PXEClient:ARCH:00007:UNDI:00301
> 
> If attempting a PXE boot, the client sends this VCI:
> 
>     PXEClient:Arch:00000:UNDI:002001
> 
> A smart DHCP server can key off that VCI and set up the DHCP option 67 (boot filename) appropriately.  As they
do in the example above.
> 
> Spike
> 
> 
> 
> Where
> 
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 26 Jul 2012 08:53:39 -0800
>> From: Erinn Looney-Triggs <erinn.looneytriggs <at> gmail.com>
>> Subject: Re: UEFI PXE boot
>> To: linux-poweredge <at> lists.us.dell.com
>> Message-ID: <50117613.8000809 <at> gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> To continue on with this somewhat Red Hat support has now duplicated 
>> the failure to PXE boot with UEFI enabled, on an R610 (in my testing 
>> r510 and r710 systems fail as well) and is working with Dell on a 
>> resolution to the issue. No idea how long that will take.
>>
>> -Erinn
> 
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge <at> dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> 

And I apologize when I said if you could test on a 12th gen server I meant 11th gen :). I don't have any 12th gen
servers to test against at this point.

-Erinn
Erinn Looney-Triggs | 26 Jul 2012 21:21
Picon

Re: UEFI PXE boot

On 07/26/2012 11:14 AM, Spike_White <at> Dell.com wrote:
> My team has not personally tested UEFI network boot yet -- I mentioned a "smart DHCP server can key off that
VCI ....".  Right now, (IMHO) a relatively dumb DHCP server is being used.  (*Not* dhcp3, I use it at my house
and it works great!).  
> 
> We have a call out now to our DHCP server vendor, how to have it send a different DHCP option 67 (boot
filename) based on boot client's VCI.  
> 
> But I'm guessing lots of these Dell PG guys on this mailing list have tested 12th gen servers doing UEFI net boots.
> 
> Spike
> 
> -----Original Message-----
> From: Erinn Looney-Triggs [mailto:erinn.looneytriggs <at> gmail.com] 
> Sent: Thursday, July 26, 2012 2:04 PM
> To: White, Spike
> Cc: linux-poweredge-Lists
> Subject: Re: UEFI PXE boot
> 
> On 07/26/2012 10:13 AM, Spike_White <at> Dell.com wrote:
>> I'm not understanding how this is a bug in 11th gen servers.  Rather a limitation of that firmware's user interface.
>>
>> PXE boot implies a BIOS boot.  I PXE-boot all the time at my house into CentOS, Ubuntu or OEL.  Using pxelinux
(with pxelinux.0 as my NBP).
>>
>> Also, we have PXE boot set up in our labs for our server builds.  It's a more complicated back-end
infrastructure, but the same phases.  DHCP -> TFTP -> download NBP -> off to the races.
>>
>> UEFI network boot is a different animal.    Luckily, UEFI network boots can re-use our existing DHCP/TFTP
infrastructure we've already set up.  But it's a totally different NBP and it's the boot client doing a UEFI
boot instead of a BIOS boot.  
>>
>> Here's a good reference for re-using existing PXE infrastructure for a network UEFI boot:
>>
>>     
http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/s1-netboot-pxe-config-efi.html

>>
>> So in this example, it's pxelinux/bootx64.efi that's the network boot 
>> program.  (Appears to be the /install/images/efiboot.img out of the 
>> CentOS 6.2 DVD.)
>>
>> On a 12th gen server (like a M620 or R620) you can go into boot manager (F11) and interactively select a UEFI
boot or a BIOS boot.  If you want PXE, you select BIOS boot.
>>
>> On a 11th gen server (like a R710), F11 by default is the BIOS boot manager.  If you press F2 and go to Boot
settings, you can change the boot mode to UEFI.  Then if you reboot, F11 is the UEFI boot manager.  But then you
can't PXE boot (as PXE boot implies a BIOS boot).
>>
>> Internally,  if attempting a UEFI network boot, a Dell 11g or 12g server sends this Vendor Class
Identifier (VCI):
>>
>>     PXEClient:ARCH:00007:UNDI:00301
>>
>> If attempting a PXE boot, the client sends this VCI:
>>
>>     PXEClient:Arch:00000:UNDI:002001
>>
>> A smart DHCP server can key off that VCI and set up the DHCP option 67 (boot filename) appropriately.  As
they do in the example above.
>>
>> Spike
>>
>>
>>
>> Where
>>
>>> ------------------------------
>>>
>>> Message: 2
>>> Date: Thu, 26 Jul 2012 08:53:39 -0800
>>> From: Erinn Looney-Triggs <erinn.looneytriggs <at> gmail.com>
>>> Subject: Re: UEFI PXE boot
>>> To: linux-poweredge <at> lists.us.dell.com
>>> Message-ID: <50117613.8000809 <at> gmail.com>
>>> Content-Type: text/plain; charset="iso-8859-1"
>>>
>>> To continue on with this somewhat Red Hat support has now duplicated 
>>> the failure to PXE boot with UEFI enabled, on an R610 (in my testing 
>>> r510 and r710 systems fail as well) and is working with Dell on a 
>>> resolution to the issue. No idea how long that will take.
>>>
>>> -Erinn
>>
>>
>> _______________________________________________
>> Linux-PowerEdge mailing list
>> Linux-PowerEdge <at> dell.com
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
> 
> And I apologize when I said if you could test on a 12th gen server I meant 11th gen :). I don't have any 12th gen
servers to test against at this point.
> 
> -Erinn
> 
> 

Well so far anyone who has it working has been pretty quiet :). Like I
said if you get a chance to try it out, give it a whirl, sounds like you
know a bit more about it than me, and perhaps you could have some
further insight.

-Erinn

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Gmane