Bug 715222
| Summary: | [qxl] Win2k3 guest got BSOD with "system_service_exception" error when live migrating during vm reboot | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Qunfang Zhang <qzhang> | ||||||
| Component: | spice-qxl-xddm | Assignee: | Yvugenfi <yvugenfi> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | --- | CC: | cfergeau, dblechte, juzhang, knoel, marcandre.lureau, michen, mkenneth, mkrcmari, pvine, qzhang, rbalakri, tburke, 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-12-16 12:35:29 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1045114 | ||||||||
| Bug Blocks: | 580948 | ||||||||
| Attachments: |
|
||||||||
Created attachment 505952 [details]
Dump file analysis
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. There's no qxl component, please help change a suitable component. Thanks. *** Bug 715198 has been marked as a duplicate of this bug. *** 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. (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. 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 |
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: