|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough
Hi and thank you both for your input. >From what I can tell, the things you mentioned are pretty similar to what i wrote in my summary in the initial mail. But it's interesting that you both got different cards running with CCC. So the CCC might be an actual issue of either vga- and mainboard combo or vendor specific. May I ask what setup's you got, especially the vendors / exact models of your HD6870. ? For the well-known fix for the atikmpaq.sys BSOD, at least in my opinion you can ignore all the solutions posted which are not xen related. I think the BSOD here is clearly xen related since at least for my it only happens with the xl toolstack and not the xm one, with the same domU. But if someone really got lucky with such a non-xen fix, it would be interesting to see, too.. Last but not least, can you say something about your setup? I would be especially curious about if you do some vga bios stuff, like extracting and including it into the xen build, and what kernel and domU parameters you use, for example if iommu=1 or iomu=soft @ kernel and stuff like pci_msitranslate=1 and pci_powermanagement in domU config (and if the viridian=1 option does actually do anything).. There are a lot of vga passthrough tutorials lately, but from what it's worth, in my opinion they all lack some detail because everyone simply describes the setup he got working and there is no comprehensive summary about the benefits of the different options. It would be great if you can help with your experience. 2013/2/7 Casey DeLorme <cdelorme@xxxxxxxxx>: > I have an HD 6870 and working CCC, tested on both Windows 7 and windows 8. > Don't have any BSoD's either. > > I only had problems with CCC and drivers when I attempted to install or > update drivers without having freshly rebooted or ejected the card. > > Unfortunately Windows 8 attempts to auto-install the drivers at boot time > and this caused some headaches during my first go at it. > > I experience performance problems after rebooting the HVM, to fix it I just > eject the card from the "Safely Remove Hardware and Eject Media" icon. > > > On Thu, Feb 7, 2013 at 4:56 PM, David TECHER <davidtecher@xxxxxxxx> wrote: >> >> Issues for CCC depends on your Video Card too. >> >> - Got a HD 79070. It worked for me to add CCC while installing the 13.2 >> beta driver. >> >> Unfortunately there was BSOD issue when rebooting the domU. >> >> I had to install .NET 4 Framework and CCC now works as expected :) >> >> - CCC is not supposed to work for HD 6870 but it worked for HD 7970. >> >> FYI to fix atikmap.sys issue there is a well-known workaround with >> something like >> >> >> http://www.computertipsfree.com/fix-43029-atikmdag-sys-blue-screen-bsod-in-windows-7/ >> >> expand -r atikmdag.sy_ atikmdag.sys >> >> But it doesn't work for me :( >> >> The good news is that I've just installed Crysis 3 beta demo. It works >> like a charm! >> >> >> ________________________________ >> De : Matthias <matthias.kannenberg@xxxxxxxxxxxxxx> >> À : xen-users@xxxxxxxxxxxxx >> Envoyé le : Jeudi 7 février 2013 20h14 >> Objet : [Xen-users] ATI/AMDs atikmpag.sys BSOD while vga passthrough >> >> Hi everyone >> >> since I'm currently migrating from xm to xl and now are also a victim >> of the said error, I started researching on it and found that many >> people had the issue but not many found solution and behind this BSOD >> (=Bluescreen of Death), there are actually multiple errors in hiding. >> >> What I would like to do is gather as much info as possible in this >> thread to form a kind of comprehensive guide to fixing this issue. >> >> From what i gathered so far, there are at least 3 different problems >> with the same symptopms. >> >> 1) >> Situation: After booting the dom0 and booting a windows domU with an >> ATI/AMD Card, Windows generally works fine, but after rebooting the >> system, or shutting down / restarting, the Bluescreen occurs or the >> performance massively below normal. >> Error: Most likely this is cause the Card is not properly resetted (no >> FLR [function level reset] ) >> Solution: If the domU reboots into BSOD, you are screwed and have to >> reboot the dom0. If it only degrades performance, eject the card and >> reinitialize to perform a manual reset. Or use the xm toolkit. >> Status: Don't know if it is fixed yet >> Source: http://lists.xen.org/archives/html/xen-users/2012-02/msg00443.html >> , http://wiki.xen.org/wiki/Talk:Xen_VGA_Passthrough_Tested_Adapters >> >> 2) >> Situation: Booting a windows domU results in a BSOD when the CCC >> (=Catalyst Control Center) installed. >> Error: The CCC tries to set some specific settings (most likely >> performance tweaks) within the driver which the driver can't pass to >> the vga through passthrough mode. Result is a BSOD. >> Solution: Deinstall the CCC in windows safe mode. The driver itself >> works without it pretty fine. >> Status: Don't know if it is fixed yet >> Source: http://lists.xen.org/archives/html/xen-users/2012-03/msg00617.html >> Note: I don't really know if this holds for the Vision Engine Control >> center, too. the VECC is basically the same as the CCC, so i assume it >> does. I simply haven't found any things referencing it. >> >> 3) >> Situation: This is actually the issue I have. Things seem a lot more >> random then the other ones. A BSOD happens basically in 80% of booting >> the Windows domU. Which means, after rebooting dom0, it mostly works. >> Rebooting or shutting down / starting the domU works sometimes (Once i >> achieved 6 consecutive reboots or shutdowns / starts before the BSOD >> happened) but after I get one Bluescreen, almost never (I can't >> exactly remember if really 'never') comes up again. Of course I tried >> the above solutions but this didn't helped me. I also tried different >> different versions of the Catalyst driver (from 12/1 to 13/1) and >> current releases of xen-4.2-testing and xen-unsable. As I said, this >> is when using the xl toolkit. I never had this issues using xm. >> I thought this might belinked to me passing other PCI devices in >> addition (I'm passing some USB controller to the domU) but even >> deactivating them didn't help. What I actually found helping boosting >> the success rate (but not solving the overall issue) is deinstalling >> all VGA-Related AMD Driver. Windows then runs on it's own VGA-Driver >> (the graphic card is currectly identified and this is an actual ati >> driver, so I'm not talking about some generic standard vga driver. I >> don't know where is driver is coming from). >> I've attached an analysis file i've gethered from the bluescreen crash >> dump. I created it using BluescreenView. This is more for currectly >> identifieng the different BSODs, I guess. >> >> >> Some Infos: >> Kernel: 3.7.4 kernel.org kernel without patches >> Xen: latest xen-unstable (but also tested with xen-4.2-testing) >> Processor: AMD Phenom 1090T >> Mainboard: Asus Crossfire IV >> VGA: Radeon HD5700 and Radeon HD5450 >> Driver: Currently running Catalyst 13/1 but tested nearly everything >> between 12/1 and 13/1 >> >> Error: Don't know yet >> Solution: Don't know yet >> Status: unsolved >> Source: >> >> >> Okay, so basically that's the story. It would be great if some people >> can complete and extend the list. Especially some who already fixed >> the issue on their side. (And of course it would be great if someone >> has an idea for my problem). >> >> Thanks >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@xxxxxxxxxxxxx >> http://lists.xen.org/xen-users >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@xxxxxxxxxxxxx >> http://lists.xen.org/xen-users > > _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |