Bug 915765 – Kernel Panic when installing RHEVH 6.4 from PXE with vlan parameter

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 915765 - Kernel Panic when installing RHEVH 6.4 from PXE with vlan parameter

Summary:	Kernel Panic when installing RHEVH 6.4 from PXE with vlan parameter

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	ovirt-node (Show other bugs)
Sub Component:
Version:	6.4
Hardware:	x86_64 Linux

Priority	urgent Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Fabian Deutsch
QA Contact:	Martin Pavlik
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression, ZStream

Depends On:
Blocks:	927291
	Show dependency tree / graph

Reported:	2013-02-26 08:15 EST by Martin Pavlik
Modified:	2015-04-06 23:10 EDT (History)
CC List:	18 users (show)

See Also:
Fixed In Version:	ovirt-node-3.0.0-6.el6
Doc Type:	Bug Fix
Doc Text:	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.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-01-21 14:27:36 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
sosreport (449.89 KB, application/x-xz) 2013-02-26 08:15 EST, Martin Pavlik	no flags	Details
kernel_panic_video (10.17 MB, video/ogg) 2013-02-26 08:16 EST, Martin Pavlik	no flags	Details
ovirt.log (196.79 KB, text/plain) 2013-03-13 03:17 EDT, cshao	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2014:0033	normal	SHIPPED_LIVE	ovirt-node bug fix and enhancement update	2014-01-21 19:14:30 EST

Groups: None (edit)

Description Martin Pavlik 2013-02-26 08:15:21 EST

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

Comment 1 Martin Pavlik 2013-02-26 08:16:36 EST

Created attachment 702867 [details]
kernel_panic_video

Comment 6 Mike Burns 2013-03-07 06:34:00 EST

Joey, Can you look at this?

Thanks

Comment 14 cshao 2013-03-13 03:17:47 EDT

Created attachment 709363 [details]
ovirt.log

Comment 27 Martin Pavlik 2013-09-06 10:41:32 EDT

verified, with use of vlan=<vlanid>:<interface> in PXE line, RHEV-H 20130815.0.el6_4 installs properly

Comment 30 errata-xmlrpc 2014-01-21 14:27:36 EST

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

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