Bug 854187 - The kdump didn't work on the Hyper-V RHEL5u9 guest
The kdump didn't work on the Hyper-V RHEL5u9 guest
Status: CLOSED CANTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
5.9
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Red Hat Kernel Manager
Virtualization Bugs
:
Depends On:
Blocks: 877921
  Show dependency treegraph
 
Reported: 2012-09-04 05:30 EDT by Bian Jinwei
Modified: 2012-11-19 04:09 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 877921 (view as bug list)
Environment:
Last Closed: 2012-09-04 07:07:00 EDT
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)
The_screenshot_of_the_error_info_with_kdump (144.76 KB, image/png)
2012-09-04 05:30 EDT, Bian Jinwei
no flags Details

  None (edit)
Description Bian Jinwei 2012-09-04 05:30:39 EDT
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

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