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

    Importing OVA - “Device Already Exists”

    Scheduled Pinned Locked Moved Xen Orchestra
    24 Posts 5 Posters 4.5k 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

      @planedrop are you importing this OVA from VMware out of curiosity?

      planedropP 1 Reply Last reply Reply Quote 1
      • planedropP Offline
        planedrop Top contributor @olivierlambert
        last edited by

        @olivierlambert Yes, that is correct, it's an exported OVA from VMWare using their CLI based OVA tool (since you can't do it in the GUI anymore). We are working with a vendor to validate their platform on XCP-ng so we can hopefully ditch VMWare and put everything on XCP-ng which is where the rest of our VMs reside.

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

          Would you like to participate to a very early beta test of our new capability to import the VM from VMware directly from VMware API to XCP-ng? (using Xen Orchestra)

          planedropP 1 Reply Last reply Reply Quote 0
          • planedropP Offline
            planedrop Top contributor @olivierlambert
            last edited by

            @olivierlambert I would be interested, however this is a production environment, so what are the risks of that? Does it require a beta version of XOA to be installed?

            Thanks for the help by the way, we aren't in some major rush so I don't mind tinkering a bit, just can't have anything cause stability issues.

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

              Please open a ticket so we can see in more depth what would be the best options 🙂

              planedropP 1 Reply Last reply Reply Quote 0
              • planedropP Offline
                planedrop Top contributor @olivierlambert
                last edited by

                @olivierlambert Will do! I will try to do that today, might be next week though, busy week so far at work lol.

                Thanks!

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

                  No worries, next week is fine 🙂 Busy here too 😉

                  planedropP 1 Reply Last reply Reply Quote 0
                  • planedropP Offline
                    planedrop Top contributor @olivierlambert
                    last edited by

                    @olivierlambert Just so you are aware, I just sent in a ticket for it a few minutes ago.

                    Thanks again for the help!

                    1 Reply Last reply Reply Quote 1
                    • T Offline
                      trent234
                      last edited by

                      FYI this same error occurs when I try to assign 9 virtual network interfaces for a new VM as well. So its not just a limit on drives.

                      planedropP 1 Reply Last reply Reply Quote 0
                      • planedropP Offline
                        planedrop Top contributor @trent234
                        last edited by

                        @trent234 Interesting, good to know. I do know that XCP-ng only officially supports 7 network interfaces, so not really surprised by that. It supports more VHDs though so feel like I shouldn't be seeing this error.

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