Hiding hypervisor from guest to prevent Nvidia Code 43


  • XCP-ng Team

    It's XCP-ng not "XCP-NV" 😉 We'll continue to track if it's possible to do so one day.



  • @olivierlambert oops.. typo. Apologies


  • XCP-ng Team

    @olivierlambert @imtrobin I had worked on CPUID for exposing temperature data of CPU to Guest (Dom0). May be we can use same.

    # cpuid | grep -I hypervisor_id
       hypervisor_id = "Microsoft Hv"
    

    Is this the one which should be hidden?


  • XCP-ng Team

    I'm not entirely sure about that, I need to ask one Xen dev.



  • This post is deleted!


  • @r1 said in Hiding hypervisor from guest to prevent Nvidia Code 43:

    @olivierlambert @imtrobin I had worked on CPUID for exposing temperature data of CPU to Guest (Dom0). May be we can use same.

    # cpuid | grep -I hypervisor_id
       hypervisor_id = "Microsoft Hv"
    

    Is this the one which should be hidden?

    I'm have no idea if that is enough, but maybe. How can we try this? For kvm , they do this

    https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#.22Error_43:_Driver_failed_to_load.22_on_Nvidia_GPUs_passed_to_Windows_VMs



  • What is the current status on this? We are hoping for this soonish, and if it isn't coming at all or not for a long time, then we need to plan a migration to another platform.

    Our use case is for business, but we are not a very big business and do not wish to spend thousands on buying Quadro cards when much cheaper GTX and other consumer cards will do the job perfectly if it wasn't for Nvidia's artificial limitation.

    We run a custom program for Kitchen Design as RemoteApps under an RDS setup. At this point, we are running under Quadro 4000 cards, as we already had them, but due to this, I cannot upgrade to Server 2019 as there are no drivers. To upgrade we have to upgrade cards, and the best bang for buck cards in our use, are P4000 which do run under Server 2019, but are $1000+ each. WE want to have 2 cards in each server, totalling 4 cards. We can get even better bang for buck on some RTX 2070's or the like for nearly half the cost.

    The only thing stopping us is this stupid Code 43 "bug".

    We are willing to wait as we haven't quite hit the limits of our current setup, but we are heading close to it, and we need to plan our next move. I love XCP-ng and honestly cannot fault it for anything, other than having the capability to hide the fact the VM is a vm.

    We have already ran a test setup on Proxmox and the Code 43 fix works perfectly.


  • XCP-ng Team

    If it's for business, why not trying to pour some resources to make this work? 🙂 It's Open Source with pro support backed, so there's 2 approaches:

    • contribute to speed up the process
    • pay to get someone (individual or company) to do it

    One priority can't be a priority for everyone. But you can have a influence on that with 2 different levers.



  • I've been using Xcp-NG and Xen for awhile now and unfortunately i have had to change everything from Xen to Esxi because this feature is not there. hypervisor.cpuid.v0=false is the only line I have to enter for it to hide the GPU's in all our servers.

    It's a shame as i understand it isn't a priority but this has been asked for many years from the google searches i have done. When this feature is available I will come back to Xen unfortunately until then I have to use Esxi


  • XCP-ng Team

    Hi!

    Thanks for the feedback, my previous message still apply 🙂


Log in to reply
 

XCP-ng Pro Support

XCP-ng Pro Support