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 1038542

Summary: win2012-R2 resuming from S4 will cause core dump after hot-plug and hot-unplug netkvm
Product: Red Hat Enterprise Linux 6 Reporter: Min Deng <mdeng>
Component: qemu-kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: acathrow, bcao, bsarathy, juzhang, michen, mkenneth, qzhang, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-05 22:16:35 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: 912287    
Attachments:
Description Flags
gdblog none

Description Min Deng 2013-12-05 10:06:53 UTC 
Description of problem:
Hot-unplug a virtio-nic and then do hibernate,resume the guest.But the guest will core dump 
Version-Release number of selected component (if applicable):
Guest - win2012R2 GUI Installation
qemu-kvm-rhev-0.12.1.2-2.415.el6.x86_64
build virtio-win-prewhql-74

How reproducible:
 5 times 

Steps to Reproduce:
1.boot up guest with the following CLI 
 [root@dhcp-8-141 home]# /usr/libexec/qemu-kvm -cpu host -enable-kvm -m 4G -smp 2 -name nerkvm -rtc base=localtime,clock=host,driftfix=slew -uuid `uuidgen` -vnc :3 -vga cirrus -monitor stdio -drive file=win2012-R2.raw,if=none,id=drive-data-disk2,format=raw,cache=writethrough,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-data-disk2,id=systemos -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device virtio-net-pci,netdev=hostnet0,id=net1
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) 
(qemu) 
(qemu) 
(qemu) netde
netdev_add  netdev_del  
(qemu) netdev_del hostnet0
(qemu) device
device_add  device_del  
(qemu) device_del net1
(qemu) 
(qemu) 
(qemu) info network
Devices not on any VLAN:
2.Execute "shutdown /h" in the guest 
3.Resume the guest 
  (qemu) [root@dhcp-8-141 home]# /usr/libexec/qemu-kvm -cpu host -enable-kvm -m 4G -smp 2 -name nerkvm -rtc base=localtime,clock=host,driftfix=slew -uuid `uuidnc :3 -vga cirrus -monitor stdio -drive file=win2012-R2.raw,if=none,id=drive-data-disk2,format=raw,cache=writethrough,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-data-disk2,id=systemos -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0

Actual results:
The guest resume failed due to qemu's core dump
(qemu) qemu: hardware error: register_ioport_write: invalid opaque
CPU #0:
RAX=0000000000000407 RBX=0000000000000002 RCX=ffffd000231ff454 RDX=0000000000000cfc
RSI=ffffd000231ff5e0 RDI=0000000000000004 RBP=ffffd000231ff454 RSP=ffffd000231ff3d8
R8 =0000000000000000 R9 =ffffd000231ff5e0 R10=0000000000000000 R11=ffffd000231ff3e0
R12=0000000000000002 R13=0000000000000001 R14=fffff80128064450 R15=00000006ab0a3601
RIP=fffff80128053d07 RFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA]
SS =0000 0000000000000000 ffffffff 00000000
DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
FS =0053 00000000b681e000 00003c00 0040f300 DPL=3 DS   [-WA]
GS =0000 fffff8012837f000 ffffffff 00000000
LDT=0000 0000000000000000 ffffffff 00000000
TR =0040 fffff8012b544080 00000067 00008b00 DPL=0 TSS64-busy
GDT=     fffff8012b543000 0000007f
IDT=     fffff8012b543080 00000fff
CR0=80050031 CR2=0000000000000000 CR3=00000000001a7000 CR4=000406f8
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
FCW=027f FSW=3800 [ST=7] FTW=80 MXCSR=00001f80
FPR0=9fc0000000000000 4008 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
XMM08=00000000000000000000000000000000 XMM09=00000000000000000000000000000000
XMM10=00000000000000000000000000000000 XMM11=00000000000000000000000000000000
XMM12=00000000000000000000000000000000 XMM13=00000000000000000000000000000000
XMM14=00000000000000000000000000000000 XMM15=00000000000000000000000000000000
CPU #1:
EAX=0001067a EBX=00000001 ECX=84282201 EDX=0f8bfbff
ESI=0000e020 EDI=00000000 EBP=00000000 ESP=00000000
EIP=000058a7 EFL=00010002 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=1
ES =0000 00000000 0000ffff 0000f300
CS =f000 000f0000 0000ffff 0000f300
SS =0000 00000000 0000ffff 0000f300
DS =f000 000f0000 0000ffff 0000f300
FS =0000 00000000 0000ffff 0000f300
GS =0000 00000000 0000ffff 0000f300
LDT=0000 00000000 0000ffff 00008200
TR =0000 feffd000 00002088 00008b00
GDT=     00000000 0000ffff
IDT=     00000000 0000ffff
CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000
DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000 
DR6=ffff0ff0 DR7=00000400
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
Aborted (core dumped)

Expected results:
The guest can resume successfully.

Additional info:
  Please get core* file from the ftp server as soon as possible because it's a temporarily server.*lftp 10.66.9.104*
Notes,
If don't hot-plug&unplug the issue could not be reproduced.
Comment 1 Min Deng 2013-12-05 11:35:28 UTC 
Created attachment 833109 [details]
gdblog
Comment 4 Ademar Reis 2014-06-05 22:16:35 UTC 
S3/S4 support is tech-preview in RHEL6 and it'll be promoted to fully supported
at some point, but only in RHEL7.

Therefore we're closing all S3/S4 related bugs in RHEL6. New bugs will be
considered only if they're regressions or break some important use-case or
certification.

RHEL7 is being more extensively tested and effort from QE is underway in
certifying that this particular bug is not present there.

Please reopen with a justification if you believe this bug should not be
closed. We'll consider them on a case-by-case basis following a best effort
approach.


Thank you.