Bug 726073 - ksdevice=bootif does not work in virsh install
Summary: ksdevice=bootif does not work in virsh install
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-27 13:09 UTC by Adam Okuliar
Modified: 2011-10-24 12:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-24 12:36:27 UTC
Target Upstream Version:


Attachments (Terms of Use)
anaconda.log (1.81 KB, text/plain)
2011-10-24 12:18 UTC, Adam Okuliar
no flags Details
syslog (36.34 KB, text/plain)
2011-10-24 12:18 UTC, Adam Okuliar
no flags Details

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.


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