Re: [vfio-users] Nvidia Error 43 and vendor_id state='on'

[Jayme Howard]

When I get error 43, I generally just delete the video card (and the
virtual one) from the device manager a few times, rebooting in between.
Eventually it comes back just fine.  It's definitely not ideal, but it's
worked for me so far.

On Sat, Jun 11, 2016 at 8:53 AM, David  wrote:

> I am getting the error 43 for my Nvidia card in a Win 7 guest with
> UEFI. Host is Fedora 23 fully updated. Is this document correct =
> (https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF)
> (Under the Troubleshooting section near the bottom) that with new
> versions of QEMU and Libvert I shouldn't need to worry about “-cpu
> host,kvm=off” or clearing out the  part of my XML file or
> anything else?
>
> And instead just add “” in the
> XML under ? This did not work for me, but it may be because I
> actually used “whatever”, not knowing a valid value to give for
> vendor_id. Anyone else have this working and can supply a value?
>
>
> If this isn't working for others, I would like to request some help
> resolving my error 43. I am new to KVM and linux as a whole, and used
> this guide (
> http://vfio.blogspot.com/2015/05/vfio-gpu-how-to-series-part-4-our-first.html
> )
> to get this far.
>
> My VM was working the other day, I installed some Steam games and
> playtested, and other than some audio issues everything was working
> ok. After a few reboots to get hugepages working, the error 43
> started.
>
> My versions =
>
> # virsh version
> Compiled against library: libvirt 1.3.3
> Using library: libvirt 1.3.3
> Using API: QEMU 1.3.3
> Running hypervisor: QEMU 2.6.0
>
> # uname -r
> 4.5.5-201.fc23.x86_64
>
> --
> David
> david...@gmail.com
>
> ___
> 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

Re: [vfio-users] Far Cry Primal

[Jayme Howard]

I don't think Blizzard uses Denuvo.

On Tue, Jun 14, 2016 at 7:29 AM, thibaut noah <thibaut.n...@gmail.com>
wrote:

> That might also have to do with denuvo protection
>
> 2016-06-14 9:49 GMT+02:00 Abdulla Bubshait <darkst...@gmail.com>:
>
>> Yes, this is a win10 issue.
>> Changing the Virtual CPU model does not make a difference. Each model has
>> its own LBR register address, but one will be called.
>>
>> The only thing I have not tried is using an AMD processor. AMD CPUs
>> support lbrv which is virtualization of the LBR registers, so it is handled
>> in hardware rather than software.
>> If anyone has an AMD CPU and a win10 VM willing to confirm if their setup
>> does indeed work in these games, that would be great.
>>
>> On Tue, Jun 14, 2016 at 3:39 AM Ivan Volosyuk <ivan.volos...@gmail.com>
>> wrote:
>>
>>> 2 things:
>>>  - this msrs are not called from StarCraft on Win8.1.
>>>  - i wonder if forcing virtual CPU model to something older will disable
>>> them in Win10.
>>>
>>> This msrs issue is what holds me off upgrade to W10.
>>>
>>> On Tue, Jun 14, 2016 at 12:39 PM Jayme Howard <g.pr...@gmail.com> wrote:
>>>
>>>> For what it's worth, I believe I was getting them on Overwatch as
>>>> well.  It's not happening with EVERY game I have though.
>>>>
>>>> On Mon, Jun 13, 2016 at 8:28 PM, Abdulla Bubshait <darkst...@gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, Jun 13, 2016 at 6:27 PM, Jayme Howard <g.pr...@gmail.com>
>>>>> wrote:
>>>>> > That's the output for Doom.
>>>>> >
>>>>> > [1639445.044855] kvm [9487]: vcpu2 kvm_set_msr_common:
>>>>> MSR_IA32_DEBUGCTLMSR
>>>>> > 0x1, nop
>>>>> > [1639445.044861] kvm [9487]: vcpu2 ignored rdmsr: 0x1c9
>>>>> > [1639445.044862] kvm [9487]: vcpu2 ignored rdmsr: 0x680
>>>>> > [1639445.044863] kvm [9487]: vcpu2 ignored rdmsr: 0x6c0
>>>>> > [1639445.044890] kvm [9487]: vcpu1 kvm_set_msr_common:
>>>>> MSR_IA32_DEBUGCTLMSR
>>>>> > 0x1, nop
>>>>> > [1639445.044895] kvm [9487]: vcpu1 ignored rdmsr: 0x1c9
>>>>> > [1639445.044896] kvm [9487]: vcpu1 ignored rdmsr: 0x680
>>>>> > [1639445.044897] kvm [9487]: vcpu1 ignored rdmsr: 0x6c0
>>>>> > [1639445.044905] kvm [9487]: vcpu1 kvm_set_msr_common:
>>>>> MSR_IA32_DEBUGCTLMSR
>>>>> > 0x1, nop
>>>>> > [1639445.044907] kvm [9487]: vcpu1 ignored rdmsr: 0x1c9
>>>>> > [1639445.044908] kvm [9487]: vcpu1 ignored rdmsr: 0x680
>>>>> > [1639445.044909] kvm [9487]: vcpu1 ignored rdmsr: 0x6c0
>>>>> > [1639445.046195] kvm [9487]: vcpu2 kvm_set_msr_common:
>>>>> MSR_IA32_DEBUGCTLMSR
>>>>> > 0x1, nop
>>>>> > [1639445.046198] kvm [9487]: vcpu2 ignored rdmsr: 0x1c9
>>>>> > [1639445.046204] kvm [9487]: vcpu2 kvm_set_msr_common:
>>>>> MSR_IA32_DEBUGCTLMSR
>>>>> > 0x1, nop
>>>>> > [1639445.155114] kvm [9487]: vcpu0 kvm_set_msr_common:
>>>>> MSR_IA32_DEBUGCTLMSR
>>>>> > 0x1, nop
>>>>> > [1639445.155123] kvm [9487]: vcpu0 kvm_set_msr_common:
>>>>> MSR_IA32_DEBUGCTLMSR
>>>>> > 0x1, nop
>>>>> >
>>>>>
>>>>> Odd, this is another game that is contantly reading the LBR. I
>>>>> initially thought this was part of the StarCraft 2 and Heroes of the Storm
>>>>> code. But now I think this might be part of Windows 10. Something being
>>>>> called by these games is causing a ton of LBR reads. Maybe DX 12?
>>>>>
>>>>> I think if we can find what is causing these reads in the games we
>>>>> might be able to solve it. Because if this is the case we might be getting
>>>>> more and more games with performance problems because of these LBR checks.
>>>>>
>>>>
>>>> ___
>>>> 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

