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.
Previously, installing the hypervisor with the vlan parameter set to vlan=<vlanid> resulted in a kernel 'panic'. Setting the vlan boot parameter to the format of vlan=<vlanid>:<interface> can be validated within dracut, so the hypervisor installation succeeds.
Created attachment 702865[details]
sosreport
Description of problem:
When installing RHEVH from PXE (full PXE record in additional info) with vlan=172 parameter set, it ends up with kernel panic. See attached video.
If the same PXE record without vlan parameter is used instalation is successfull
Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Hypervisor release 6.4 (20130221.0.el6)
How reproducible:
100%
Steps to Reproduce:
1. install RHEVH from PXE with configutation from additional info section
Actual results:
kernel panic
Expected results:
successfull install
Additional info:
attached sosreport from successfull install (without vlan parameter) for details about machine used
PXE record causing kernel panic:
LABEL rhev-hypervisor6-6.4-20130221.0.el6-vlan
MENU LABEL rhev-hypervisor6-6.4-20130221.0.el6-^vlan
TEXT HELP
Added on 2013-02-22
ENDTEXT
KERNEL images/RHEVH/rhev-hypervisor6-6.4-20130221.0.el6/vmlinuz0
APPEND rootflags=loop initrd=images/RHEVH/rhev-hypervisor6-6.4-20130221.0.el6/initrd0.img root=live:/rhevh-latest-6.iso rootfstype=auto ro liveimg nomodeset check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline processor.max_cstate=1 rd_NO_LVM rd_NO_LUKS rd_NO_MD rd_NO_DM firstboot storage_init=/dev/sda storage_vol=::::: ssh_pwauth=1 adminpw=LMi16hIGAvm0A ntp=**REMOVED** edd=off rhevm_admin_password=gPA37ATxRODnA management_server=**REMOVED** vlan=172
IPAPPEND 2
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-0033.html
Created attachment 702865 [details] sosreport Description of problem: When installing RHEVH from PXE (full PXE record in additional info) with vlan=172 parameter set, it ends up with kernel panic. See attached video. If the same PXE record without vlan parameter is used instalation is successfull Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Hypervisor release 6.4 (20130221.0.el6) How reproducible: 100% Steps to Reproduce: 1. install RHEVH from PXE with configutation from additional info section Actual results: kernel panic Expected results: successfull install Additional info: attached sosreport from successfull install (without vlan parameter) for details about machine used PXE record causing kernel panic: LABEL rhev-hypervisor6-6.4-20130221.0.el6-vlan MENU LABEL rhev-hypervisor6-6.4-20130221.0.el6-^vlan TEXT HELP Added on 2013-02-22 ENDTEXT KERNEL images/RHEVH/rhev-hypervisor6-6.4-20130221.0.el6/vmlinuz0 APPEND rootflags=loop initrd=images/RHEVH/rhev-hypervisor6-6.4-20130221.0.el6/initrd0.img root=live:/rhevh-latest-6.iso rootfstype=auto ro liveimg nomodeset check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline processor.max_cstate=1 rd_NO_LVM rd_NO_LUKS rd_NO_MD rd_NO_DM firstboot storage_init=/dev/sda storage_vol=::::: ssh_pwauth=1 adminpw=LMi16hIGAvm0A ntp=**REMOVED** edd=off rhevm_admin_password=gPA37ATxRODnA management_server=**REMOVED** vlan=172 IPAPPEND 2