XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    nVidia Tesla P4 for vgpu and Plex encoding

    Scheduled Pinned Locked Moved
    Compute
    13
    55
    9.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • splastunovS
      splastunov @austinw
      last edited by

      @austinw no licenses, but a lot of troubles.....

      M 1 Reply Last reply Reply Quote 0
      • M
        mohammadm @splastunov
        last edited by

        @splastunov said in nVidia Tesla P4 for vgpu and Plex encoding:

        @austinw no licenses, but a lot of troubles.....

        Curious, what troubles?

        splastunovS 1 Reply Last reply Reply Quote 0
        • splastunovS
          splastunov @mohammadm
          last edited by

          @mohammadm
          I'm talking now about vGPU not passthrough

          1. old drivers
          2. no way to monitor GPU load
          3. Sometimes the GPU on Dom0 stops responding and the only thing that can be done to solve this problem is to reboot the entire server with all the virtual machines on it.
            and etc.... do not remember all troubles I had with it
          M A 2 Replies Last reply Reply Quote 0
          • M
            mohammadm @splastunov
            last edited by

            @splastunov said in nVidia Tesla P4 for vgpu and Plex encoding:

            @mohammadm
            I'm talking now about vGPU not passthrough

            1. old drivers
            2. no way to monitor GPU load
            3. Sometimes the GPU on Dom0 stops responding and the only thing that can be done to solve this problem is to reboot the entire server with all the virtual machines on it.
              and etc.... do not remember all troubles I had with it

            I installed the Firepro S7150x2 yesterday without any issues. It's been about 24 hours, so far no issues. I do agree I am missing the nvidia-smi command to get a better overview.

            Why is the support regarding vGPU so bad and mostly outdated 😞

            1 Reply Last reply Reply Quote 0
            • olivierlambertO
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              I will have the opportunity to discuss more with AMD (on a regular basis, for some reasons), I'll try to see if I can connect to their GPU division 🙂

              J 1 Reply Last reply Reply Quote 1
              • A
                austinw @splastunov
                last edited by

                @splastunov Dom0 would need to have a vGPU in this scenario?

                1 Reply Last reply Reply Quote 0
                • J
                  JamesG @olivierlambert
                  last edited by

                  @olivierlambert As mentioned in another thread...Intel Flex GPU's seem primed for this. nVidia is closed and license greedy. AMD seems a little lost and wandering. Intel has said, "No licensing...Just use it." but they require some development.

                  It should be relatively easy to incorporate the Intel Flex GPU's, but I'm not sure if the newer kernels are required. That might be where the wheels fall off for now.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mohammadm @JamesG
                    last edited by

                    @JamesG This would indeed be awesome! I would prefer going the Intel route. Any contacts there @olivierlambert ?

                    J 1 Reply Last reply Reply Quote 0
                    • J
                      JamesG @mohammadm
                      last edited by

                      From my perspective, there's literally money on the ground for any virtualization platform to pick up VDI with Intel. The GPU's are affordable and performant for VDI work. They currently work with Openshift and Proxmox is at work on it.

                      1 Reply Last reply Reply Quote 2
                      • stormiS
                        stormi Vates 🪐 XCP-ng Team
                        last edited by

                        @splastunov why do you extract the vgpu RPM rather than just installing the RPM directly?

                        1 Reply Last reply Reply Quote 1
                        • H
                          high-voltages
                          last edited by

                          I am currently trying to get a NVIDIA Telsa M10 working with the latest updated Xcp-ng 8.2.1 Build Date 2024-07-17.

                          The Drivers "NVIDIA-vGPU-xenserver-8-550.54.10.x86_64.rpm" are installed and the system was rebooted. Now it is possible to select a vGPU via XOA for the VM.

                          Further the extracted vgpu file from the CitrixHypervisor-8.2.0-install-cd.iso was copied to /usr/lib64/xen/bin/vgpu and is executable.

                          The Start of the VM exited with:

                          "FAILED_TO_START_EMULATOR(OpaqueRef:0cc388f0-b606-469d-b68c-b4713c7f4abb, vgpu, Daemon exited unexpectedly)
                          "

                          Is there someone who has solved this Problem?

                          Platform:
                          HPE DL380 Gen10

                          msupportM 1 Reply Last reply Reply Quote 0
                          • msupportM
                            msupport @high-voltages
                            last edited by

                            @high-voltages

                            download XenServer iso file (https://www.xenserver.com/downloads | XenServer8_2024-06-03.iso)
                            copy the file (vgpu-7.4.13-1.xs8.x86_64.rpm) in the packages directory ! Do not use CitrixHypervisor-8.2.0-install-cd file vgpu-7.4.8-1.x86_64
                            unpack file vgpu-7.4.13-1.xs8.x86_64
                            copy the file \usr\lib64\xen\bin\vgpu (size 129KB) to \usr\lib64\xen\bin\ on your XCP-NG host (chmod 755)

                            stormiS H 2 Replies Last reply Reply Quote 1
                            • stormiS
                              stormi Vates 🪐 XCP-ng Team @msupport
                              last edited by

                              Why unpacking and making manual changes to the filesystem instead of installing the RPM directly?

                              1 Reply Last reply Reply Quote 0
                              • H
                                high-voltages @msupport
                                last edited by

                                Thanks...

                                I tried at first the driver from above:
                                NVIDIA-GRID-CitrixHypervisor-8.2-550.54.10-550.54.14-551.61
                                what doesn’t work.
                                After this I have found the newer Version:
                                NVIDIA-GRID-CitrixHypervisor-8.2-550.54.16-550.54.15-551.78
                                Now the Error on VM startup does not came up and the driver installation in the VM works.

                                The Driver packages what are specially for Xenserver8 are not installable on the Xcp-NG Version 8.2.1 because the different Base "https://xcp-ng.org/forum/post/80461https://xcp-ng.org/forum/post/80461"

                                now I get one VM working with a vGPU but a second one does not detect the mapped vGPU and the windows driver cant be installed
                                I am currently not sure why this happens, because a copy of the working one with another vGPU config will work.
                                The Xentools and Windowsversions are the same and the template also

                                the vGPU rpm is installable without any problems😊

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post