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 923758 - [virtio-win][netkvm]Guest Win2012.64 and win8 BSOD during s4
Summary: [virtio-win][netkvm]Guest Win2012.64 and win8 BSOD during s4
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 947290 (view as bug list)
Depends On:
Blocks: Virt-S3/S4-7.0
TreeView+ depends on / blocked
 
Reported: 2013-03-20 11:53 UTC by lijin
Modified: 2013-11-06 10:03 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-06 10:03:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
the information after windbg the "memory.dump"file (17.37 KB, text/plain)
2013-03-20 11:53 UTC, lijin 		no flags Details
memory.dmp file (44.30 MB, application/zip)
2013-03-21 06:49 UTC, lijin 		no flags Details
View All

Description lijin 2013-03-20 11:53:11 UTC 
Created attachment 713195 [details]
the information after windbg the "memory.dump"file

Description of problem:
Do s4 in 2012.64 guest,guest BSOD with information:"SYSTEM_THREAD_EXCEPTION_NOT_HANDLED". 
I confirmed that on RHEL6.4(qemu-kvm:qemu-kvm-0.12.1.2-2.358.el6_4.bz909059.x86_64;kernel:kernel-2.6.32-358.el6.x86_64),with the same command and same virtio-win version(1.6.3-3),BSOD not happened on RHEL6.4

Version-Release number of selected component (if applicable):
RHEL-7.0-20130306.0
kernel:3.8.0-0.40.el7.x86_64
qemu-kvm:qemu-kvm-1.4.0-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.start a win7-32 guest with below command line:
/usr/libexec/qemu-kvm  \
-drive file=/home/acpi-test/acpi-test2.qcow2,if=none,media=disk,format=qcow2,id=drive-ide0-0-1 -device virtio-blk-pci,id=virtio-blk1,drive=drive-ide0-0-1,bootindex=0 \
-netdev tap,id=hostnet0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:7f:f9:F6,bus=pci.0 \
-device virtio-balloon-pci,bus=pci.0,addr=0x6,id=balloon0 \
-drive file=/home/acpi-test/test.qcow2,if=none,id=scsi0 -device virtio-scsi-pci,id=scsi0 -device scsi-hd,drive=scsi0 \
-monitor stdio  \
-spice port=5900,addr=10.66.5.201,disable-ticketing -vga qxl \
-usb \
-device usb-tablet,id=tablet1 \
-boot menu=on \
-chardev file,path=/root/console.log,id=serial1 \
-device isa-serial,chardev=serial1,id=s1 \
-M pc \
-smp 4,maxcpus=4,cores=2,threads=1,sockets=2 \
-m 4096 \
-enable-kvm \
-global PIIX4_PM.disable_s3=0 \
-global PIIX4_PM.disable_s4=0 \
-fdb /usr/share/virtio-win/virtio-win-1.6.3_x86.vfd \
-cdrom /tmp/winutils.iso

2.do s4 in guest

  
Actual results:
guest BSOD

Expected results:
guest s4 successfully

Additional info:
attached is the information after windbg the "memory.dump"file
Comment 2 lijin 2013-03-21 06:49:51 UTC 
Created attachment 713609 [details]
memory.dmp file
Comment 3 lijin 2013-03-21 10:16:34 UTC 
same BSOD happened on Win8.64 guest with the same virtio-win version:virtio-win-1.6.3-3.el6.noarch
the attachment:"memory.dmp file" is the win8 guest's dmp file
Comment 4 Hai Huang 2013-03-21 14:23:53 UTC 
Please reassign to the Windows team if appropriate. Thanks.
Comment 5 Sibiao Luo 2013-03-22 05:33:44 UTC 
hi Amit Shah,

   Does this issue the duplicate to the bug 920017 that related to the virtio-net ? please help check it, thx in advance.

