Summary: | Windows 7 i386 BSOD with qxldd.dll | ||
---|---|---|---|
Product: | Spice | Reporter: | Joseph Callen <jcpowermac> |
Component: | win32 qxl xddm | Assignee: | Spice Bug List <spice-bugs> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | bugzilla, lucas.gary |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Windows (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
CrashDumpAnalysis
Machine.xml file FC14.xml file KDM log that might be related. |
Description
Joseph Callen
2010-10-13 09:32:51 UTC
Check how much memory is allocated to the video card of type qxl. The current virt-manager defaults to 9MB and cannot be changed from the virt-manager GUI. This needs to be at least 64MB for qxl drivers to work reliably as I found out by googling. You can go and change the .xml file for the VM to increase the memory and use virsh to define the vm again. virt-manager will then show the updated video memory and qxl becomes a lot more stable after that. This may or may not be related to your problem but worth checking. (In reply to comment #0) > Crash seems to occur more often when using Firefox, but will happen with no > applications running, just at idle. Using the Microsoft VGA driver has no > issues. I didn't know exactly what to provide if any more information is > needed please let me know. > Created attachment 47575 [details]
CrashDumpAnalysis
Crash dump analysis
Created attachment 47576 [details]
Machine.xml file
Created attachment 47577 [details]
FC14.xml file
I've been having similar issues with my VM's. My host is running FC15 stable. - 1st VM is running WinXP (crashdump attached). The driver QXL is definitly listed as the culprit. -- This is somewhat reproducible... Open firefox (3 on my system) find a long web page with lots of graphics and scroll up and down quickly... Eventually my VM will crash. 2nd VM is running FC14 -- Under similar circumstances the VM will log me out and kick me back to the login screen. It is almost completely random when this will occur. I haven't been able to track down anything meaningfull in the logs except this which may or may not be related: [ 194.694] Cache contents: null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null 560 865 357 454 510 555 973 1014 837 total: 9 [ 194.706] - 1th attempt [ 194.706] - OOM at 1033 849 32 [ 194.706] Cache contents: null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null 560 865 357 454 510 555 973 1014 837 total: 9 [ 194.717] - 2th attempt [ 194.717] - OOM at 1033 849 32 [ 194.717] Cache contents: null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null 560 865 357 454 510 555 973 1014 837 total: 9 [ 194.729] Out of video memory: Could not allocate 3512200 bytes [ 212.525] Bad bpp: 1 (1) [ 412.875] Bad bpp: 1 (1) This has never happened when not using the QXL driver / device... Both machine's XML's are included as attachments. I don't think it's the 9MB issue detailed below, or if it is then I don't know how to check how much ram the virtual video device has. Created attachment 47578 [details]
KDM log that might be related.
This excerpt from the guest FC14 installation seems to be issueing an out of memory error.
Can you please provide an update on this bug with current releases? thanks I'm closing this due inactivity: NEEDINFO since 2014-11-03 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.