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 786652 - Guest get calltrace and failed to boot up after several times iofuzz testing
Summary: Guest get calltrace and failed to boot up after several times iofuzz testing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Paolo Bonzini
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-02 03:06 UTC by Qunfang Zhang
Modified: 2013-01-10 00:42 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-13 15:11:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
autotest log (138.23 KB, application/octet-stream)
2012-02-02 03:08 UTC, Qunfang Zhang 		no flags Details
Serial log of the guest (31.07 KB, application/octet-stream)
2012-02-02 03:08 UTC, Qunfang Zhang 		no flags Details
View All

Description Qunfang Zhang 2012-02-02 03:06:52 UTC 
Description of problem:
Running iofuzz testing on RHEL5.8 guest and repeat several times, after 3 or 4 rounds later, guest image can not boot up and get a call trace. Attachment will be upload.

Version-Release number of selected component (if applicable):
kernel-2.6.32-220.el6.x86_64
qemu-kvm-0.12.1.2-2.222.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run iofuzz testing on RHEL6.3 host, I tested rhel5.7 and 5.8 guest, got the same result.
2.

CLI:
/home/staf-kvm-devel/autotest-devel/client/tests/kvm/qemu -name vm1 -chardev
socket,id=qmp_monitor_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20120201-143600-63Pq,server,nowait
-mon chardev=qmp_monitor_id_qmpmonitor1,mode=control -chardev
socket,id=serial_id_20120201-143600-63Pq,path=/tmp/serial-20120201-143600-63Pq,server,nowait
-device isa-serial,chardev=serial_id_20120201-143600-63Pq -device
ich9-usb-uhci1,id=usb1,bus=pci.0,addr=0x4 -drive
file=/home/staf-kvm-devel/autotest-devel/client/tests/kvm/images/RHEL-Server-5.7-64.qcow2,index=0,if=none,id=drive-ide0-0-0,media=disk,cache=none,format=qcow2,aio=native
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device
e1000,netdev=idxEvOi8,mac=9a:ad:28:4b:eb:ea,id=ndev00idxEvOi8,bus=pci.0,addr=0x3
-netdev tap,id=idxEvOi8,fd=19 -m 512 -smp 1,cores=1,threads=1,sockets=1 -cpu
cpu64-rhel6,+sse2,+x2apic -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1
-vnc :0 -rtc base=utc,clock=host,driftfix=slew -M rhel6.2.0 -boot
order=cdn,once=c,menu=off -no-kvm-pit-reinjection -enable-kvm

  
Actual results:
Guest got call trace and  failed to boot up after 3 or 4 rounds of iofuzz testing.

Expected results:
Guest could boot up.

Additional info:
Comment 1 Qunfang Zhang 2012-02-02 03:08:06 UTC 
Created attachment 558959 [details]
autotest log
Comment 2 Qunfang Zhang 2012-02-02 03:08:31 UTC 
Created attachment 558960 [details]
Serial log of the guest
Comment 4 Paolo Bonzini 2012-02-15 09:58:07 UTC 
I think this is not a problem; iofuzz is mostly a QEMU test and can destabilize the guest hardware (which leads to crashes).  Unless QEMU core dumps, as in bug 751937 for example, I think there is no problem.

That said, getting the output of the gdb command "thread apply bt full" on the QEMU process can help.
Comment 5 Paolo Bonzini 2012-02-15 09:58:57 UTC 
Closed by mistake, setting NEEDINFO for Qunfang
Comment 6 Qunfang Zhang 2012-02-16 10:20:24 UTC 
Hi, Paolo
I meet this issue during iofuzz autotest. Now the job is running and I will provide the bt log after it get the calltrace point.

So, this issue is most likely not a bug?
Note You need to log in before you can comment on or make changes to this bug.