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 857001

Summary: sometimes shutdown guest cause guest Call Trace by command 'init 0' inside guest
Product: Red Hat Enterprise Linux 6 Reporter: FuXiangChun <xfu>
Component: qemu-kvmAssignee: Amos Kong <akong>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: acathrow, ailan, areis, bsarathy, chayang, dyasny, flang, juzhang, michen, mkenneth, qzhang, shu, sluo, virt-maint, wdai
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: 2012-10-09 00:14:43 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:
Attachments:
Description Flags
call trace from console none

Description FuXiangChun 2012-09-13 10:55:44 UTC 
Description of problem:
Boot a rhel6.4 guest with three nics(virtio e1000 and rtl8139),Sometimes Guest show call Trace when execute shutdown command 'init 0' inside guest.  I attached a Call Trace file.

host and physical info:

cpu:AMD Phenom(tm) 9600B Quad-Core Processor
# lspci |grep Ether*
3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit 

Ethernet PCI Express (rev 02)
Version-Release number of selected component (if applicable):
# uname -r
2.6.32

guest kernel:
2.6.32-303.el6.x86_64

# qemu-kvm -version
QEMU PC emulator version 0.12.1

How reproducible:
sometimes

Steps to Reproduce:
1.boot rhel6.4 guest with three nics
qemu-kvm -M rhel6.3.0 -cpu phenom -enable-kvm -m 2G -smp 2,sockets=2,cores=1,threads=1,maxcpus=6 -usb -device usb-tablet,id=input0 -name virt-nic -uuid 9ed5a909-5c33-4bc0-960c-29ecfc61a503 -drive file=rhel6.4-virt-nic-2.qcow2,format=qcow2,if=none,id=drive-disk,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,drive=drive-disk,id=virtio_image,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup,vhost=on -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=00:24:21:7F:93:11,bus=pci.0,addr=0x4 -netdev tap,id=hostnet1,script=/etc/qemu-ifup,vhost=off -device e1000,netdev=hostnet1,id=virtio-net-pci1,mac=00:24:21:7F:93:2F,bus=pci.0,addr=0x5 -netdev tap,id=hostnet2,script=/etc/qemu-ifup,vhost=off -device rtl8139,netdev=hostnet2,id=virtio-net-pci3,mac=00:24:21:7F:93:3E,bus=pci.0,addr=0x6 -vnc :3 -device sga -chardev socket,id=serial1,path=/var/test6,server,nowait -device isa-serial,chardev=serial1 -bios /usr/share/seabios/bios-pm.bin -boot menu=on -monitor stdio -qmp tcp:0:6666,server,nowait

2.shutdown guest inside guest
#init 0
3.get call Trace info from console in host
#nc -U  nc -U /var/test6
  
Actual results:
sometimes guest call trace

Expected results:
shutdown successfully

Additional info:
Comment 1 FuXiangChun 2012-09-13 10:57:09 UTC 
Created attachment 612404 [details]
call trace from console
Comment 4 Amos Kong 2012-10-01 02:06:11 UTC 
(In reply to comment #0)
> Description of problem:
> Boot a rhel6.4 guest with three nics(virtio e1000 and rtl8139),Sometimes
> Guest show call Trace when execute shutdown command 'init 0' inside guest. 
> I attached a Call Trace file.

Hi Xiangchun,

Can you help to test with non kvmclock?


> host and physical info:
> 
> cpu:AMD Phenom(tm) 9600B Quad-Core Processor
> # lspci |grep Ether*
> 3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit 
> 
> Ethernet PCI Express (rev 02)
> Version-Release number of selected component (if applicable):
> # uname -r
> 2.6.32

Is it a RHEL kernel? What's the output of '# uname -a', '# rpm -q kernel'

> guest kernel:
> 2.6.32-303.el6.x86_64

Please use latest kernel in brewweb in new test.

> # qemu-kvm -version
> QEMU PC emulator version 0.12.1

It's better to provide kvm version info by "# rpm -q qemu-kvm"

> How reproducible:
> sometimes

probability ?%
Comment 5 FuXiangChun 2012-10-08 10:36:51 UTC 
(In reply to comment #4)
> (In reply to comment #0)
> > Description of problem:
> > Boot a rhel6.4 guest with three nics(virtio e1000 and rtl8139),Sometimes
> > Guest show call Trace when execute shutdown command 'init 0' inside guest. 
> > I attached a Call Trace file.
> 
> Hi Xiangchun,
> 
> Can you help to test with non kvmclock?
> 
> 
> > host and physical info:
> > 
> > cpu:AMD Phenom(tm) 9600B Quad-Core Processor
> > # lspci |grep Ether*
> > 3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit 
> > 
> > Ethernet PCI Express (rev 02)
> > Version-Release number of selected component (if applicable):
> > # uname -r
> > 2.6.32
> 
> Is it a RHEL kernel? What's the output of '# uname -a', '# rpm -q kernel'
> 
> > guest kernel:
> > 2.6.32-303.el6.x86_64
> 
> Please use latest kernel in brewweb in new test.
> 
> > # qemu-kvm -version
> > QEMU PC emulator version 0.12.1
> 
> It's better to provide kvm version info by "# rpm -q qemu-kvm"
> 
> > How reproducible:
> > sometimes
> 
> probability ?%

If reinstall guest and update kernel with the latest kernel.  I cann't reproduce this bug. I am continuing to confirm this issue. Any testing results I will update to bz.
Comment 6 Amos Kong 2012-10-09 00:14:43 UTC 
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #0)
> > > Description of problem:
> > > Boot a rhel6.4 guest with three nics(virtio e1000 and rtl8139),Sometimes
> > > Guest show call Trace when execute shutdown command 'init 0' inside guest. 
> > > I attached a Call Trace file.
> > 
> > Hi Xiangchun,
> > 
> > Can you help to test with non kvmclock?
> > 
> > 
> > > host and physical info:
> > > 
> > > cpu:AMD Phenom(tm) 9600B Quad-Core Processor
> > > # lspci |grep Ether*
> > > 3f:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit 
> > > 
> > > Ethernet PCI Express (rev 02)
> > > Version-Release number of selected component (if applicable):
> > > # uname -r
> > > 2.6.32
> > 
> > Is it a RHEL kernel? What's the output of '# uname -a', '# rpm -q kernel'
> > 
> > > guest kernel:
> > > 2.6.32-303.el6.x86_64
> > 
> > Please use latest kernel in brewweb in new test.
> > 
> > > # qemu-kvm -version
> > > QEMU PC emulator version 0.12.1
> > 
> > It's better to provide kvm version info by "# rpm -q qemu-kvm"
> > 
> > > How reproducible:
> > > sometimes
> > 
> > probability ?%
> 
> If reinstall guest and update kernel with the latest kernel.  I cann't
> reproduce this bug. I am continuing to confirm this issue. Any testing
> results I will update to bz.

Close this bug as WORKSFORME, please re-open this bug if you can reproduce it.