XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    Unable to export OVA

    Xen Orchestra
    7
    62
    1659
    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.
    • Darkbeldin
      Darkbeldin Vates 🪐 Pro Support Team 💡 @Danp last edited by

      @Danp So export of a bigger VM failed through XOA with memory being at max
      b654919d-2923-4e96-89d1-5c3930ecaec1-image.png
      Testing it with XO from sources now

      1 Reply Last reply Reply Quote 0
      • olivierlambert
        olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼 last edited by

        @Danp can you try on latest commit on master?

        Danp 1 Reply Last reply Reply Quote 0
        • Danp
          Danp Top contributor 💪 @olivierlambert last edited by

          @olivierlambert Appears to be working correctly on the latest commit. 👍

          1 Reply Last reply Reply Quote 1
          • olivierlambert
            olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼 last edited by

            Yay! @florent : your fix seems to be working 🙂

            Danp 2 Replies Last reply Reply Quote 0
            • Danp
              Danp Top contributor 💪 @olivierlambert last edited by

              @olivierlambert While exporting a stopped VM, it's not possible to start the VM until the export finishes. So it might be good to add some form of warning message.

              1 Reply Last reply Reply Quote 0
              • olivierlambert
                olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼 last edited by

                That's a behavior you have for XVA exports too, since it XenServer exists (you can export a disk while it's live, because… that would export garbage)

                Danp 1 Reply Last reply Reply Quote 0
                • Danp
                  Danp Top contributor 💪 @olivierlambert last edited by

                  @olivierlambert Ran into an issue when I tried importing the newly exported OVA. Here's the error shown in the browser console --

                  importVms 20230125T190404Z - Server.ova Error: Unsupported file, high order bits are too high in field grain directory address
                      a vmdk-read-table.js:24
                      i vmdk-read-table.js:49
                      default vmdk-read-table.js:30
                      parseOVAFile ova-read.js:237
                      u index.js:24
                      i index.js:2
                      s index.js:2
                      s index.js:2
                      s index.js:2
                      u index.js:27
                      default index.js:23
                      D index.js:191
                      C index.js:24
                      i index.js:24
                      x index.js:24
                      x index.js:24
                      j index.js:188
                      r index.js:260
                      mapPlus utils.js:175
                      Lodash 2
                      mapPlus utils.js:175
                      r index.js:252
                      C index.js:24
                      i index.js:24
                      x index.js:24
                      x index.js:24
                      B index.js:268
                      value index.js:206
                  index.js:1757:16
                  
                  olivierlambert florent 2 Replies Last reply Reply Quote 0
                  • Danp
                    Danp Top contributor 💪 @olivierlambert last edited by

                    @olivierlambert One way around that would be to optionally take a snapshot even if the VM is stopped.

                    1 Reply Last reply Reply Quote 0
                    • olivierlambert
                      olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼 @Danp last edited by

                      @Danp That's for @florent

                      1 Reply Last reply Reply Quote 0
                      • florent
                        florent Vates 🪐 XO Team 🔭 @Danp last edited by

                        @Danp hi

                        what is the mdisk size of the VM ? we're limited to 2TB per disk

                        Danp 1 Reply Last reply Reply Quote 0
                        • Danp
                          Danp Top contributor 💪 @florent last edited by

                          @florent Nothing large. Either 10 or 20GB. I'm thinking it's due to the same issue as here.

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