[vfio-users] Steam blocking VMs in csgo?

Brandon Ganem brandonganem at gmail.com
Mon Feb 27 02:43:42 UTC 2017


I'll give it a go again if I get kicked after these changes. Thanks for
your help!

On Sun, Feb 26, 2017 at 9:41 PM, Taiidan at gmx.com <Taiidan at gmx.com> wrote:

> Damn, like I said you should submit a support ticket with valve.
>
> I am sure there is a way, no matter how hard the web 2.0 companies try to
> make it.
>
>
> On 02/26/2017 09:39 PM, Brandon Ganem wrote:
>
>> Updated to the following:
>>    <features>
>>      <acpi/>
>>      <hyperv>
>>        <relaxed state='on'/>
>>        <vapic state='on'/>
>>        <spinlocks state='on' retries='8191'/>
>>      </hyperv>
>>      <kvm>
>>        <hidden state='on'/>
>>      </kvm>
>>    </features>
>>    <cpu mode='host-passthrough'>
>>      <topology sockets='1' cores='6' threads='2'/>
>>    </cpu>
>>    <clock offset='localtime'>
>>      <timer name='hypervclock' present='yes'/>
>>    </clock>
>>
>> So far i'm in a game, but it typically takes anywhere from 30 minutes to
>> an
>> hour to get VAC'd based on the last 3 attempts.
>>
>> On Sun, Feb 26, 2017 at 9:34 PM, Taiidan at gmx.com <Taiidan at gmx.com> wrote:
>>
>> You need to use a newer version of libvirt that has the vendor tag
>>> workaround to be able to get past that, it should also give you better
>>> performance to use all the hyperv enhancements.
>>>
>>> This
>>> <vendor_id state='on' value='whatever'/>
>>> needs to be supported but I forgot which version added it
>>>
>>>
>>> On 02/26/2017 09:30 PM, Brandon Ganem wrote:
>>>
>>> Looks like I've got the opposite of all of that enabled, probably was for
>>>> code 43 issues. I'll update to recommended hyper-v settings and see.
>>>>
>>>> On Sun, Feb 26, 2017 at 9:12 PM, Taiidan at gmx.com <Taiidan at gmx.com>
>>>> wrote:
>>>>
>>>> Did you try the hyperV clock? it could be a timer issue.
>>>>
>>>>>
>>>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20170226/3e2a4b2a/attachment.htm>


More information about the vfio-users mailing list