Bug 671221

Summary:	RHEV guest kernel panic when updating to 2.6.18-238 running on top of 2.6.18-238
Product:	Red Hat Enterprise Linux 5	Reporter:	Dave Sullivan <dsulliva>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	5.6	CC:	apevec, bburns, tburke
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-15 21:10:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dave Sullivan 2011-01-20 19:09:24 UTC

Description of problem:

RHEV guest kernel panic when updating to 2.6.18-238 (5.6) running on top of 2.6.18-238 (5.6)

When booting back to 2.6.18-194 everything is fine.

This environment is RHEV Hosts all 5.6 (2.6.18-238).

As soon as we upgrade the guest to 2.6.18-238 from 2.6.18-194 via satellite and reboot we run into the following error:

switchroot: mount failed: no such file or directory
kernle panic- not syncing: Attempted to kill init "


When we revert back to booting to 2.6.18-194 all is good.

So must be something wrong in kernel or virtio_blk module


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


How reproducible:

Should be self explanatory from above.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dave Sullivan 2011-02-15 21:10:15 UTC

This issue was being caused by an update to lvm.conf from our %post of our kickstart which was adding a filter for the thick host, when adding the same filter to the guests it was causing this issue.

So I'm closing this....Dave Sullivan

Comment 2 Dave Sullivan 2011-02-15 21:11:39 UTC

we accidently left the kickstart snippet in place for the guests, user error