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

    Cannot Import VMDK Through Import > Disk (migrating from ESXi, all methods not working)

    Xen Orchestra
    3
    17
    574
    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.
    • planedropP
      planedrop @olivierlambert
      last edited by

      @olivierlambert Yes, I actually have a ticket open with this, but wanted to see if anyone public had any ideas too.

      Ticket is Ticket#7711465 and has more info on the exact error I am seeing when trying the direct import feature.

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

        Perfect thanks 🙂

        1 Reply Last reply Reply Quote 0
        • C
          caponate
          last edited by

          Was this ever resolved? I noticed I can no longer import VHD files (that's all we have, we were a hyper v shop) through XOA or XO from the sources. Both of my servers are on the latest patches. It does the same thing with the spinning circle but I can see activity on my NIC that is uploading something. Nothing useful in the log that I could see. I'm not super well versed in Xen Orchestra yet so go easy on me 🙂

          I spun up a brand new XOA last night and it still didn't work.
          1399d3db-dbdd-4fa8-82f2-f8b47b1394f8-image.png

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

            Hi,

            XOA on latest full up to date?

            C 1 Reply Last reply Reply Quote 0
            • C
              caponate @olivierlambert
              last edited by

              @olivierlambert Realized it was on stable, just updated it to latest but now I just get an error with no logs 07dfece8-1230-4f8c-9a17-f54a03979c14-image.png

              83ea446d-4404-4d6f-8516-821a32834385-image.png

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

                Is it a generic VHD that we could grab somewhere to see if we can reproduce here?

                C 1 Reply Last reply Reply Quote 0
                • C
                  caponate @olivierlambert
                  last edited by

                  @olivierlambert No, it is our unifi controller VM so it has some private info. I tried it this afternoon again with a different VHD and had the same result, this time a VHD I exported from our veeam backups, which I have done with XOA before without issue. Should I create my own thread?

                  I also just tried it again from my macbook with safari, same result. Weird how when I go to show logs, there is nothing.

                  Thank you so much for your assistance!

                  planedropP 1 Reply Last reply Reply Quote 0
                  • planedropP
                    planedrop @caponate
                    last edited by

                    @caponate Have you tried importing it via XCP-ng center? It's older but may be worth a try.

                    C 1 Reply Last reply Reply Quote 0
                    • C
                      caponate @planedrop
                      last edited by caponate

                      @planedrop Is that even possible anymore? I cannot find the option to do that, it has been a long time since I used xcp-ng center.

                      Just tested it on my main desktop at home, I can import a generic windows server VHD I downloaded from microsoft. But not a copy of an Azure VM that I downloaded the other day (but it boots in hyper-V)... Very weird. I will try downloading it again and report back.

                      C 1 Reply Last reply Reply Quote 0
                      • C
                        caponate @caponate
                        last edited by caponate

                        Here is what I get when trying to upload the exported vhd:

                        Tried with 3 different browsers just in case.

                        d5440a17-3ed3-490c-a1d0-1cfd312ad240-image.png

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

                          Just to double check: are you in HTTPS in your browser?

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

                            You could also try to import the VHD directly with xe on the host, and see if it works.

                            1 Reply Last reply Reply Quote 0
                            • C
                              caponate @olivierlambert
                              last edited by

                              @olivierlambert Yep. And I confirmed it today, it appears it is JUST the vhd files exported from Azure that don't work. I don't know what in the hell they do to them, but there's something messed up about them. Maybe I will export a generic one and post it for analysis.

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

                                Interesting 🤔 Are you sure they are VHD and not VHDX? If it's possible to access the problematic VHD, we could take a look and see what's inside in terms of structure and headers.

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