Re: [vfio-users] Far Cry Primal

[Jayme Howard]

Actually, I also haven't seen further ones while I'm playing Overwatch.
Just at startup.  I wonder if maybe I've got something misconfigured?

On Tue, Jun 14, 2016 at 11:23 AM, Abdulla Bubshait <darkst...@gmail.com>
wrote:

> Thanks, I guess the "issue" is only from the blizzard games. It could very
> well be that this is used as some anti-tamper tool in these blizzard games,
> but I find it odd that it only does this in Win10 and that returning 0
> doesn't cause a problem.
>
> On Tue, Jun 14, 2016 at 12:06 PM Jayme Howard <g.pr...@gmail.com> wrote:
>
>> I've only seen it call them at startup.  After playing for an hour or so,
>> I didn't see more of them in my dmesg output.
>>
>> On Tue, Jun 14, 2016 at 9:38 AM, Abdulla Bubshait <darkst...@gmail.com>
>> wrote:
>>
>>> For what its worth it seems Rise of the Tomb Raider also calls it, so it
>>> might be Denuvo.
>>>
>>> The interesting thing is Rise of the Tomb Raider only calls it once. So
>>> there is no performance issue. Heroes and Starcraft continuously make these
>>> calls which causes the performance issue.
>>>
>>> Can anyone confirm if Doom only calls up the MSRS in one spot or does it
>>> constantly keep calling the MSRS throughout the game?
>>>
>>> On Tue, Jun 14, 2016 at 8:55 AM thibaut noah <thibaut.n...@gmail.com>
>>> wrote:
>>>
>>>> They have the warden which is constantly checking your system
>>>>
>>>> 2016-06-14 14:36 GMT+02:00 Jayme Howard <g.pr...@gmail.com>:
>>>>
>>>>> I don't think Blizzard uses Denuvo.
>>>>>
>>>>> On Tue, Jun 14, 2016 at 7:29 AM, thibaut noah <thibaut.n...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> That might also have to do with denuvo protection
>>>>>>
>>>>>> 2016-06-14 9:49 GMT+02:00 Abdulla Bubshait <darkst...@gmail.com>:
>>>>>>
>>>>>>> Yes, this is a win10 issue.
>>>>>>> Changing the Virtual CPU model does not make a difference. Each
>>>>>>> model has its own LBR register address, but one will be called.
>>>>>>>
>>>>>>> The only thing I have not tried is using an AMD processor. AMD CPUs
>>>>>>> support lbrv which is virtualization of the LBR registers, so it is 
>>>>>>> handled
>>>>>>> in hardware rather than software.
>>>>>>> If anyone has an AMD CPU and a win10 VM willing to confirm if their
>>>>>>> setup does indeed work in these games, that would be great.
>>>>>>>
>>>>>>> On Tue, Jun 14, 2016 at 3:39 AM Ivan Volosyuk <
>>>>>>> ivan.volos...@gmail.com> wrote:
>>>>>>>
>>>>>>>> 2 things:
>>>>>>>>  - this msrs are not called from StarCraft on Win8.1.
>>>>>>>>  - i wonder if forcing virtual CPU model to something older will
>>>>>>>> disable them in Win10.
>>>>>>>>
>>>>>>>> This msrs issue is what holds me off upgrade to W10.
>>>>>>>>
>>>>>>>> On Tue, Jun 14, 2016 at 12:39 PM Jayme Howard <g.pr...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> For what it's worth, I believe I was getting them on Overwatch as
>>>>>>>>> well.  It's not happening with EVERY game I have though.
>>>>>>>>>
>>>>>>>>> On Mon, Jun 13, 2016 at 8:28 PM, Abdulla Bubshait <
>>>>>>>>> darkst...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jun 13, 2016 at 6:27 PM, Jayme Howard <g.pr...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>> > That's the output for Doom.
>>>>>>>>>> >
>>>>>>>>>> > [1639445.044855] kvm [9487]: vcpu2 kvm_set_msr_common:
>>>>>>>>>> MSR_IA32_DEBUGCTLMSR
>>>>>>>>>> > 0x1, nop
>>>>>>>>>> > [1639445.044861] kvm [9487]: vcpu2 ignored rdmsr: 0x1c9
>>>>>>>>>> > [1639445.044862] kvm [9487]: vcpu2 ignored rdmsr: 0x680
>>>>>>>>>> &

Re: [vfio-users] Far Cry Primal

[Jayme Howard]

I've only seen it call them at startup.  After playing for an hour or so, I
didn't see more of them in my dmesg output.

On Tue, Jun 14, 2016 at 9:38 AM, Abdulla Bubshait <darkst...@gmail.com>
wrote:

