I have tried running it in Compatibility mode, but it didn't work.
On Wed, May 11, 2016 at 10:04 AM Brett Peckinpaugh <b...@erylflynn.com>
wrote:
> Have you tried running the game in compatibility mode set to 8.1?
>
>
> On May 11, 2016 5:26:19 AM PDT, Abdulla Bubshait <darkst...@gmail.com>
> wrote:
>>
>> StarCraft and heroes are the two games that have this problem, they are
>> both based on the same engine. Unfortunately I cannot test the cpu because
>> if I were to change my cpu to anything but "host" my machine will not boot
>> (I believe this is due to a problem with the AMD drivers).
>>
>> I believe the MSRs are called by Windows 10, since they are privileged
>> registers. Likely for debugging purposes here.
>>
>> I would suggest trying something more related tou your cpu ("Haswell" in
>> my case) instead of "core2duo". I remember when I first tried to install
>> Win10 under virt-manager I got a KVM error about unsupported cpu functions
>> when I tried to clone the host cpu. Setting it to Haswell cleared those
>> errors so this might have something to do with it. Unfortunately that
>> didn't play nice with my video card so I ended up with a command line setup
>> as virt-manager setup refused to load AMD drivers.
>> Hope this helps.
>>
>> Abdulla
>>
>> On Wed, May 11, 2016, 04:03 Ivan Volosyuk <ivan.volos...@gmail.com>
>> wrote:
>>
>>> My 2c: I had the same issues with StarCraft crashing on Win10 due to the
>>> unsupported msrs (or producing lots of logs in dmesg). On Win8.1 I don't
>>> have this problem. My best guess is that nvidia drivers for Win10 started
>>> to use msrs unsupported by qemu. Can you change your CPU to emulated
>>> core2duo and check if it actually works faster and doesn't produce this
>>> logging spam?
>>>
>>> On Wed, May 11, 2016 at 4:50 PM Quentin Deldycke <
>>> quentindeldy...@gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I also play quite much this game. Adding this option makes the game
>>>> "Works".
>>>>
>>>> But for me, it is also the game with worst performance. As there is a
>>>> storm of unsupported msr (not 1 or 2 but hundreds of thousands...)
>>>>
>>>> Do you have correct performance? I go between 120 at begging to 15
>>>> during fights.
>>>>
>>>> Note that this is the only game making such mess with msr. Other
>>>> blizzard games works perfectly...
>>>> On 11 May 2016 1:04 am, "Abdulla Bubshait" <darkst...@gmail.com> wrote:
>>>>
>>>>> Just put that in and it solved the problem.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Tue, May 10, 2016 at 6:54 PM Alex Williamson <
>>>>> alex.l.william...@gmail.com> wrote:
>>>>>
>>>>>> On Tue, May 10, 2016 at 4:40 PM, Abdulla Bubshait <
>>>>>> darkst...@gmail.com> wrote:
>>>>>>
>>>>>>> I have a pretty stable VFIO setup running for a while, but I am
>>>>>>> stuck with this
>>>>>>> odd problem where 1 game (heroes of the storm) keeps giving me a BSOD
>>>>>>> whenever I try to run it in the VM under Windows 10.
>>>>>>>
>>>>>>> All other games are running fine. If I install Windows 8 in the VM
>>>>>>> the game runs fine.
>>>>>>> If I boot the machine into the Windows 10 HDD directly the game
>>>>>>> runs fine.
>>>>>>> This crash occurs with both Nvidia GTX 770 and AMD Fury X.
>>>>>>> It only crashes when in VM and Windows 10.
>>>>>>>
>>>>>>> The BSOD is some form of exception. Examples that occur
>>>>>>> SYSTEM_SERVICE_EXCEPTION
>>>>>>> KMODE_EXCEPTION_NOT_HANDLED
>>>>>>> SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
>>>>>>> The dump files seem to suggest a windows8 driver issue,
>>>>>>> but I can't pinpoint any faulty driver.
>>>>>>>
>>>>>>> I am running netrunner (manjaro) kernel 4.4.9, qemu 2.5.1.
>>>>>>>
>>>>>>> My config is:
>>>>>>> http://pastebin.com/W6cPyMEB
>>>>>>>
>>>>>>> Sample BSOD dumps:
>>>>>>> http://pastebin.com/bgh2uEhf
>>>>>>> http://pastebin.com/SLPTVUwn
>>>>>>> http://pastebin.com/zdjTzKuV
>>>>>>> http://pastebin.com/8Lt5VfLg
>>>>>>>
>>>>>>> Welcome any ideas to fix this problem. Thanks,
>>>>>>>
>>>>>>
>>>>>>
>>>>>> Do you have the following set in a modprobe.d conf file?
>>>>>>
>>>>>> options kvm ignore_msrs=1
>>>>>>
>>>>>> Windows BSODs are often the result of calling an unsupported MSR and
>>>>>> not handling the exception. There's some risk to this option because
>>>>>> zero
>>>>>> isn't guaranteed to be a valid return for an unknown MSR, but it seems to
>>>>>> solve a lot of problems. YMMV.
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> vfio-users mailing list
>>>>> vfio-users@redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/vfio-users
>>>>>
>>>>> _______________________________________________
>>>> vfio-users mailing list
>>>> vfio-users@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/vfio-users
>>>>
>>> ------------------------------
>>
>> vfio-users mailing list
>> vfio-users@redhat.com
>> https://www.redhat.com/mailman/listinfo/vfio-users
>>
>>
_______________________________________________
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users
