from Hyper-V
-
@McHenry Maybe this old post helps Error importing large vhd file. It also links to the documentation on how to Migrate to XCP-ng from Hyper-V, but I guess you already read that.
-
A filename MUST be:
- in the format
<UUID>.vhd(you MUST have the .vhd extension!) - use dynamic VHD format
- in the format
-
If you have problem migrating from Hyper-V to XCP-ng with vhd importing, you can try Vinchin Backup & Recovery to perform a full machine migration.
-
I'm fine with third-party vendors, but only when they are clearly identified as such. Only 2 posts to say the same thing with a specific UTM, that's really not great…
-
We have a simplified process now.
- Shutdown VM in Hyper-V
- Convert VHDX to VHD using PowerShell
- Move VHD to xcp-ng using SSH
- Generate new name using uuidgen
- Rename VHD
- Create VM in XO and attach VHD
After much trial and error this works every time.
-
Do you have the Powershell command to do this? We can use that to improve the current doc
Or you can even send us a pull request directly @McHenry -
Convert-VHD -Path <source path> -DestinationPath <destination path> -VHDType DynamicDisk type is set by extension so ensure the destination path filename ends in ".vhd"
-
Not sure how to send a pull request sorry.
-
Don't worry, I'm adding @thomas-dkmt in the conversation so he can see how to update our doc for this
-
@olivierlambert Thanks! I'll add it to the documentation.
