Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 702290

Summary: Guest cannot reboot after doing kdump
Product: Red Hat Enterprise Linux 6 Reporter: Mike Cao <bcao>
Component: kernelAssignee: Gleb Natapov <gleb>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: bcao, ddutile, juzhang, knoel, michen, 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-06-15 14:06:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike Cao 2011-05-05 09:56:27 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
host info:
# uname -r
2.6.32-131.0.10.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.160.el6.x86_64

Guest info :
kernel2.6.18-259.el5

How reproducible:
sometimes 

Steps to Reproduce:
1.start RHEL5u7 x86_64 guest
CLI:
/usr/libexec/qemu-kvm -M rhel6.1.0 -enable-kvm -m 3G -smp 2,sockets=1,cores=2,threads=1 -name rhel5u6_64 -uuid c6b7e971-5550-4c6d-a47f-5fd95feea1a2 -rtc base=utc,clock=host,driftfix=slew -boot c -drive file=/home/virtio_serial/rhel5.7.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:0a:6a:69,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc :6 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -monitor stdio -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x8 -chardev socket,id=s1,path=/tmp/tt1,server,nowait -device virtserialport,chardev=s1,name=org.linux-kvm.port.0,bus=virtio-serial0.0,id=port0
2.echo c >/proc/sysrq-trigger

  
Actual results:
Guest could not generate crashdump,and will not reboot automately.

Expected results:
Guest generates crashdump,after that reboot automately.

Additional info:
1.kdump service is running
2.in the guest # cat /proc/cmdline 
ro root=/dev/VolGroup00/LogVol00 rhgb quiet crashkernel=128M@16M
Comment 1 Don Dutile (Red Hat) 2011-06-08 04:37:13 UTC 
Is this a valid kdump setup? 
does changing the setting to 256M@32M work?
Comment 2 Mike Cao 2011-06-08 06:34:54 UTC 
(In reply to comment #1)
> Is this a valid kdump setup? 
yes ,it is .

> does changing the setting to 256M@32M work?
still can reproduced .
As I said in comment #0 ,this issue does not 100% happened .

Additional info
re-tested on 
# uname -r
2.6.32-131.0.15.el6.x86_64
[root@dhcp-8-156 ~]# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.160.el6.x86_64
Comment 3 Gleb Natapov 2011-06-15 14:06:28 UTC 
Please check for existing bugs before opening new one.

*** This bug has been marked as a duplicate of bug 611407 ***