Description of problem:
There is no way to pass network configuration to Anaconda through the kernel
command line when doing VNC network installation (kickstart is not used).
The perfectly valid FC6 kernel command line:
"vnc method=nfs:xxx:/home/src/F7 noipv6 ip=10.0.0.2 netmask=255.255.255.252
gateway=10.0.0.1 dns=10.0.0.1 lang=en_US keymap=us loglevel=debug"
does not start Anaconda VNC network installation in F7. The Anaconda loader
stops in the "Manual TCP/IP Configuration" dialog where the IP address field is
blank and has to be filled in on a local console.
The similar command line:
"text telnet method=nfs:xxx:/home/src/F7 noipv6 ip=10.0.0.2
netmask=255.255.255.252 gateway=10.0.0.1 dns=10.0.0.1 lang=en_US keymap=us
works without problems and a Telnet network installation (without using
kickstart) starts ok.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start VNC network installation with a command line like the one above
2. The Anaconda loader stops for manual TCP/IP configuration before starting a
VNC server although all necessary network settings are passed through the
kernel command line.
After manual network configuration on the local console the VNC server is
started and the installation procedes ok.
Start VNC server for graphical network installation without manual
configuration on the local console or kickstart configuration file.
Both VNC and Telnet network installations work in FC6 with similar kernel
command lines. VNC network installations are a convenient way for installing
for example Xen guests,
Created attachment 156564 [details]
Local console #3 debug log screenshots for Telnet and VNC network installations
This is related to bug #250895 and has been fixed in the Fedora development
tree. Thanks for the report.