> For what its worth it seems Rise of the Tomb Raider also calls it, so it
> might be Denuvo.
>
> The interesting thing is Rise of the Tomb Raider only calls it once. So
> there is no performance issue. Heroes and Starcraft continuously make these
> calls which causes the performance issue.
>
> Can anyone confirm if Doom only calls up the MSRS in one spot or does it
> constantly keep calling the MSRS throughout the game?
>
> On Tue, Jun 14, 2016 at 8:55 AM thibaut noah <thibaut.n...@gmail.com>
> wrote:
>
>> They have the warden which is constantly checking your system
>>
>> 2016-06-14 14:36 GMT+02:00 Jayme Howard <g.pr...@gmail.com>:
>>
>>> I don't think Blizzard uses Denuvo.
>>>
>>> On Tue, Jun 14, 2016 at 7:29 AM, thibaut noah <thibaut.n...@gmail.com>
>>> wrote:
>>>
>>>> That might also have to do with denuvo protection
>>>>
>>>> 2016-06-14 9:49 GMT+02:00 Abdulla Bubshait <darkst...@gmail.com>:
>>>>
>>>>> Yes, this is a win10 issue.
>>>>> Changing the Virtual CPU model does not make a difference. Each model
>>>>> has its own LBR register address, but one will be called.
>>>>>
>>>>> The only thing I have not tried is using an AMD processor. AMD CPUs
>>>>> support lbrv which is virtualization of the LBR registers, so it is 
>>>>> handled
>>>>> in hardware rather than software.
>>>>> If anyone has an AMD CPU and a win10 VM willing to confirm if their
>>>>> setup does indeed work in these games, that would be great.
>>>>>
>>>>> On Tue, Jun 14, 2016 at 3:39 AM Ivan Volosyuk <ivan.volos...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> 2 things:
>>>>>>  - this msrs are not called from StarCraft on Win8.1.
>>>>>>  - i wonder if forcing virtual CPU model to something older will
>>>>>> disable them in Win10.
>>>>>>
>>>>>> This msrs issue is what holds me off upgrade to W10.
>>>>>>
>>>>>> On Tue, Jun 14, 2016 at 12:39 PM Jayme Howard <g.pr...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> For what it's worth, I believe I was getting them on Overwatch as
>>>>>>> well.  It's not happening with EVERY game I have though.
>>>>>>>
>>>>>>> On Mon, Jun 13, 2016 at 8:28 PM, Abdulla Bubshait <
>>>>>>> darkst...@gmail.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jun 13, 2016 at 6:27 PM, Jayme Howard <g.pr...@gmail.com>
>>>>>>>> wrote:
>>>>>>>> > That's the output for Doom.
>>>>>>>> >
>>>>>>>> > [1639445.044855] kvm [9487]: vcpu2 kvm_set_msr_common:
>>>>>>>> MSR_IA32_DEBUGCTLMSR
>>>>>>>> > 0x1, nop
>>>>>>>> > [1639445.044861] kvm [9487]: vcpu2 ignored rdmsr: 0x1c9
>>>>>>>> > [1639445.044862] kvm [9487]: vcpu2 ignored rdmsr: 0x680
>>>>>>>> > [1639445.044863] kvm [9487]: vcpu2 ignored rdmsr: 0x6c0
>>>>>>>> > [1639445.044890] kvm [9487]: vcpu1 kvm_set_msr_common:
>>>>>>>> MSR_IA32_DEBUGCTLMSR
>>>>>>>> > 0x1, nop
>>>>>>>> > [1639445.044895] kvm [9487]: vcpu1 ignored rdmsr: 0x1c9
>>>>>>>> > [1639445.044896] kvm [9487]: vcpu1 ignored rdmsr: 0x680
>>>>>>>> > [1639445.044897] kvm [9487]: vcpu1 ignored rdmsr: 0x6c0
>>>>>>>> > [1639445.044905] kvm [9487]: vcpu1 kvm_set_msr_common:
>>>>>>>> MSR_IA32_DEBUGCTLMSR
>>>>>>>> > 0x1, nop
>>>>>>>> > [1639445.044907] kvm [9487]: vcpu1 ignored rdmsr: 0x1c9
>>>>>>>> > [1639445.044908] kvm [9487]: vcpu1 ignored rdmsr: 0x680
>>>>>>>> > [1639445.044909] kvm [9487]: vcpu1 ignored rdmsr: 0x6c0
>>>>>>>> > [1639445.046195] kvm [9487]: vcpu2 kvm_set_msr_common:
>>>>>>>> MSR_IA32_DEBUGCTLMSR
>>>>>>

Re: [vfio-users] Far Cry Primal

[Jayme Howard]

Truthfully, I don't know offhand.  If you can tell me how to determine
that, I can check it out when I get home.

On Mon, Jun 13, 2016 at 4:44 PM, Abdulla Bubshait <darkst...@gmail.com>
wrote:

> What msrs does doom call?
>
> On Mon, Jun 13, 2016, 17:36 Jayme Howard <g.pr...@gmail.com> wrote:
>
>> I've seen exactly the same behavior with DOOM.  ignore_msrs fixed the
>> problem for me.
>>
>> On Mon, Jun 13, 2016 at 4:35 PM, Brett Peckinpaugh <b...@erylflynn.com>
>> wrote:
>>
>>> I wanted to see if anyone else has been able to play this on a VM.  At
>>> this time it is the only one, and it forces a reboot.  I have a ticket in
>>> with Ubisoft, but with their heavy handed DRM I am concerned it might be
>>> DRM.
>>>
>>> Was hoping to see if anyone has ran it to somewhat rule out the VM as
>>> being part of the issue.
>>>
>>> ___
>>> 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

Re: [vfio-users] Far Cry Primal

[Jayme Howard]

Ah, I didn't realize those were the actual output you wanted.  I've got
output from a few different games in dmesg, so I'll fire up Doom when I get
home and see what it spits out and reply.

On Mon, Jun 13, 2016 at 4:49 PM, Abdulla Bubshait <darkst...@gmail.com>
wrote:

> It usually outputs the ignored msrs to dmesg.
>
> On Mon, Jun 13, 2016, 17:45 Jayme Howard <g.pr...@gmail.com> wrote:
>
>> Truthfully, I don't know offhand.  If you can tell me how to determine
>> that, I can check it out when I get home.
>>
>> On Mon, Jun 13, 2016 at 4:44 PM, Abdulla Bubshait <darkst...@gmail.com>
>> wrote:
>>
>>> What msrs does doom call?
>>>
>>> On Mon, Jun 13, 2016, 17:36 Jayme Howard <g.pr...@gmail.com> wrote:
>>>
>>>> I've seen exactly the same behavior with DOOM.  ignore_msrs fixed the
>>>> problem for me.
>>>>
>>>> On Mon, Jun 13, 2016 at 4:35 PM, Brett Peckinpaugh <b...@erylflynn.com>
>>>> wrote:
>>>>
>>>>> I wanted to see if anyone else has been able to play this on a VM.  At
>>>>> this time it is the only one, and it forces a reboot.  I have a ticket in
>>>>> with Ubisoft, but with their heavy handed DRM I am concerned it might be
>>>>> DRM.
>>>>>
>>>>> Was hoping to see if anyone has ran it to somewhat rule out the VM as
>>>>> being part of the issue.
>>>>>
>>>>> ___
>>>>> 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

Re: [vfio-users] Far Cry Primal

[Jayme Howard]

I've seen exactly the same behavior with DOOM.  ignore_msrs fixed the
problem for me.

On Mon, Jun 13, 2016 at 4:35 PM, Brett Peckinpaugh 
wrote:

