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

    XO - enable PCI devices for pass-through - should it work already or not yet?

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    15 Posts 4 Posters 915 Views 4 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.
    • abudefA Offline
      abudef
      last edited by

      Dear fellow virtualizers,
      in the current Xen Orchestra + XCP-ng 8.3 combination, the switches for enabling PCI devices for pass-through have started to work. But it seems to do nothing? What is your experience? Should it work already or is this still a kind of taster preview?
      Thanks and have a nice day everyone!

      23da31f6-cb7f-470f-9a54-73fc123eba59-obrazek.png

      1 Reply Last reply Reply Quote 0
      • abudefA Offline
        abudef
        last edited by

        That's exactly it, thank you 👌 😉

        1533660b-c0eb-45b1-b81c-ae50d03a4f36-image.png

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

          Hi,

          Can you be more specific? "Doing nothing" means what is missing exactly? Thanks!

          Adding BenjiReis in the loop

          1 Reply Last reply Reply Quote 0
          • abudefA Offline
            abudef
            last edited by

            I click OK in the dialog and - nothing happens.

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

              Ping MathieuRA then.

              Can you open your browser console and see if you have any error?

              abudefA 1 Reply Last reply Reply Quote 0
              • abudefA Offline
                abudef @olivierlambert
                last edited by

                olivierlambert Yes, there is an error:
                a4222701-eaac-4899-8152-b923e7af4a2e-image.png

                MathieuRAM 1 Reply Last reply Reply Quote 0
                • MathieuRAM Offline
                  MathieuRA Vates 🪐 XO Team @abudef
                  last edited by

                  Hi abudef 🙂

                  how many host do you have in your pool?

                  abudefA 1 Reply Last reply Reply Quote 0
                  • abudefA Offline
                    abudef @MathieuRA
                    last edited by

                    Hi MathieuRA ,
                    There's only one host in the pool; all XCP-ng 8.3 patches installed, XO commit 6444f.

                    MathieuRAM 1 Reply Last reply Reply Quote 0
                    • abudefA Offline
                      abudef
                      last edited by

                      It behaves the same way in XOA 5.94.2

                      1 Reply Last reply Reply Quote 0
                      • MathieuRAM Offline
                        MathieuRA Vates 🪐 XO Team @abudef
                        last edited by

                        So the error is "normal".
                        XOA tries to evacuate your host before restarting it, but your host's VMs have "nowhere to go" since you don't have another host.
                        Are you using XO from sources?

                        abudefA P 2 Replies Last reply Reply Quote 0
                        • abudefA Offline
                          abudef @MathieuRA
                          last edited by

                          MathieuRA I understand that, it's the same as having to reboot a host with running VMs, right? However, there we have an option called Force reboot. Or simply notify the user that the settings have been saved and the host needs to be rebooted, etc.

                          I tried this with both Xen Orchestra Appliance and Xen Orchestra from source (versions see above).

                          MathieuRAM 1 Reply Last reply Reply Quote 0
                          • MathieuRAM Offline
                            MathieuRA Vates 🪐 XO Team @abudef
                            last edited by

                            abudef As workaround, you can run an XO locally, shutdown all your VMs from your host and toggle your PCI from your local XO.
                            Otherwise it's also possible doing it with command line.

                            In the modal, if we simply change the buttons like this: [Reboot, Force Reboot, Cancel], instead of [Ok, Cancel] would that be sufficient?

                            abudefA 1 Reply Last reply Reply Quote 0
                            • P Offline
                              Paolo @MathieuRA
                              last edited by

                              MathieuRA said in XO - enable PCI devices for pass-through - should it work already or not yet?:

                              So the error is "normal".
                              XOA tries to evacuate your host before restarting it, but your host's VMs have "nowhere to go" since you don't have another host.
                              Are you using XO from sources?

                              IMHO If there isn't a host where to evacuate the running VMs, the reboot procedure should simply notify the user and shutdown the VMs.

                              1 Reply Last reply Reply Quote 0
                              • abudefA Offline
                                abudef @MathieuRA
                                last edited by

                                MathieuRA said in XO - enable PCI devices for pass-through - should it work already or not yet?:

                                In the modal, if we simply change the buttons like this: [Reboot, Force Reboot, Cancel], instead of [Ok, Cancel] would that be sufficient?

                                Yeah, that would be great. And it would also be handy to add a feedback in case of the "Reboot" option if running VMs can't be evacuated.

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

                                  That's the "force reboot" button we have. I agree that ideally we should catch that and offer the force alternative reboot for the user telling him "your VM will be rebooted".

                                  1 Reply Last reply Reply Quote 0
                                  • abudefA Offline
                                    abudef
                                    last edited by

                                    That's exactly it, thank you 👌 😉

                                    1533660b-c0eb-45b1-b81c-ae50d03a4f36-image.png

                                    1 Reply Last reply Reply Quote 2
                                    • olivierlambertO olivierlambert marked this topic as a question on
                                    • olivierlambertO olivierlambert has marked this topic as solved on
                                    • First post
                                      Last post