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

    Tesla xenctrlext.unix_error Device or resource is busy

    Scheduled Pinned Locked Moved Unsolved Hardware
    11 Posts 2 Posters 506 Views 2 Watching
    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.
    • K Offline
      kuznetcoff777
      last edited by

      Hi! I have XCP-ng release 8.2.1 and tesla, only one videocard (becasue of x8da3 motherboard, we have now network card and tesla without any videocard for video-kvm access)

      3df5afbc-593c-4abb-a6ad-51d12c1cda72-изображение.png

      6c6c2500-f09a-4ef9-9be2-a8d9e9015f6c-изображение.png

      I checked all VMs, no one more have this gpu, only this VM and it does not start. Can you please tell how to solve this problem?

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

        The GPU is probably not hidden to the Dom0

        K 1 Reply Last reply Reply Quote 1
        • K Offline
          kuznetcoff777 @olivierlambert
          last edited by kuznetcoff777

          @olivierlambert
          Yep, added excusion /opt/xensource/libexec/xen-cmdline --set-dom0 "xen-pciback.hide=(0000:05:00.0)" (https://docs.xcp-ng.org/compute/)
          worked llike a sharm, thanks.

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

            Note that PCI passthrough will be entirely exposed in XO with XCP-ng 8.3, no need for the CLI anymore 🙂

            K 1 Reply Last reply Reply Quote 0
            • olivierlambertO olivierlambert marked this topic as a question on
            • olivierlambertO olivierlambert has marked this topic as solved on
            • K Offline
              kuznetcoff777 @olivierlambert
              last edited by kuznetcoff777

              @olivierlambert
              After restart VM it began to show the same error, just like hide list is empty. If any way to check this hide list?

              May 22 11:10:57 xcp kernel: [86647.738094] pciback 0000:05:00.0: timed out waiting for pending transaction; performing function level reset anyway
              May 22 11:10:58 xcp kernel: [86648.986119] pciback 0000:05:00.0: not ready 1023ms after FLR; waiting
              May 22 11:10:59 xcp kernel: [86650.042116] pciback 0000:05:00.0: not ready 2047ms after FLR; waiting
              May 22 11:11:02 xcp kernel: [86652.346147] pciback 0000:05:00.0: not ready 4095ms after FLR; waiting
              May 22 11:11:06 xcp kernel: [86656.698127] pciback 0000:05:00.0: not ready 8191ms after FLR; waiting
              May 22 11:11:14 xcp kernel: [86665.146149] pciback 0000:05:00.0: not ready 16383ms after FLR; waiting
              ...
              May 22 11:12:08 xcp kernel: [86718.394184] pciback 0000:05:00.0: not ready 65535ms after FLR; giving up
              
              
              
              1 Reply Last reply Reply Quote 0
              • olivierlambertO Online
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Maybe this will ring a bell to anyone around here?

                1 Reply Last reply Reply Quote 0
                • K Offline
                  kuznetcoff777
                  last edited by

                  Can someone please delete Solved sign? Cause problem still persists...
                  If any way to check what is in hide list?

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO olivierlambert has marked this topic as unsolved on
                  • olivierlambertO Online
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    Put back as unresolved 🙂

                    1 Reply Last reply Reply Quote 1
                    • K Offline
                      kuznetcoff777
                      last edited by

                      [11:12 xcp ~]# dmesg | grep pciback
                      [    0.000000] Command line: root=LABEL=root-apezjy ro nolvm hpet=disable rd.auto console=hvc0 console=tty0 quiet vga=785 splash plymouth.ignore-serial-consoles xen-pciback.hide=(0000:05:00.0)
                      [    3.313418] Kernel command line: root=LABEL=root-apezjy ro nolvm hpet=disable rd.auto console=hvc0 console=tty0 quiet vga=785 splash plymouth.ignore-serial-consoles xen-pciback.hide=(0000:05:00.0)
                      
                      [20:49 xcp ~]# lspci -s 0000:05:00.0 -v
                      05:00.0 3D controller: NVIDIA Corporation TU104GL [Tesla T4] (rev ff) (prog-if ff)
                              !!! Unknown header type 7f
                              Kernel driver in use: pciback
                      

                      Seems to be that it was on boot in exception and now it is still in. But VM cannot get it...

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

                        You are only hidding one PCI address. In your dom0, with a lspci command, double check if you have other Nvidia references

                        1 Reply Last reply Reply Quote 0
                        • K Offline
                          kuznetcoff777
                          last edited by

                          Yep, only one, cause one tesla onboard, no any other video devices (maybe it is a problem)

                          [20:53 xcp ~]# lspci | grep -i nvidia
                          05:00.0 3D controller: NVIDIA Corporation TU104GL [Tesla T4] (rev ff)
                          
                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post