> I wanted to see if anyone else has been able to play this on a VM.  At
> this time it is the only one, and it forces a reboot.  I have a ticket in
> with Ubisoft, but with their heavy handed DRM I am concerned it might be
> DRM.
>
> Was hoping to see if anyone has ran it to somewhat rule out the VM as
> being part of the issue.
>
> ___
> 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

Re: [vfio-users] Far Cry Primal

[Jayme Howard]

For what it's worth, I believe I was getting them on Overwatch as well.
It's not happening with EVERY game I have though.

On Mon, Jun 13, 2016 at 8:28 PM, Abdulla Bubshait <darkst...@gmail.com>
wrote:

>
>
> On Mon, Jun 13, 2016 at 6:27 PM, Jayme Howard <g.pr...@gmail.com> wrote:
> > That's the output for Doom.
> >
> > [1639445.044855] kvm [9487]: vcpu2 kvm_set_msr_common:
> MSR_IA32_DEBUGCTLMSR
> > 0x1, nop
> > [1639445.044861] kvm [9487]: vcpu2 ignored rdmsr: 0x1c9
> > [1639445.044862] kvm [9487]: vcpu2 ignored rdmsr: 0x680
> > [1639445.044863] kvm [9487]: vcpu2 ignored rdmsr: 0x6c0
> > [1639445.044890] kvm [9487]: vcpu1 kvm_set_msr_common:
> MSR_IA32_DEBUGCTLMSR
> > 0x1, nop
> > [1639445.044895] kvm [9487]: vcpu1 ignored rdmsr: 0x1c9
> > [1639445.044896] kvm [9487]: vcpu1 ignored rdmsr: 0x680
> > [1639445.044897] kvm [9487]: vcpu1 ignored rdmsr: 0x6c0
> > [1639445.044905] kvm [9487]: vcpu1 kvm_set_msr_common:
> MSR_IA32_DEBUGCTLMSR
> > 0x1, nop
> > [1639445.044907] kvm [9487]: vcpu1 ignored rdmsr: 0x1c9
> > [1639445.044908] kvm [9487]: vcpu1 ignored rdmsr: 0x680
> > [1639445.044909] kvm [9487]: vcpu1 ignored rdmsr: 0x6c0
> > [1639445.046195] kvm [9487]: vcpu2 kvm_set_msr_common:
> MSR_IA32_DEBUGCTLMSR
> > 0x1, nop
> > [1639445.046198] kvm [9487]: vcpu2 ignored rdmsr: 0x1c9
> > [1639445.046204] kvm [9487]: vcpu2 kvm_set_msr_common:
> MSR_IA32_DEBUGCTLMSR
> > 0x1, nop
> > [1639445.155114] kvm [9487]: vcpu0 kvm_set_msr_common:
> MSR_IA32_DEBUGCTLMSR
> > 0x1, nop
> > [1639445.155123] kvm [9487]: vcpu0 kvm_set_msr_common:
> MSR_IA32_DEBUGCTLMSR
> > 0x1, nop
> >
>
> Odd, this is another game that is contantly reading the LBR. I initially
> thought this was part of the StarCraft 2 and Heroes of the Storm code. But
> now I think this might be part of Windows 10. Something being called by
> these games is causing a ton of LBR reads. Maybe DX 12?
>
> I think if we can find what is causing these reads in the games we might
> be able to solve it. Because if this is the case we might be getting more
> and more games with performance problems because of these LBR checks.
>
___
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users

Re: [vfio-users] [Virt-Manager]Unable to install Nvidia driver (crash during installation)

[Jayme Howard]

Does the vendor ID need to be exactly 12 characters to work reliably?  I
believe I've been using nvidia43fix as mine, and had unreliable results.
 ~75% of the time my VM boots with code 43.

On Fri, Jun 17, 2016 at 10:30 AM, Alex Williamson <
alex.l.william...@gmail.com> wrote:

> On Fri, Jun 17, 2016 at 3:57 AM, Berillions  wrote:
>
>> Hi,
>>
>> I have a big problem when i want to install the Nvidia driver on my
>> Windows 10 VM.
>> The VM's creation and installation of Windows 10 is correct. I can use it
>> without problem.
>>
>> But during the installation of Nvidia driver, I have a BSOD with this
>> error message :
>>
>> *SYSTEM_THREAD_EXCEPTION_NOT_HANDLED *
>> but KVM is hidden in my .xml (see pastebin)
>>
>> I give you the pastebin which have these informations :
>> - Boot kernel line
>> - How i install Win10 on the VM
>> - Graphic card
>> - Libvirt xml
>>
>> http://pastebin.com/rXsW3PyY
>>
>
> a) Add a modprobe.d entry to add the ignore_msrs options to kvm, ex:
>
> # cat /etc/modprobe.d/local.conf
> options kvm ignore_msrs=1
>
> b) Hiding kvm is not enough, you also need to mask hyper-v extensions to
> avoid a code43.  Add within the  section:
>
> 
>
> (or some other random 12-char string)
>
> ___
> 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

Re: [vfio-users] Guest does not boot OS with GPU passed through, stuck at TianoCore boot splash

[Jayme Howard]

Possibly more appropriate to the spirit of another thread, but for what
it's worth Alex, I'm using both emulated graphics and an NVIDIA GTX 970
together, successfully.  Not going to try to derail this further, just felt
that it's worth noting for anybody who catches this in the archive.

On Mon, Apr 11, 2016 at 3:36 PM, Alex Williamson <
alex.l.william...@gmail.com> wrote:

> On Mon, Apr 11, 2016 at 1:47 PM, Stefan Seil  wrote:
>
>> I am already running on 4.5, so that should be fine. The OVMF version I
>> was using was a couple of months old, so I just got a newer one from
>> https://www.kraxel.org/repos/jenkins/edk2/ and pointed the respective
>> XML tag to the newer OVMF_CODE-pure-efi.fd, but that did not change
>> anything.
>> I guess your card is from a different manufacturer then and thus has a
>> different ROM? Because if I try to use the standard ROM of my card (as in
>> not explicitly passing any rom file to the VM at all), I don't get any
>> output on the monitor connected to the card at all.
>> What exactly do you mean with "AMD cards also have the option of running
>> as secondary graphics devices in many cases"?
>
>
> You have two options when you assign a GPU to a VM, you can do it in
> addition to the emulated graphics (cirrus/VGA/QXL) or instead of the
> emulated graphics.  You indicated following my blog, so I assume you
> removed the emulated graphics when you added the assigned GPU.  This is
> necessary for NVIDIA GeForce, but many users have found that AMD cards also
> work when added to the VM configuration with the emulated graphics.  No ROM
> is necessary on the assigned GPU in this case.  The emulated graphics will
> show the BIOS and early boot output, then the assigned graphics can be
> enabled.  This mode doesn't actually require OVMF, it works with SeaBIOS
> too.
>
> Anyway, I'm curious to the answers to Laszlo's questions.  I've also seen
> hangs at the TianoCore splash with certain USB host controllers assigned.
> Thanks,
>
> Alex
>
> ___
> 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

