I have the isc-dhcp-server configured with the foreman-proxy and omapi key.
If I try to boot ubuntu12 and ubuntu10, this two distros has its own
"pxelinux.0" file and it´s not compatible with the other. I want to know if
it exist a way to select that file manually. For example in a simple
standalone dhcpd server I´m able to use the parameter "filename
/pxelinux.0" in the configuration file but when the dhcpd server is
controlled via omapi this is the default behaviour when you create a host:
set statements = "next-server = c0:a8:02:7d; filename = "pxelinux.0";option host-name "nx.lan";"
So it assumes that the same "pxelinux.0" must be compatible with all the
operating systems.
I understand your question, but I can't see why it's necessary. Can you
provide any pointers to why PXELinux would be able to boot one OS and
not the other?
It should be able to boot pretty much anything - the difference between
distros and releases should be in the kernel and initrd used for the
installer, not the PXELinux bootloader.
···
On 02/01/13 09:44, F�lix Barbeira wrote:
> I have the isc-dhcp-server configured with the foreman-proxy and omapi
> key. If I try to boot ubuntu12 and ubuntu10, this two distros has its
> own "pxelinux.0" file and it�s not compatible with the other. I want to
> know if it exist a way to select that file manually. For example in a
> simple standalone dhcpd server I�m able to use the parameter "filename
> /pxelinux.0" in the configuration file but when the dhcpd server is
> controlled via omapi this is the default behaviour when you create a host:
>
> set statements = "next-server = c0:a8:02:7d; filename = \"pxelinux.0\";option host-name \"nx.lan\";"
>
> So it assumes that the same "pxelinux.0" must be compatible with all the
> operating systems.
–
Dominic Cleal
Red Hat Engineering
> I have the isc-dhcp-server configured with the foreman-proxy and omapi
> key. If I try to boot ubuntu12 and ubuntu10, this two distros has its own
> "pxelinux.0" file and it´s not compatible with the other. I want to know if
> it exist a way to select that file manually. For example in a simple
> standalone dhcpd server I´m able to use the parameter "filename
> /pxelinux.0" in the configuration file but when the dhcpd server is
> controlled via omapi this is the default behaviour when you create a host:
>
> set statements = "next-server = c0:a8:02:7d; filename = "pxelinux.0";option host-name "nx.lan";"
>
> So it assumes that the same "pxelinux.0" must be compatible with all the
> operating systems.
>
Until now, this was never a problem, at worst, a newer version of pxelinux
was usually fixing problems on older hw too.
Foreman has the ability to override the file name, but usually depends on
the os type, and not on the os version, however, if really required, we can
fix that.
can you elaborate more on what the real issue with pxelinux is?
thanks,
Ohad
···
On Wed, Jan 2, 2013 at 11:44 AM, Félix Barbeira wrote:
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/Z7Ba5Z0F-WkJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
You were right. It looks like the boot error was related to files
"vesamenu.c32" and "splash.png" because were different in ubuntu 12 and 10.
I replace the version 10 files with the 12 and now it works fine.
Thanks for your rapid answers and sorry for waste your time 
···
El miércoles, 2 de enero de 2013 10:51:34 UTC+1, Dominic Cleal escribió:
>
> On 02/01/13 09:44, F�lix Barbeira wrote:
> > I have the isc-dhcp-server configured with the foreman-proxy and omapi
> > key. If I try to boot ubuntu12 and ubuntu10, this two distros has its
> > own "pxelinux.0" file and it�s not compatible with the other. I want
> to
> > know if it exist a way to select that file manually. For example in a
> > simple standalone dhcpd server I�m able to use the parameter "filename
> > /pxelinux.0" in the configuration file but when the dhcpd server is
> > controlled via omapi this is the default behaviour when you create a
> host:
> >
> > set statements = "next-server = c0:a8:02:7d; filename =
> \"pxelinux.0\";option host-name \"nx.lan\";"
> >
> > So it assumes that the same "pxelinux.0" must be compatible with all the
> > operating systems.
>
> I understand your question, but I can't see why it's necessary. Can you
> provide any pointers to why PXELinux would be able to boot one OS and
> not the other?
>
> It should be able to boot pretty much anything - the difference between
> distros and releases should be in the kernel and initrd used for the
> installer, not the PXELinux bootloader.
>
> --
> Dominic Cleal
> Red Hat Engineering
>
> You were right. It looks like the boot error was related to files
> "vesamenu.c32" and "splash.png" because were different in ubuntu 12 and 10.
> I replace the version 10 files with the 12 and now it works fine.
>
> Thanks for your rapid answers and sorry for waste your time
>
no problems, if you are having further problems with pxelinux or second
stage tftp booting (e.g. fetching kernel etc), you can also use ipxe with
foreman as described here:
http://theforeman.org/projects/foreman/wiki/Fetch_boot_files_via_http_instead_of_TFTP
Ohad
···
On Wed, Jan 2, 2013 at 1:37 PM, Félix Barbeira wrote:
El miércoles, 2 de enero de 2013 10:51:34 UTC+1, Dominic Cleal escribió:
On 02/01/13 09:44, F�lix Barbeira wrote:
I have the isc-dhcp-server configured with the foreman-proxy and omapi
key. If I try to boot ubuntu12 and ubuntu10, this two distros has its
own “pxelinux.0” file and it�s not compatible with the other. I want
to
know if it exist a way to select that file manually. For example in a
simple standalone dhcpd server I�m able to use the parameter
"filename
/pxelinux.0" in the configuration file but when the dhcpd server is
controlled via omapi this is the default behaviour when you create a
host:
set statements = “next-server = c0:a8:02:7d; filename =
“pxelinux.0”;option host-name “nx.lan”;”
So it assumes that the same “pxelinux.0” must be compatible with all
the
operating systems.
I understand your question, but I can’t see why it’s necessary. Can you
provide any pointers to why PXELinux would be able to boot one OS and
not the other?
It should be able to boot pretty much anything - the difference between
distros and releases should be in the kernel and initrd used for the
installer, not the PXELinux bootloader.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/pTWpAFIA1JMJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
