Bug 671221 - RHEV guest kernel panic when updating to 2.6.18-238 running on top of 2.6.18-238
Summary: RHEV guest kernel panic when updating to 2.6.18-238 running on top of 2.6.18-238
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.6
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-20 19:09 UTC by Dave Sullivan
Modified: 2013-01-09 23:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-15 21:10:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.