Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 726073

Summary: ksdevice=bootif does not work in virsh install
Product: Red Hat Enterprise Linux 6 Reporter: Adam Okuliar <aokuliar>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: rvykydal
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-24 12:36:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda.log
none
syslog none

Description Adam Okuliar 2011-07-27 13:09:47 UTC 
Description of problem:
ksdevice=bootif does not work in virsh install

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

How reproducible:
100%

Steps to Reproduce:
1. install virtual machine with multiple bridged network interfaces. Specify ksdevice=bootif as kernel parameter. 

virt-install -n rhel --vnc --vcpus=2 -r 2048  \
-f /var/lib/libvirt/images/rhel.img -s 10 \
--network bridge:br-rhts --network bridge:br-igb --network bridge:br-netxen --network bridge:br-ixgbe \
--os-type=linux --os-variant=virtio26  --accelerate \
--location http://download.englab.brq.redhat.com/pub/rhel/released/RHEL-6/6.1/Server/x86_64/os/ --noautoconsole  \
-x "ksdevice=bootif ks=http://download.englab.brq.redhat.com/perf-results/ks.cfg text console=tty0 utf8 console=ttyS0,115200"; 

2. virsh console rhel

  
Actual results:
Even if ksdevice=bootif were passed as parameter installation still prompts me to select installation device:

┌───────────────┤ Networking Device ├───────────────┐
│                                                   │
│ You have multiple network devices on this system. │
│ Which would you like to install through?          │
│                                                   │
│  eth0 - Ethernet device eth0 - 52:54:00:d2:c5:68  │
│  eth1 - Ethernet device eth1 - 52:54:00:1b:89:b7  │
│  eth2 - Ethernet device eth2 - 52:54:00:bd:e8:b9  │
│  eth3 - Ethernet device eth3 - 52:54:00:98:fc:cf  │
│                                                   │
│    ┌────┐        ┌──────────┐        ┌──────┐     │
│    │ OK │        │ Identify │        │ Back │     │
│    └────┘        └──────────┘        └──────┘     │
│                                                   │
│                                                   │
└───────────────────────────────────────────────────┘


Expected results:
Correct installation from boot interface without prompting
Comment 2 Chris Lumens 2011-07-27 14:22:21 UTC 
Does virt-install cause a BOOTIF= parameter to be added to the kernel command line?  You can check /proc/cmdline to find out.
Comment 3 Adam Okuliar 2011-07-27 14:29:27 UTC 
I'm sure that bootif parameter is correctly passed to kernel, because bootif=eth0 works correctly.

Thanks,
Adam
Comment 4 Chris Lumens 2011-07-27 15:32:20 UTC 
Can you attach /tmp/anaconda.log and /tmp/syslog to this bug report?
Comment 5 Adam Okuliar 2011-10-24 12:18:00 UTC 
Created attachment 529849 [details]
anaconda.log
Comment 6 Adam Okuliar 2011-10-24 12:18:39 UTC 
Created attachment 529850 [details]
syslog
Comment 7 Adam Okuliar 2011-10-24 12:20:20 UTC 
$grep '' /proc/cmdline

method=http://download.englab.brq.redhat.com/pub/rhel/released/RHEL-6/6.1/Server/x86_64/os/ ksdevice=bootif ks=http://download.englab.brq.redhat.com/perf-results/ks.cfg text console=tty0 utf8 console=ttyS0,115200
Comment 8 Radek Vykydal 2011-10-24 12:36:27 UTC 
You are not providing BOOTIF= value among boot options:

12:11:10,560 INFO    : kernel command line: method=http://download.englab.brq.redhat.com/pub/rhel/released/RHEL-6/6.1/Server/x86_64/os/ ksdevice=bootif ks=http://download.englab.brq.redhat.com/perf-results/ks.cfg text console=tty0 utf8 console=ttyS0,115200

See http://fedoraproject.org/wiki/Anaconda_Boot_Options#ksdevice.