VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator
Moderators: anton (staff), art (staff), Anatoly (staff), Max (staff)
-
JLee
- Posts: 3
- Joined: Fri Feb 21, 2025 3:27 pm
Fri Feb 21, 2025 10:19 pm
Now I am getting a black screen. I changed the options within V2V and now when I boot the Hyper-V VM it sits at a black screen not doing anything
-
yaroslav (staff)
- Staff
- Posts: 3571
- Joined: Mon Nov 18, 2019 11:11 am
Fri Feb 21, 2025 11:00 pm
The black screen is likely due to drivers, not StarWind V2V software. Try to remove VMware tools prior to conversion and try attaching the boot volume to an IDE controller.
-
mr_vaughn
- Posts: 5
- Joined: Fri May 09, 2025 8:21 pm
Fri May 09, 2025 8:23 pm
Is this fixed in the latest build?
I have many thick VMDK on ESXi needing to go to Hyper-V
I wish when selecting the Hyper-V you could select/specify the destination VHDX type.
-
yaroslav (staff)
- Staff
- Posts: 3571
- Joined: Mon Nov 18, 2019 11:11 am
Sat May 10, 2025 7:00 am
Driver mismatch is something you need to fix from the VM side. It is because the source and destination environments need a different set of drivers for the VM to start.
Thick disks can be converted in the latest build.