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

    Truenas Scales VM failed to start

    Scheduled Pinned Locked Moved Solved Compute
    44 Posts 3 Posters 3.6k 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.
    • AtaxyaNetworkA Offline
      AtaxyaNetwork Ambassador @jag5cof
      last edited by

      @jag5cof I never use PCI passthrough myself, but you can see the docs here: https://docs.xcp-ng.org/compute/#pci-passthrough

      jag5cofJ 1 Reply Last reply Reply Quote 0
      • jag5cofJ Offline
        jag5cof @AtaxyaNetwork
        last edited by

        @AtaxyaNetwork the reference said "If you attempt to perform PCI passthrough on a system which does not have VT-d/IOMMU enabled, you may encounter the following error when you start the target virtual machine:

        Internal error: xenopsd internal error: Device.PCI.Cannot_add(_, _)

        On, my host servver, I have VT-d/IOMMU enabled

        AtaxyaNetworkA 1 Reply Last reply Reply Quote 0
        • AtaxyaNetworkA Offline
          AtaxyaNetwork Ambassador @jag5cof
          last edited by

          @jag5cof As I said, "The "Device or resource busy" let me think that the device you're using in the TrueNas's VM is already used in an other VM."

          You can't use the same PCI device on multiple VMs

          jag5cofJ 1 Reply Last reply Reply Quote 0
          • jag5cofJ Offline
            jag5cof @AtaxyaNetwork
            last edited by

            @AtaxyaNetwork what do you think my next step to resolve this issue. None of the other vm's are giving me this problem. VM's Windows 10, 3 Ubuntu and one debian.

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

              It means the PCI device you are trying to pass to this VM is already used, either by another VM, or by the Dom0 itself.

              jag5cofJ 1 Reply Last reply Reply Quote 0
              • jag5cofJ Offline
                jag5cof @olivierlambert
                last edited by

                @olivierlambert what is the fix action and how

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

                  I can't guess the device you are trying to passthrough and how/if it's used by another VM or the dom0.

                  The fix is to be sure no other VM is using this device (including the dom0). If you added a passthrough device, you know which one you added, and nobody else can guess it 🙂

                  jag5cofJ 1 Reply Last reply Reply Quote 0
                  • jag5cofJ Offline
                    jag5cof @olivierlambert
                    last edited by

                    @olivierlambert I know the other vm which are using the passthough. So do you know I can remove the passthough from the others vms

                    AtaxyaNetworkA 1 Reply Last reply Reply Quote 0
                    • AtaxyaNetworkA Offline
                      AtaxyaNetwork Ambassador @jag5cof
                      last edited by

                      @jag5cof I imagine it's something like:

                      • List the param of your VM with xe vm-param-list uuid=<uuid>
                      • Find the line like other-config:pci=0/0000:04:01.0
                      • Then you can remove with xe vm-param-remove other-config:pci=0/0000:04:01.0 uuid=<uuid>
                      jag5cofJ 2 Replies Last reply Reply Quote 0
                      • jag5cofJ Offline
                        jag5cof @AtaxyaNetwork
                        last edited by

                        @AtaxyaNetwork ok and thanks

                        1 Reply Last reply Reply Quote 0
                        • jag5cofJ Offline
                          jag5cof @AtaxyaNetwork
                          last edited by

                          @AtaxyaNetwork I'm gettin this error when I run this command

                          Required parameter not found: param-name
                          xe vm-param-remove other-config:pci=0/0000:03:00.0 uuid=vm#

                          I add the correct pci id and vm uuid

                          AtaxyaNetworkA 1 Reply Last reply Reply Quote 0
                          • AtaxyaNetworkA Offline
                            AtaxyaNetwork Ambassador @jag5cof
                            last edited by

                            @jag5cof Maybe xe vm-param-remove param-name=other-config param-key=pci=0/0000:03:00.0 uuid=<uuid> ?

                            jag5cofJ 1 Reply Last reply Reply Quote 0
                            • jag5cofJ Offline
                              jag5cof @AtaxyaNetwork
                              last edited by

                              @AtaxyaNetwork I got this error when I ran your cmd - Key pci=0/0000:03:00.0 is not in map

                              I aslo ran xl pci-assignable-list
                              0000:03:00.0

                              AtaxyaNetworkA 1 Reply Last reply Reply Quote 0
                              • AtaxyaNetworkA Offline
                                AtaxyaNetwork Ambassador @jag5cof
                                last edited by

                                @jag5cof I just discussed this with @olivierlambert, the right syntax is:
                                xe vm-param-remove param-name=other-config param-key=pci uuid=<VM UUID>

                                He will add the procedure to delete PCI passthrough in the docs 🙂

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

                                  I updated the doc, it's now available: https://docs.xcp-ng.org/compute/#detaching-a-pci-device

                                  jag5cofJ 1 Reply Last reply Reply Quote 1
                                  • jag5cofJ Offline
                                    jag5cof @AtaxyaNetwork
                                    last edited by

                                    @AtaxyaNetwork I appreciate you working with me on this. It is a learn experience.

                                    1 Reply Last reply Reply Quote 0
                                    • jag5cofJ Offline
                                      jag5cof @olivierlambert
                                      last edited by

                                      @olivierlambert I'm still getting this error - Key pci is not in map

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

                                        Check if you have the PCI parameter enabled on the VM first:

                                        xe vm-param-list uuid=<VM UUID>

                                        jag5cofJ 1 Reply Last reply Reply Quote 0
                                        • jag5cofJ Offline
                                          jag5cof @olivierlambert
                                          last edited by

                                          @olivierlambert What line am I'm looking for on the vm after the
                                          cmd is run

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

                                            The other-config line 🙂 Paste it here

                                            jag5cofJ 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post