Re: [vfio-users] cpu usage in guest != cpu usage in host, even with exclusive pinning

[Jayme Howard]

Okay wow, Alex.  That made a huge difference immediately.  That dropped me
from 90% to 33% on the main thread, and all the children are below 10%.

On Sun, Apr 3, 2016 at 8:07 PM, Alex Williamson  wrote:

> If this is the issue I think it is, the unraid folks bisected this and
> found the culprit as:
>
> aca6ff2 KVM: dynamic halt-polling
>
> (
> https://github.com/torvalds/linux/commit/aca6ff29c4063a8d467cdee241e6b3bf7dc4a171
> )
>
> It seems to be a poor interaction of the halt polling interval vs the
> timer ticks on win10.  You can pick a different polling interval with the
> kvm module option halt_poll_ns.  The default is 50.  It seemed that
> setting this to 40 or lower resolves the issue.  You can do this via a
> modprobe entry, 'options kvm halt_poll_ns=40' or on the kernel command
> line with kvm.halt_poll_ns=40.  You can also change it dynamically via
> 'echo 40 > /sys/module/kvm/parameters/halt_poll_ns'
>
> ___
> 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

Re: [vfio-users] Nvidia GTX 970 sound is choppy

[Jayme Howard]

Alternately, if that doesn't help you, Razer's got a virtual surround app
that generates a virtual sound card.  I use that as my default sound card
in the VM.  That doesn't solve the problem if you're using the sound
directly on the host, though.  I play through in-home streaming, and Steam
picks up the virtual card as a valid audio source and streams it perfectly.

On Tue, Apr 19, 2016 at 1:36 PM, Alex Williamson <
alex.l.william...@gmail.com> wrote:

>
> http://vfio.blogspot.com/2014/09/vfio-interrupts-and-how-to-coax-windows.html
>
> ___
> 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

Re: [vfio-users] NVIDIA GPU Passthrough to Win10 - Driver Disabled (Code 43)

[Jayme Howard]

I don't have an XML example handy, but you're missing the Nvidia workaround
flags.  In the CLI version, they look like the following:

OPTS="$OPTS -cpu
host,kvm=off,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=Nvidia43FIX"

All those hv_ flags are necessary to get around Nvidia's virtualization
detection.  You also don't mention what version of QEMU you're running, but
I believe those flags were added in 2.3 or 2.4.  2.5's out now, and uses
those as well.

On Mon, Jul 25, 2016 at 3:45 PM, Steven Bell  wrote:

> Hello,
>
> I am currently trying to setup a Windows 10 VM on a Fedora 23 host with
> QEMU-KVM passing through a NIC, a USB controller, and a NVIDIA GPU (GTX
> 670). With my current setup, the NIC and USB Controller are both passed
> through and function without issue. The GPU driver gives the message
> "Windows has stopped this device because it has reported problems. (Code
> 43)".
>
> I've been following Alex Williamson's guide (
> http://vfio.blogspot.ca/2015/05/vfio-gpu-how-to-series-part-3-host.html )
> and I believe I have successfully configured things on the host.
>
> On the host, if I use "lshw" to look at my hardware devices, I can find
> the NIC, USB controller and both the GPU's video and audio controllers.
> They all correctly list their drivers as "vfio-pci". All the device ids are
> listed in the modprobe.d file and I believe the vfio-pci driver is proof
> that this is working, and the host is not binding these devices on boot.
>
> I have also verified that the motherboard (MSI WORKSTATION C236A) groups
> the PCI devices correctly. The NIC and USB controllers are in their own
> IOMMU groups respectively, and the NVIDIA GPU has 3 items in its group. The
> root PCIe Controller (which I believe should NOT be configured to be passed
> through) and the Video and Audio controllers, both of which WILL be passed
> through.
>
> I configure an i440FX machine using virt-manager. I set the firmware to
> UEFI x86_64. Initially I do not make any of the PCI devices available and
> install Windows onto the VM.
>
> Next, I reboot the Guest and only make the pass-through NIC available.
> It's drivers are installed correctly and I have access to the LAN it
> connects to. I am able to use that connection to copy vfio-drivers for
> Balloon driver installation, as well as the most up to date NVIDIA driver
> installer (but don't run it yet). I also install TightVNC server.
>
> Next I shutdown and remove all unused devices, as described in Alex's
> guide. I remove the Display and Video devices (I will use the TightVNC
> server from here on to connect to the Guest). I also remove the USB
> redirect devices, the virtual NIC, etc. I add the pass-through USB
> controller and NVIDIA audio and video devices. Before booting again, I also
> edit the XML and add the required "" line in
> the features tag. Without this, the machine blue screens every time after
> the NVIDIA driver has been installed.
>
> Now I boot the Guest again, connect using the TightVNC server, and install
> the NVIDIA driver from the installer (I've tried different versions,
> standalone, through Windows Update etc.). The driver installs successfully
> and requests a reboot. After rebooting, the Device Manager shows GTX 670
> with a yellow mark and the message "Windows has stopped this device because
> it has reported problems. (Code 43)".
>
> No other devices appear with an issue in the Guest's Device Manager. No
> output is coming from the device to my screen plugged into the GPU card
> (obviously).
>
> I have also checked the following:
> The GPU should have sufficient power. My PSU is more than powerful
> enough. I hear the GPU fan spin up to full briefly when the Host powers on.
> I have checked in the Host's mobo BIOS settings that the default video
> card is the IGD. The host boots and uses the IGD without issue.
> As mentioned above, all devices that should not be bound by the host
> have vfio-pci as their listed driver .
> As mentioned above, the kvm hidden xml line is added. The log shows
> the "-cpu host,kvm=off " option is used to boot the VM, and removing line
> from the XML causes blue screen on boot so I believe it's doing it's job.
> No other display adapters are present or installed. I believe a
> pass-through GPU cannot be a secondary display device, so I've made sure of
> this.
>
>
> I feel like nothing I'm doing is especially tricky, and in my mind my
> setup SHOULD work, based on everything I've read. But honestly I've just
> run out of ideas on how to proceed with troubleshooting this.
>
> Any help and ideas would be appreciated. Thanks!
>
>
> ___
> 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] USB Devices Hang During Audio Playback

[Jayme Howard]

Alright, this one I'm struggling to come up with an answer for.

Last night, I added a USB 3 PCI-E expansion card to my PC.  Luckily, it
ended up in its own IOMMU group, so I passed it through to my VM with no
problems at all.  For reference, I've got a USB device switch connected to
both the new card, and my onboard USB so I can easily swap directly between
the host and guest with the same inputs.  Connected to the switch is a USB
3 hub, which currently has my keyboard, mouse, and a bluetooth adapter.
Plugged directly into the new USB 3 card is a USB audio adapter.  This is
where my problem gets weird.

Any time there's audio OUTPUT (specifically not input, because this device
does both) through the USB audio device, all other USB devices on the card
hang and refuse to respond until playback stops.  So, for example, if I
click on the volume slider in Windows to do a level check, my mouse and
keyboard will just stop entirely until the ding finishes.  This manifests
in a really horrible way if I open a game, because inputs stop responding
completely.

