Cannot Import VMDK Through Import > Disk (migrating from ESXi, all methods not working)
-
@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.
-
Perfect thanks
-
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.
-
Hi,
XOA on
latestfull up to date? -
@olivierlambert Realized it was on stable, just updated it to latest but now I just get an error with no logs
-
Is it a generic VHD that we could grab somewhere to see if we can reproduce here?
-
@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!
-
@caponate Have you tried importing it via XCP-ng center? It's older but may be worth a try.
-
@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.
-
Here is what I get when trying to upload the exported vhd:
Tried with 3 different browsers just in case.
-
Just to double check: are you in HTTPS in your browser?
-
You could also try to import the VHD directly with
xeon the host, and see if it works. -
@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.
-
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.
