Bug 170124 - RFE: add support for 'ksdevice=ethX' for PXE installs
RFE: add support for 'ksdevice=ethX' for PXE installs
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: system-config-netboot (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jaroslav Reznik
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-10-07 11:32 EDT by bastiaan
Modified: 2010-04-06 07:04 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-06 07:04:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description bastiaan 2005-10-07 11:32:57 EDT
Description of problem:
On systems with multiple network cards it may be necessary to specify which
network device kickstart should use for installs. Kickstart supports this with
kernel boot parameter 'ksdevice=ethX'. 
However redhat-config-netboot doesn't. As a workaround you could add this
parameter manually to the appropiate pxelinux.cfg, but redhat-confg-netboot will
overwrite this on the next update.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. create a PXE install profile with redhat-config-netboot
2. add ksdevice=ethX to pxelinux.cfg/default 
3. add or remove an PXE install profile with redhat-config-netboot
Actual results:
the ksdevice=ethX parameter is gone

Expected results:
the ksdevice=ethX parameter should still be there

Additional info:
Comment 1 Jason Vas Dias 2005-10-07 12:08:53 EDT
Some issues with incorrect removal of manually configured boot arguments 
were fixed with the latest system-config-netboot-0.1.33* release - 
see Bug 167762 and Bug 168415.

Please try out the latest system-config-netboot-0.1.33-1_EL4 release for RHEL-4,
available from:

Are you seeing the 'ksdevice=' setting being removed by the 0.1.33-1 version ?
If so, please let me know - this should not be happening with 0.1.33.

Perhaps for Network Install boot configurations, we should always set the 
ksdevice= parameter to the same value as we would set the ETHNERNET= parameter
for diskless clients, so that you can choose the interface used for booting
with the GUI both for network install and diskless configurations.
Comment 3 Jaroslav Reznik 2010-04-06 07:04:54 EDT
As there is now response from reporter, it was working for previous maintainer
and the bug is old, I'm closing this bug as NOTABUG.

Note You need to log in before you can comment on or make changes to this bug.