I've found that by swapping back and forth between the host and guest modes
on my USB switch, I can get input back briefly, usually about 2 seconds.
In many cases that can be enough to exit the game and get control of the
guest back.

My initial thought was that this was an issue with the audio adapter
itself.  I've since connected a separate USB headset and confirmed that it
causes the same behavior.  I also tested whether audio input causes it, and
confirmed that it specifically does not.  Further, audio output via HDMI
works perfectly.

This is mostly an annoyance and a curiosity at this point, because I've got
a somewhat functional workaround, but I'd really like to fix it if at all
possible.  I've checked my dmesg and not found anything in there that
corresponds with the timeframes that the problem occurred.

Attached is the shell script that I use to start the VM, and the output of
lspci -nnk.  If there are any other useful pieces of data I could provide,
I'd be glad to do so.

Thanks!
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM 
Controller [8086:0c00] (rev 06)
Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core 
Processor DRAM Controller [1462:7922]
Kernel driver in use: hsw_uncore
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x16 Controller [8086:0c01] (rev 06)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
DeviceName:  Onboard IGD
Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7922]
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller [8086:0c0c] (rev 06)
Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor HD Audio Controller [1462:7922]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB 
xHCI Controller [8086:8cb1]
Subsystem: Micro-Star International Co., Ltd. [MSI] 9 Series Chipset 
Family USB xHCI Controller [1462:7922]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset 
Family ME Interface #1 [8086:8cba]
Subsystem: Micro-Star International Co., Ltd. [MSI] 9 Series Chipset 
Family ME Interface [1462:7922]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB 
EHCI Controller #2 [8086:8cad]
Subsystem: Micro-Star International Co., Ltd. [MSI] 9 Series Chipset 
Family USB EHCI Controller [1462:7922]
Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio 
Controller [8086:8ca0]
Subsystem: Micro-Star International Co., Ltd. [MSI] 9 Series Chipset 
Family HD Audio Controller [1462:d922]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI 
Express Root Port 1 [8086:8c90] (rev d0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 
d0)
00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI 
Express Root Port 4 [8086:8c96] (rev d0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.6 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI 
Express Root Port 7 [8086:8c9c] (rev d0)
Kernel driver in use: pcieport

Re: [vfio-users] Dual monitor with spice display + hdmi

[Jayme Howard]

I've used both together, but I don't remember if one was mirroring the
other or if I did it as dual-monitor.  It was a configuration I abandoned
early on.  It DID work, but it caused (about 75% of the time) Nvidia code
43 issues for me.  But it definitely did work outside of that.

On Wed, Jan 18, 2017 at 1:08 PM, Doug Applegate 
wrote:

> Is it possible for a guest VM to use both spice server graphics with
> qxl video AND hdmi gpu passthrough? Could the guest be configured
> (windows 10 in this case) see it as a dual-monitor setup?
>
> Has anyone tried this or gotten it to work?
>
> ___
> 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

Re: [vfio-users] Dual monitor with spice display + hdmi

[Jayme Howard]

It just treats them as independent displays.  It can either mirror them, or
extend the desktop onto multiple.  It can't do multiple independent
desktops.  A real life example of this is a motherboard with onboard video
coupled with a discrete GPU in a slot.  As long as the onboard isn't
disabled, they can work in tandem, at least for software rendering.  From
what I understand, as well, DirectX 12 and Vulkan both support hardware
rendering with multiple GPUs of different brands.

On Wed, Jan 18, 2017 at 1:45 PM, Will Marler <w...@wmarler.com> wrote:

> That's an interesting scenario ... How does Windows handle multiple
> graphics cards? Like, let's say this was all bare metal, and the machine
> had 2 different models of nVidia cards and an ATI card, with a monitor
> connected to each card. Would Windows be able to display a desktop on each
> monitor, or span a single contiguous desktop across them? If yes then I'd
> guess that what you're asking is at least theoretically possible, though
> I've never tested personally.
>
> On Wed, Jan 18, 2017 at 12:19 PM, Jayme Howard <g.pr...@gmail.com> wrote:
>
>> I've used both together, but I don't remember if one was mirroring the
>> other or if I did it as dual-monitor.  It was a configuration I abandoned
>> early on.  It DID work, but it caused (about 75% of the time) Nvidia code
>> 43 issues for me.  But it definitely did work outside of that.
>>
>> On Wed, Jan 18, 2017 at 1:08 PM, Doug Applegate <doug.appleg...@gmail.com
>> > wrote:
>>
>>> Is it possible for a guest VM to use both spice server graphics with
>>> qxl video AND hdmi gpu passthrough? Could the guest be configured
>>> (windows 10 in this case) see it as a dual-monitor setup?
>>>
>>> Has anyone tried this or gotten it to work?
>>>
>>> ___
>>> 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

Re: [vfio-users] Nvidia code 43 with Ubuntu 16.04 host

[Jayme Howard]

Solving the libvirt version issue is easy enough.  Add
ppa:jacob/virtualisation and upgrade libvirt.  He's got 2.1.0 in there,
along with updated versions of qemu and virt-manager.

On Tue, Sep 6, 2016 at 1:00 PM, Alex Williamson  wrote:

> On Tue, Sep 6, 2016 at 11:47 AM, Will Marler  wrote:
>
>> Simon, are you able to boot your VM with GPU passthrough and no Code 43
>> errors without enabling any hyperv features? Do this first, then move on to
>> enabling Hyper V.
>>
>> "I cannot place the vendor_id flag in the xml because it is validated in
>> the Ubuntu package" -- what does this mean? Is there something specific to
>> the Ubuntu package that is checking the XML syntax and saying "vendor_id is
>> invalid?" When I got around to enabling HyperV on my VM, I ran into a
>> similar XML "validation" situation. But this was on Arch, not Ubuntu.
>> Ultimately I traced the problem down to putting a tag in the wrong
>> subsection. I'm afraid I didn't take notes, and don't remember the
>> specifics.
>>
>
> It means his version of libvirt is too old to recognize the tag and
> generates an error parsing the xml because it's unknown.  The referenced
> xml doesn't include anything that would trigger hyper-v afaict, so the
> vendor id should not even be necessary, but the resulting process args (ps
> aux | grep qemu) would confirm.  Note that Code 43 is a generic error code
> for the driver, it can also be generated when, for instance, an aux power
> plug is left disconnected.
>
> ___
> 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

Re: [vfio-users] Users of X99-boards, can you do me a small favor?

[Jayme Howard]

I can confirm that GFE doesn't care if the CPU doesn't match what the
physical CPU offers in terms of cores.  My i5-4670k is chugging along just
fine with 3 cores, as far as Windows knows.

On Tue, Oct 4, 2016 at 3:42 PM, Hristo Iliev  wrote:

> Am 04.10.2016 18:32, schrieb Brett Peckinpaugh:
>
> What are you settling that fixes the Nvidia experience complaint?
>>
>>
> In the domain description:
>
>   
> 
>   
>
> And ignore_msrs=1 in the options to the kvm kernel module.
>
> Apparently NVIDIA GFE is happy with i7-5820K having only two cores.
>
> Cheers,
> Hristo
>
> On October 4, 2016 9:15:56 AM PDT, Hristo Iliev  wrote:
>>>
>>> Hi Martin,
>>>
>>> Am 04.10.2016 10:09, schrieb Martin Schrodt:
>>> Hi Hristo,
>>>
>>> No need to sleep/wake - my X99-based system starts with TSC disabled:
>>>
>>> $ dmesg | grep TSC
>>> [ 0.00] tsc: Fast TSC calibration using PIT
>>> [ 0.077986] TSC deadline timer enabled
>>> [ 0.203383] TSC synchronization [CPU#0 -> CPU#1]:
>>> [ 0.203384] Measured 974558547804462 cycles TSC warp between CPUs,
>>> turning off TSC clock.
>>> [ 0.203388] tsc: Marking TSC unstable due to check_tsc_sync_source
>>> failed
>>>
>>> Consequently, tsc is not among the clock sources listed in
>>> available_clocksource. KVM is not happy about that:
>>>
>>> [16739.200656] kvm: SMP vm created on host with unstable TSC; guest
>>> TSC
>>> will not be reliable
>>> Ok, so an X99-board that behaves like this even on a fresh start.
>>> Interesting.
>>>
>>> But I haven't observed any instabilities of the Windows 10 guest,
>>> which
>>> happily runs with 4 virtual CPUs (2 virtual hyperthreaded CPUs) bound
>>> to
>>> two cores of my i7-5820K.
>>> This really makes me think there's something else involved in this
>>> behaviour. Maybe the CPU configuration (I use "Skylake-Client") exposes
>>> TSC to the guest, so if you put that on, it'll use it?
>>>
>>> Can you check what kind of virtual CPU you use?
>>>
>>
>> I use 'passthrough', otherwise the default 'Haswell-noTSX' that
>> virt-manager picks results in NVIDIA GeForce Experience complaining
>> about unrecognised CPU
>> type, so the TSC gets pretty much exposed to the
>> guest.
>>
>> Just found this paste with a boot log from another system with the same
>> motherboard, though with an older BIOS version and a Xeon E5-1620 v3
>> CPU:
>>
>> https://pastelink.net/fjm
>>
>> It shows the same problem with unsynchronised TSCs. Could also be
>> something specific to the LGA 2011v3 processors or to the EFI BIOS. I'll
>> take a look in the BIOS options when time permits.
>>
>> Cheers,
>>> Martin
>>>
>>
>> Cheers,
>> Hristo
>>
>
> ___
>
> 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

Re: [vfio-users] Win10 Guest, stability is horrible and freeze quickly

[Jayme Howard]

Put the 960 into the one that goes 4x if you're that worried about it, but
it shouldn't be a huge deal.  I don't know if the 960 can even saturate a
4x.  It might be able to, but since it's a lower performance card anyway,
it shouldn't really matter.

On Fri, Oct 7, 2016 at 12:36 PM, Berillions  wrote:

> I have two PCI-E 3.0 16x slot,
>
> The first with the 960 and the second for the 970. if the second slot is
> used, his bandwidth will not be 16x but 4x.
> The others slots are only PCI-E 3.0 1x ...
>
> ___
> 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

Re: [vfio-users] Passthrough USB PCI Controller

[Jayme Howard]

I'm doing exactly this with no significant problem.  The way I handle it is
that I've got a script that binds the specific card to vfio-pci at runtime,
and I call that as a part of my startup script for the VM.

/usr/local/bin/vfio-bind
#!/bin/bash

modprobe vfio-pci

for dev in "$@"; do
vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
device=$(cat /sys/bus/pci/devices/$dev/device)
if [ -e /sys/bus/pci/devices/$dev/driver ]; then
echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
fi
echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
done

Then I just add "-device vfio-pci,host=" to the args to qemu.
Works like a charm.  The script is called with the format ":06:00.0",
the args to qemu are "06:00.0".  Your address may vary, of course.

On Tue, Oct 25, 2016 at 6:11 AM, Andrei Grigore 
wrote:

> Hi,
>
> Does anyone know of an easy way to pass through a USB PCI controller in
> QEMU w/o libvirt? Since libvirt automatically binds the controller to VFIO,
> without it I get VFIO not found error messages.
>
> I am getting slightly better performance with a QEMU script rather than
> using virt-manager. I cannot bind them on boot since I have the same id for
> all USBs.
>
> Thanks!
>
> ___
> 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

Re: [vfio-users] Passthrough USB PCI Controller

[Jayme Howard]

I appreciate the patch, but it's not a great one for me to test,
personally.  My issue wasn't actually that I have two identical
controllers.  Rather, I have one specific controller that I sometimes want
to use on the host, so I don't want to assign it to the guest at boot of
the host.  That's why I actually use the script.  On a quick glance though
the patch looked solid to me, though I'm not a kernel dev.

On Tue, Oct 25, 2016 at 1:32 PM, Laszlo Ersek <ler...@redhat.com> wrote:

> On 10/25/16 16:30, Jayme Howard wrote:
> > I'm doing exactly this with no significant problem.  The way I handle it
> > is that I've got a script that binds the specific card to vfio-pci at
> > runtime, and I call that as a part of my startup script for the VM.
> >
> > /usr/local/bin/vfio-bind
> > #!/bin/bash
> >
> > modprobe vfio-pci
> >
> > for dev in "$@"; do
> > vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
> > device=$(cat /sys/bus/pci/devices/$dev/device)
> > if [ -e /sys/bus/pci/devices/$dev/driver ]; then
> > echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
> > fi
> > echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
> > done
> >
> > Then I just add "-device vfio-pci,host=" to the args to qemu.
> > Works like a charm.  The script is called with the format
> > ":06:00.0", the args to qemu are "06:00.0".  Your address may vary,
> > of course.
>
> I posted a kernel patch for this, and CC'd you guys on it. If you could
> test it, that would be great.
>
> The intended use is that you keep your current pci-stub.ids=... options,
> but add pci-stub.except=:03:00.0,... for those devices that you want
> pci-stub to ignore. This will cause :03:00.0 to be bound by the
> appropriate host driver, while the rest of the ID- and class-matched
> devices will be claimed by pci-stub (and therefore they'll be eligible
> for assignment, assuming all other conditions are met).
>
> If I misunderstood the original problem (~ having two identical PCI USB
> controllers and intending to assign only one of them), then my bad.
>
> Thanks
> Laszlo
>
>
> > On Tue, Oct 25, 2016 at 6:11 AM, Andrei Grigore <andrei@gmail.com
> > <mailto:andrei@gmail.com>> wrote:
> >
> > Hi,
> >
> > Does anyone know of an easy way to pass through a USB PCI controller
> > in QEMU w/o libvirt? Since libvirt automatically binds the
> > controller to VFIO, without it I get VFIO not found error messages.
> >
> > I am getting slightly better performance with a QEMU script rather
> > than using virt-manager. I cannot bind them on boot since I have the
> > same id for all USBs.
> >
> > Thanks!
> >
> >
> > ___
> > vfio-users mailing list
> > vfio-users@redhat.com <mailto:vfio-users@redhat.com>
> > https://www.redhat.com/mailman/listinfo/vfio-users
> > <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

Re: [vfio-users] Looking for recommendations for screen-switching

[Jayme Howard]

I do exactly what you described as your original solution, though I've got
a USB switch inline as well, because my monitor doesn't have USB
passthrough.

On Sun, Mar 19, 2017 at 9:14 AM, Patrick O'Callaghan  wrote:

> I have VFIO passthrough working with a Windows 10 VM, running on Fedora
> 25. Currently I have two cables running to my single monitor (one HDMI
> and one DVI), so switching back and forth means toggling a monitor
> setting. This does work, but is a bit clunky.
>
> BTW the mouse and keyboard also switch back and forth (this slightly
> surprised me but I'm not going to question it :-)
>
> I thought I could make this simpler by exchanging the DVI cable for
> another HDMI cable, both cables going into an HDMI switch and hence to
> the HDMI port on the monitor, with the idea of toggling back and forth.
> However this doesn't entirely work. I suspect that the switch powers
> off the input it's not using and this confuses Windows.
>
> Most of the discussion I've seen recommends Synergy, a software
> KB/mouse switcher, however this explicitly does not support video
> switching, i.e. it assumes you have a separate monitor for each machine
> (real or virtual), which is not the case here.
>
> The other option seems to be a physical KVM switch, but before shelling
> out more money I'd like to hear people's thoughts on this. What do you
> do to support a single monitor?
>
> poc
>
> ___
> 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

Re: [vfio-users] Console output on the host stops after launching a VM with vfio GPU

[Jayme Howard]

Are you backgrounding qemu?  If you just call it from the CLI, it won't
fork into the background and return the terminal to you.  You could launch
it with "nohup  &" and it should return the terminal to you.

On Mon, May 8, 2017 at 7:16 PM, Roman Mamedov  wrote:

> On Mon, 8 May 2017 16:58:22 -0700
> Nick S  wrote:
>
> > The host console is associated with emulated VGA and indeed becomes just
> a
> > useful window to grab/release your keyboard and mouse focus. It is used
> > during the boot process and displays whatever was the last output before
> > your OS switched to the passthrough GPU. I am not sure what you are
> trying
> > to fix here, it may be possible to completely get rid of this console and
> > use your passthrough card for boot as well, but overall it works as
> > designed. You normally need a separate display cable and port to see your
> > guest output.
>
> I feel you are reading that I was talking about the Qemu console window; I
> did
> not, I meant the actual prompt in the 80x25 text mode on a physical
> monitor.
>
> My monitor is connected to the host video card and that is OK. (I do not
> need
> to see my guest output on the monitor, VNC access to the guest OS is enough
> for my task).
>
> The host machine does not use Xorg, it boots into said text console only.
> I log-in and launch the shell script which starts the guest. After that,
> the content shown on the host's video card monitor stops updating
> (freezes),
> and all local access to the host machine via the connected
> monitor/keyboard is
> effectively lost until reboot. This is the problem. (Incidentally, trying
> to
> switch consoles with Alt-F1...Alt-FX does not work either). It does not
> blank
> out either, just whatever was last printed there stays displayed and frozen
> indefinitely.
>
> How can I keep the host video card and text console working while the guest
> is running (which uses another video card)?
>
> --
> With respect,
> Roman
>
> ___
> 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