QA:Testcase biosdevname Automated Kickstart Installation

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(How To Test)
(How To Test)
Line 11: Line 11:
 
<lo>
 
<lo>
 
<li> Start the Rawhide instllation by booting into the {{filename|boot.iso}} from <here>
 
<li> Start the Rawhide instllation by booting into the {{filename|boot.iso}} from <here>
<li> In the welcome screen, press TAB to edit the grub command line and append '''ksdevice=em1''' '''ks=ks.cfg location on network'''. More information on ''ks and ksdevice'' can be found [http://fedoraproject.org/wiki/Anaconda/Kickstart#Other_kickstart_options: here]. More information on creating a ks.cfg can be found [http://fedoraproject.org/wiki/Anaconda/Kickstart#Creating_the_Kickstart_File here]
+
<li> In the welcome screen, press TAB to edit the grub command line and append '''ksdevice=em1''' '''ks=ks.cfg location on network'''. More information on ''ks and ksdevice'' options can be found [http://fedoraproject.org/wiki/Anaconda/Kickstart#Other_kickstart_options: here]. More information on creating a ks.cfg can be found [http://fedoraproject.org/wiki/Anaconda/Kickstart#Creating_the_Kickstart_File here]
 +
</lo>
  
 
== Results ==
 
== Results ==

Revision as of 16:18, 24 January 2011

Contents

Description

This test scenario make sure that ksdevice=<interface name> format will handle interface names of the form emN or pci<slot>#<port>. For example passing 'ksdevice=em1' will work without issues.

Setup

Make sure hardware requirements are met.

How To Test

<lo>

  • Start the Rawhide instllation by booting into the boot.iso from <here>
  • In the welcome screen, press TAB to edit the grub command line and append ksdevice=em1 ks=ks.cfg location on network. More information on ks and ksdevice options can be found here. More information on creating a ks.cfg can be found here </lo>

    Results