Best Regards.
sluo
Comment 6 Amit Shah 2013-03-22 06:46:33 UTC 
(In reply to comment #5)
> hi Amit Shah,
> 
>    Does this issue the duplicate to the bug 920017 that related to the
> virtio-net ? please help check it, thx in advance.

No, it's not.  That's a RHEL guest bug, this is a Windows guest bug.
Comment 7 Mike Cao 2013-04-02 05:31:11 UTC 
Move to RHEL6 virtio-win component
Comment 8 Mike Cao 2013-04-02 05:31:57 UTC 
*** Bug 947290 has been marked as a duplicate of this bug. ***
Comment 10 huiqingding 2013-04-19 03:40:16 UTC 
On rhel7 host, boot win2008r2sp1 guest and do S4, also hits BSOD.

qemu-kvm version:
qemu-kvm-1.4.0-2.el7.x86_64
Kenrel version:
qemu-kvm-1.4.0-2.el7.x86_64

The command line is as following:

/usr/libexec/qemu-kvm -M q35 -cpu SandyBridge -enable-kvm -m 2048 -smp 4,sockets=2,cores=2,threads=1 -name rhel7 -rtc base=localtime,clock=host,driftfix=slew \
-device pci-bridge,bus=pcie.0,id=bridge1,chassis_nr=1,addr=0x3 \
-drive file=/home/win2008r2sp1.raw,if=none,id=drive-scsi0-disk0,format=raw,werror=stop,rerror=stop \
-device virtio-scsi-pci,id=scsi0,bus=bridge1,addr=0x6 \
-device scsi-hd,scsi-id=0,lun=0,bus=scsi0.0,drive=drive-scsi0-disk0,id=virtio-disk0,bootindex=1 \
-netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup \
-device virtio-net-pci,netdev=hostnet0,id=virtio-netpci0,mac=54:52:1b:35:2c:01,bus=bridge1,addr=0x7 \
-device virtio-balloon-pci,id=balloon0,bus=bridge1,addr=0x8 \
-vnc :10 -monitor stdio \
-device virtio-serial-pci,id=virtio-serial0,max_ports=3,bus=bridge1,addr=0x9 \
-chardev socket,id=channel0,path=/var/lib/libvirt/qemu/rhel6.channel0,server,nowait \
-device virtserialport,chardev=channel0,name=org.linux-kvm.port.0,bus=virtio-serial0.0,id=port1
Comment 11 Vadim Rozenfeld 2013-04-19 09:20:31 UTC 
(In reply to comment #10)
> On rhel7 host, boot win2008r2sp1 guest and do S4, also hits BSOD.
> 

Could you please upload the crash dump file?
Thank you,
Vadim.
Comment 12 huiqingding 2013-05-23 05:41:59 UTC 
(In reply to Vadim Rozenfeld from comment #11)
> (In reply to comment #10)
> > On rhel7 host, boot win2008r2sp1 guest and do S4, also hits BSOD.
> > 
> 
> Could you please upload the crash dump file?
> Thank you,
> Vadim.

Hello, Vadim,

Sorry for replying so late.

I do S4 on win2008r2sp1 guest, using following version:
kernel-3.9.0-0.55.el7.x86_64
qemu-kvm-1.4.0-4.el7.x86_64

Not BSOD. But guest is hang and command line cannot quit.

The command line is as following:
/usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm -m 2048 -smp 4,sockets=2,cores=2,threads=1 -name rhel7 -rtc base=localtime,clock=host,driftfix=slew -drive file=/dinghuiqing/win2008r1sp2.raw,if=none,id=drive-scsi0-disk0,format=raw,werror=stop,rerror=stop -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x6 -device scsi-hd,scsi-id=0,lun=0,bus=scsi0.0,drive=drive-scsi0-disk0,id=virtio-disk0,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-netpci0,mac=54:52:1b:35:2c:01,bus=pci.0,addr=0x7 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -vnc :10 -monitor stdio
Comment 13 Yvugenfi@redhat.com 2013-11-06 10:03:56 UTC 
According to the dump file - this crash should be solved by commit 5f65ea361e86f736a79d0279430d08128b369be7 that is found in RHEL6.5 release.
Note You need to log in before you can comment on or make changes to this bug.