Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 854187

Summary: The kdump didn't work on the Hyper-V RHEL5u9 guest
Product: Red Hat Enterprise Linux 5 Reporter: Bian Jinwei <jbian>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED CANTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.9CC: ccui, gbai, jasowang, jbian, leiwang, qguan, rhod, shwang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 877921 (view as bug list) Environment:
Last Closed: 2012-09-04 11:07:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 877921    
Attachments:
Description Flags
The_screenshot_of_the_error_info_with_kdump none

Description Bian Jinwei 2012-09-04 09:30:39 UTC 
Created attachment 609607 [details]
The_screenshot_of_the_error_info_with_kdump

Description of problem:
When you trigger the kernel panic on the Hyper-V guest(RHEL5.9 with kernel2.6.18-339el5),the kdump will not capture the kernel error info,only with the error message on the screen:the crashkernel fail to probe teh driver and it reports: hv_storvsc: probe of vmbus_0_2 failed with error -110

Version-Release number of selected component (if applicable):
version:
The Hyper-V:6.1.7600.16385
The Hyper-V guest:rhel5.9 kernel:2.6.18-339.el5(x86_64)

How reproducible:
100%

Steps to Reproduce:
1.Create a new virtual machine RHEL5u9 with kernel2.6.18-339el5 on Hyper-V,install the kexec-tools;

2.Set the target kernel with crashkernel setting below:
The setting target kernel with the option below(/etc/grub.conf,the crashkernel=128M@16M added):

3.reboot the guest,after reboot,then
#cat /proc/iomem | grep Crash\ kernel
with the similiar output "01000000-08ffffff : Crash kernel"to detect the crash kernel is working. and restart the kdump service with the command
#service kdump restart;

4.Trigger the kernel panic with the command below
#sync
#echo "1" > /proc/sys/kernel/sysrq
#echo "c" > /proc/sysrq-trigger
 
  
Actual results:

the kdump will not capture the kernel error info,only with the error message on the screen:the crashkernel fail to probe teh driver and it reports: hv_storvsc: probe of vmbus_0_2 failed with error -110,the screenshot has been attached


Expected results:

The kernel crash info will be stored into a location with the default path:/var/crash/`date`/.

Additional info:
the problem already mentioned in bug 824877:
https://bugzilla.redhat.com/show_bug.cgi?id=824877#c44
And also give the solution that it will be addressed in the next update of the hypervisor (hyper-V):
https://bugzilla.redhat.com/show_bug.cgi?id=824877#c52