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

    PCI Passthorugh INTERNAL_ERROR

    Scheduled Pinned Locked Moved Management
    13 Posts 4 Posters 205 Views 3 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      Oh sorry, I thought you were on the sources 🙂 In that case, you just have to provide the XOA channel you are on, that's enough 🙂

      Regarding your issue, it's hard to tell, it seems you have a problem at the host level. Have you enabled IOMMU in the bios?

      T 1 Reply Last reply Reply Quote 0
      • T Offline
        TITUS MAXIMUS @olivierlambert
        last edited by

        @olivierlambert I have SR-IOV enabled in the BIOS.

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

          What's the result of lspci on your machine?

          Also pinging @Team-Hypervisor-Kernel

          1 Reply Last reply Reply Quote 0
          • TeddyAstieT Offline
            TeddyAstie Vates 🪐 XCP-ng Team Xen Guru
            last edited by

            Not a Xen issue.
            This seems to be either a configuration issue (knowing /opt/xensource/libexec/xen-cmdline --get-dom0 may help) causing a issue in XAPI (@Team-XAPI-Network).

            Maybe crashing in xapi/pciops.ml#L71-L80 or xapi/xapi_pci_helpers.ml#L179-L207.

            T 1 Reply Last reply Reply Quote 0
            • T Offline
              TITUS MAXIMUS @TeddyAstie
              last edited by TITUS MAXIMUS

              @TeddyAstie I ran /opt/xensource/libexec/xen-cmdline --get-dom0 on the host and it didn't return anything. 😞

              EDIT: I also want to mention that I upgraded from 8.2 to 8.3 is that makes any difference. But I only started to testing passing through devices after I upgraded.

              A 2 Replies Last reply Reply Quote 0
              • A Offline
                andriy.sultanov Vates 🪐 XAPI & Network Team @TITUS MAXIMUS
                last edited by

                @TITUS-MAXIMUS Could you please attach /var/log/xensource.log from the time of the error? Would be very useful to have a backtrace from where the error occurs 🙂

                T 1 Reply Last reply Reply Quote 0
                • A Offline
                  andriy.sultanov Vates 🪐 XAPI & Network Team @TITUS MAXIMUS
                  last edited by

                  @TITUS-MAXIMUS --get-dom0 being empty means no PCI devices were hidden from dom0 either, did you follow this step of the guide? https://docs.xcp-ng.org/compute/#2-tell-xcp-ng-not-to-use-this-device-id-for-dom0

                  1 Reply Last reply Reply Quote 0
                  • T Offline
                    TITUS MAXIMUS @andriy.sultanov
                    last edited by TITUS MAXIMUS

                    @andriy.sultanov Here are the logs. To your second question. I thought I was able to pass through devices from XO and then the host reboots. Maybe I misunderstood how this worked. Are you saying I need to do this in the console and then XO?

                    Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] PCI.get_dom0_access_status R:1f40280dd69a failed with exception Server_error(INTERNAL_ERROR, [ 126 ])
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] Raised Server_error(INTERNAL_ERROR, [ 126 ])
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 1/15 xapi Raised at file ocaml/xapi-aux/helper_process.ml, line 17
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 2/15 xapi Called from file ocaml/xapi/pciops.ml, line 73
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 3/15 xapi Called from file ocaml/xapi/pciops.ml, line 95
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 4/15 xapi Called from file ocaml/xapi/pciops.ml, line 99
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 5/15 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 6/15 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 7/15 xapi Called from file ocaml/xapi/xapi_pci_helpers.ml, line 213
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 8/15 xapi Called from file ocaml/xapi/message_forwarding.ml, line 141
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 9/15 xapi Called from file ocaml/xapi/rbac.ml, line 188
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 10/15 xapi Called from file ocaml/xapi/rbac.ml, line 197
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 11/15 xapi Called from file ocaml/xapi/server_helpers.ml, line 77
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 12/15 xapi Called from file ocaml/xapi/server_helpers.ml, line 96
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 13/15 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 14/15 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 15/15 xapi Called from file ocaml/libs/log/debug.ml, line 250
Jul  7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace]
                    A 1 Reply Last reply Reply Quote 0
                    • A Offline
                      andriy.sultanov Vates 🪐 XAPI & Network Team @TITUS MAXIMUS
                      last edited by

                      @TITUS-MAXIMUS You are correct. Sorry, the command to run is /opt/xensource/libexec/xen-cmdline --get-dom0 xen-pciback.hide - does this return anything? what's the return code of the command?

                      T 1 Reply Last reply Reply Quote 0
                      • T Offline
                        TITUS MAXIMUS @andriy.sultanov
                        last edited by

                        @andriy.sultanov After running that command I didn't have anything returned.

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