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 715222 - [qxl] Win2k3 guest got BSOD with "system_service_exception" error when live migrating during vm reboot
Summary: [qxl] Win2k3 guest got BSOD with "system_service_exception" error when live m...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-qxl-xddm
Version: ---
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Desktop QE
URL:
Whiteboard:
: 715198 (view as bug list)
Depends On: 1045114
Blocks: Rhel5KvmTier2
TreeView+ depends on / blocked
 
Reported: 2011-06-22 09:22 UTC by Qunfang Zhang
Modified: 2019-10-10 13:41 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-16 12:35:29 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot of BSOD (17.84 KB, image/png)
2011-06-22 09:22 UTC, Qunfang Zhang 		no flags Details
Dump file analysis (3.16 KB, text/plain)
2011-06-22 09:26 UTC, Qunfang Zhang 		no flags Details
View All

Description Qunfang Zhang 2011-06-22 09:22:26 UTC 
Created attachment 505951 [details]
Screenshot of BSOD

Description of problem:
Do migration during vm reboot, gust got BSOD with "system_service_exception" error.
Dump files will be attached.

Version-Release number of selected component (if applicable):
kernel-2.6.18-268.el5
kvm-83-238.el5

How reproducible:
Always

Steps to Reproduce:
1.Boot a guest in src host:

/usr/libexec/qemu-kvm -no-hpet -no-kvm-pit-reinjection -usbdevice tablet -rtc-td-hack -startdate now -name 2k3-64 -smp 4,cores=4 -k en-us -m 4096 -boot c -net nic,vlan=1,macaddr=00:1a:4a:42:17:01,model=virtio -net tap,vlan=1,script=/etc/qemu-ifup,script=/etc/qemu-ifup -drive file=/mnt/win2k3-64-virtio.raw,media=disk,if=virtio,cache=off,boot=on,format=raw,werror=stop -cpu qemu64,+sse2 -M rhel5.6.0 -notify all -balloon none -monitor stdio -spice host=0,ic=on,port=5910,disable-ticketing -qxl 1 -uuid 4c4fda5b-ef71-4455-8556-374e62b60a55

2.Boot guest with the same command line and add "-incoming tcp:0:5800" in des host.
3.Reboot guest
4.Migrate guest to dst host.
  
Actual results:
Guest always get a BSOD.

Expected results:
Guest should finish migration successfully without any error.

Additional info:
Comment 1 Qunfang Zhang 2011-06-22 09:26:10 UTC 
Created attachment 505952 [details]
Dump file analysis
Comment 3 Qunfang Zhang 2011-06-23 02:16:03 UTC 
This issue also happens when migrate with large RAM. Physical memory is 12G and guest memory is 8G. Migrate the vm between the 2 hosts.
Comment 5 Qunfang Zhang 2011-06-23 07:40:12 UTC 
There's no qxl component, please help change a suitable component. Thanks.
Comment 7 Dor Laor 2011-08-07 10:46:53 UTC 
*** Bug 715198 has been marked as a duplicate of this bug. ***
Comment 8 Marian Krcmarik 2011-11-29 18:36:47 UTC 
QXL component for Windows guest is located under RHEVM product. 

Moreover this happens only when using RHEL5 hosts and qspice -> used within RHEV2.2 and does *not* happen once using RHEL6 hosts and spice-server -> used within RHEV3 (the way how migration works was changed). 
It might be a problem with qspice+qxl driver combination.

I am moving to qxl component.
Comment 9 Marian Krcmarik 2011-11-30 19:04:50 UTC 
(In reply to comment #8)
> QXL component for Windows guest is located under RHEVM product. 
> 
> Moreover this happens only when using RHEL5 hosts and qspice
Scratch that, It seems to be different BSOD.
Comment 10 Alon Levy 2013-07-29 08:44:04 UTC 
Hi Qunfang Zhang,

This is an ancient bug not addressed, so I apologize for having to refresh your memory. Does this happen with RHEL 6 qemu / kernel ? does it happen with smaller smp and memory configuration? (reported smp 4, memory 4096 megabytes). The closed duplicate has a samba file copy while ping ponging, here it is reboot - the other bug doesn't have a crash dump, so I can't see if they are really related, and ideas why it was closed as duplicate (talking about bug 715918)?

If the need info should be from Marian (since he commented on this last) please let me know, or better yet change it to a need info from him,

Thanks,
Alon
Note You need to log in before you can comment on or make changes to this bug.