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.

Description of problem:
I install an application on the guest which is Windows 7 ultimate OS.After reboot, the guest sometimes BSOD, sometimes works well.


Version-Release number of selected component (if applicable):
Host:
Kernel:3.10.0-290.el7.x86_64
qemu-kvm-rhev:qemu-kvm-rhev-2.3.0-7.el7.x86_64

Guest:
OS:Windows 7 Ultimate


How reproducible:
50%


Steps to Reproduce:
1.
/usr/libexec/qemu-kvm -name win7 -S -machine  pc-i440fx-rhel7.2.0,accel=kvm,usb=off -cpu Haswell,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time -m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid 82b1a01e-5f6c-4f5f-8d27-3854a74e6b5b -drive file=/home/win7_64.qcow2,if=none,id=drive-virtio-blk-0,format=qcow2 -device virtio-blk-pci,drive=drive-virtio-blk-0,bootindex=1,id=virtio-blk01 -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5c:89:4d -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0 -spice port=5900,addr=0.0.0.0,disable-ticketing,image-compression=off,seamless-migration=on -monitor stdio

2.
reboot the guest.


Actual results:
BSOD

Expected results:
The guest works well.

Additional info:

Additional.

For fresh win7 x64 guest. Doesn't hit this issue.

What kind of application is it?

Hi Vadim Rozenfeld,

It is an application for monitoring.A computer can use it to control the other computers.

(In reply to zhangpei from comment #5)
> Hi Vadim Rozenfeld,
> 
> It is an application for monitoring.A computer can use it to control the
> other computers.

Can you take a snapshot from BSOD screen and add it to attachments?
Is the problem reproducible after switching to emulated (non-virtio) devices?
What is the application's name?

Thanks,
Vadim.

Can QE try reproducing this problem and upload the relevant crash dump file?

I tried with latest qemu, still hit this issue: after reboot, win7 guest will BSOD.

versions:
host:
3.10.0-456.el7.x86_64
qemu-kvm-rhev-2.6.0-11.el7.x86_64

(1) Relevant crash dump file
http://fileshare.englab.nay.redhat.com/pub/section2/coredump/var/crash/pezhang/bug1242395/Memory.dmp

(2) Win7 image with the monitor application installed:
1)zip file
http://fileshare.englab.nay.redhat.com/pub/section2/images_backup/rhel7/bug1242395/win7_64.qcow2.zip

# gzip -d win7_64.qcow2.zip --suffix=zip

2)normal file
http://fileshare.englab.nay.redhat.com/pub/section2/coredump/var/crash/pezhang/bug1242395/win7_64.qcow2

Thank you,
Pei

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.