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

    Cannot import a large VHD using Import Disk option

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    8 Posts 3 Posters 1.5k Views 1 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.
    • D Offline
      DeOccultist
      last edited by

      I'm running XO Community Edition xo-server 5.74.0, xo-web 5.77.0

      When I drag and drop a VHD disk that is 6GB it imports fine. But when I try to drag and drop in a 97GB VHD disk it says "an error has occurred" but there are no errors in Settings -> Logs.

      Is there a disk size limit when importing via the XO web interface?

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

        Hi!

        VHD import is partly managed by the browser. Check your browser console for errors 🙂

        D 1 Reply Last reply Reply Quote 0
        • D Offline
          DeOccultist @olivierlambert
          last edited by

          @olivierlambert Thanks.
          I see the problem now, it has to do with the capital extension .VHD which is the default when creating the image with disk2vhd.exe .
          It works when I rename it to lowercase vhd.

          This is the error when dropping in a *.VHD file.

          index.js:111 Uncaught TypeError: Cannot read property 'file' of undefined
              at index.js:111
              at Array.map (<anonymous>)
              at index.js:111
              at r (patch-react.js:22)
              at g.render (ReactCompositeComponent.js:42)
              at l._renderValidatedComponentWithoutOwnerOrContext (ReactCompositeComponent.js:796)
              at l._renderValidatedComponent (ReactCompositeComponent.js:824)
              at l._updateRenderedComponent (ReactCompositeComponent.js:743)
              at l._performComponentUpdate (ReactCompositeComponent.js:721)
              at l.updateComponent (ReactCompositeComponent.js:642)
          
          nraynaudN 1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Interesting bug. I think we can fix it easily (we'll, @nraynaud will tell 😛 )

            1 Reply Last reply Reply Quote 0
            • nraynaudN Offline
              nraynaud XCP-ng Team @DeOccultist
              last edited by

              @deoccultist Thanks for the report, the fix is done, you can follow its route to a release here: https://github.com/vatesfr/xen-orchestra/pull/5574

              Nicolas

              nraynaud opened this pull request in vatesfr/xen-orchestra

              closed fix(import/disk): allow uppercase extensions #5574

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

                That was fast!! Thanks @nraynaud 👍

                nraynaudN 1 Reply Last reply Reply Quote 0
                • nraynaudN Offline
                  nraynaud XCP-ng Team @olivierlambert
                  last edited by

                  @olivierlambert actually I saw the messages a few minutes before being tagged, and I was looking at the code by the time I got tagged.

                  D 1 Reply Last reply Reply Quote 1
                  • D Offline
                    DeOccultist @nraynaud
                    last edited by

                    @nraynaud @olivierlambert Thanks guys!

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