Can't you make the script check if it windows or Linux and skip if it's Linux?
Best Regards,
Strahil NikolovOn Mar 19, 2019 23:02, Darin Schmidt <darinschm...@gmail.com>
wrote:
>
> You also need to have this code hooked in:
> cd /usr/libexec/vdsm/hooks/before_vm_start/
> vi 99_mask_kvm
>
> #!/usr/bin/python2
>
> import hooking
> domxml = hooking.read_domxml()
>
> hyperv = domxml.getElementsByTagName('hyperv')[0]
> smm = domxml.createElement('vendor_id')
> smm.setAttribute('state', 'on')
> smm.setAttribute('value', '1234567890ab')
> hyperv.appendChild(smm)
>
> features = domxml.getElementsByTagName('features')[0]
> kvm = domxml.createElement('kvm')
> hidden = domxml.createElement('hidden')
> hidden.setAttribute('state', 'on')
> kvm.appendChild(hidden)
> features.appendChild(kvm)
>
> hooking.write_domxml(domxml)
>
>
> only problem now is that I cant boot a linux VM with the vendor_is portion
> there......
>
> On Mon, Mar 18, 2019 at 3:30 PM Darin Schmidt <darinschm...@gmail.com> wrote:
>>
>> Seems that the system has to be running with bios Q35 UEFI. Standard bios
>> does not work. System is operational now.
>>
>> On Mon, Mar 18, 2019, 6:30 AM Darin Schmidt <darinschm...@gmail.com> wrote:
>>>
>>> Still no luck getting the gtx 1080 to enable inside the VM. I see the code
>>> is being generated in the xml with the hook. But I still get error code 43.
>>> Someone mentioned doing it with eufi bios and that worked for them. So when
>>> I get back from work today, perhaps ill give that a try.
>>>
>>> On Mon, Mar 18, 2019, 6:10 AM Darin Schmidt <darinschm...@gmail.com> wrote:
>>>>
>>>> I have gotten the system to see the card, its in device manager. The
>>>> problem seems to be that I cannot use it in the VM because from what I
>>>> have been finding out is that it gets and error code 43. Nvidia drivers
>>>> disable the card if it detects that its being used in a VM. I have found
>>>> some code to use to hook it into the xml before_vm_starts.
>>>>
>>>> 99_mask_kvm
>>>> #!/usr/bin/python2
>>>>
>>>> import hooking
>>>> domxml = hooking.read_domxml()
>>>>
>>>> hyperv = domxml.getElementsByTagName('hyperv')[0]
>>>> smm = domxml.createElement('vendor_id')
>>>> smm.setAttribute('state', 'on')
>>>> smm.setAttribute('value', '1234567890ab')
>>>> hyperv.appendChild(smm)
>>>>
>>>> features = domxml.getElementsByTagName('features')[0]
>>>> kvm = domxml.createElement('kvm')
>>>> hidden = domxml.createElement('hidden')
>>>> hidden.setAttribute('state', 'on')
>>>> kvm.appendChild(hidden)
>>>> features.appendChild(kvm)
>>>>
>>>> hooking.write_domxml(domxml)
>>>>
>>>>
>>>> I am currently reinstalling the drivers to see if this helps.
>>>>
>>>> kvm off and vender_id is now in the xml code that get generated when the
>>>> VM is started. Im going off of examples Im finding online. Perhaps I just
>>>> need to add the 10de to it instead of some generic # others are using.
>>>>
>>>> On Mon, Mar 18, 2019 at 6:02 AM Nisim Simsolo <nsims...@redhat.com> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Vendor ID of Nvidia is usually 10de.
>>>>> You can locate 'vendor ID:_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VH27ZEYJHUE5XQ72FPE26YLOQBNHIXW4/
