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 1162470

Summary: do “systerm_reset” when guest booting for more than 20 times,and the guest system hang with BSOD
Product: Red Hat Enterprise Linux 7 Reporter: xiagao
Component: qemu-kvm-rhevAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.1CC: hhuang, huding, juzhang, knoel, mtosatti, virt-maint, xfu
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: 2015-07-21 21:32:30 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
BSOD none

Description xiagao 2014-11-11 07:00:19 UTC
Created attachment 956122 [details]
BSOD

Description of problem:
do “systerm_reset” when guest booting  more than 20 times,and when prompting “Lauch Startup Repair(recommended)” and “Start Windows Normally”,selecte the second option,the guest will hang with BSOD. 

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.1.2-5.el7.x86_64

How reproducible:
sometimes

Steps to Reproduce:
1.boot up a guest with 7 disks
2.reboot guest and do system_reset during guest rebooting for more than 20 times.
# (qmp)  {"execute": "qmp_capabilities"}
         { "execute": "system_reset" }

Actual results:
guest hang with BSOD before system bootup.
error info with “stop:0x0000005C (0X0000010B,0x00000001,0x00000000,0x00000000)”

Expected results:

Additional info
1.Because guest hanged before system bootup, can't collect dump information.
2.Guest: Win7-32
3.host cpuinfo:
processor	: 15
vendor_id	: GenuineIntel
cpu family	: 6
model		: 62
model name	: Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
stepping	: 4
4.host kernel: 3.10.0-196.el7.x86_64
5.virtio-win:  virtio-win-prewhql-0.1-93
6.no BSOD with 3 disks
7.CLI:
/usr/libexec/qemu-kvm \
-name 'virt-tests-vm1' \
-sandbox off  -M pc-i440fx-rhel7.1.0  -m 8G \
-smp 8,sockets=2,cores=2,threads=2 \
-cpu SandyBridge,check,enforce  -S \
-nodefaults -boot menu=on \
-device nec-usb-xhci,id=usb0,bus=pci.0,addr=0x5 \
-device usb-tablet,id=tablet1,bus=usb0.0,port=1 \
-no-shutdown -enable-kvm \
-chardev socket,id=serial_xiagao,path=/tmp/xiagao,server,nowait \
-device isa-serial,chardev=serial_xiagao \
-device virtio-scsi-pci,bus=pci.0,addr=0x4,id=scsi0 \
-drive file=/home/v1/img/win7-32-sp1-32-virtio1-new.qcow2,if=none,id=drive-scsi0-0-0,media=disk,format=qcow2,aio=native,cache=none \
-device scsi-hd,bus=scsi0.0,scsi-id=0,lun=0,drive=drive-scsi0-0-0,id=scsi-disk0 \
-drive file="/home/v1/img/virtio-win-prewhql-0.1-93.iso",if=none,id=cdrom1,media=cdrom,cache=none,readonly=on \
-device ide-drive,id=ide-cd2,drive=cdrom1 \
-drive file="/home/v1/img/en_windows_7_ultimate_with_sp1_x86_dvd_u_677460.iso",if=none,media=cdrom,readonly=on,format=raw,id=cdrom2 \
-device scsi-cd,bus=scsi0.0,scsi-id=0,lun=1,drive=cdrom2,id=scsi-cd0 \
-netdev tap,id=hostnet0,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:ae:a4:95 \
-vga cirrus \
-vnc :0 \
-boot menu=on \
-monitor stdio \
-qmp tcp:0:1234,server,nowait \
-drive file="/home/v1/img/disk-10g.qcow2",if=none,id=drive-scsi0-0-1,media=disk,format=qcow2,aio=threads,cache=none,werror=stop,rerror=stop \
-device scsi-hd,bus=scsi0.0,scsi-id=0,lun=4,drive=drive-scsi0-0-1,id=scsi-disk1 \
-drive file="/home/v1/img/disk-5g.qcow2",if=none,id=drive-scsi0-0-2,media=disk,format=qcow2,aio=native,cache=none,werror=stop,rerror=stop \
-device scsi-hd,bus=scsi0.0,scsi-id=0,lun=5,drive=drive-scsi0-0-2,id=scsi-disk2 \
-drive file="/home/v1/img/disk-5g.raw",if=none,id=drive-scsi0-0-3,media=disk,format=raw,aio=native,cache=none,werror=stop,rerror=stop \
-device scsi-hd,bus=scsi0.0,scsi-id=0,lun=6,drive=drive-scsi0-0-3,id=scsi-disk3 \
-drive file="iscsi://10.66.9.23:3260/iqn.2014-10.com.xiagao:server.target0/2",if=none,id=drive-scsi0-0-4,media=disk,format=raw,aio=native,cache=none,werror=stop,rerror=stop \
-iscsi id=iqn \
-device scsi-hd,bus=scsi0.0,scsi-id=0,lun=7,drive=drive-scsi0-0-4,id=scsi-disk4 \

Comment 2 Vadim Rozenfeld 2014-11-25 06:54:30 UTC
Please try reproducing with drivers from build 94 (build 93 has some regression
in crash dump stack).

Thanks,
Vadim.

Comment 5 Marcelo Tosatti 2015-07-21 21:32:30 UTC

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