StarWind Software

Hi there,
my first post here. I'm trying to do a v2v migration from a windows server 2012 vm hosted on a esxi 6.0 host to a new windows server 2019 with hyper-v
The process completes correctly but when I try to run the vm, I get an inaccessible boot device BSOD. Automatic repair fails , bcdedit too "the boot configuration data store could not be opened", boot rec as well " a device attached to the system is not functioning", Diskpart is showing no disks ?!?!?!
Do you have any suggestion? Really don't know how to get out of it.
I forgot to say that I tried a conversion from the powered on vm.
thanks in advance
Max
Italy

Welcome to StarWind Forum.
Shut down the VM and do the conversion of its disks alone.

Hello . Just tried with a linux vm hosted on the source esxi . I powered off the vm before migration.
Different message but same issue: disk anaccessible

Try converting the disk alone.

Sorry what do you mean by "converting the disk alone" ?
Here are the steps followed:
turned off the source vm
Selected the disk of the source vm in the converter
Set all the parameters for the creation of the new hyperv vm.
Started conversion
thanks
Max

It is possible to convert VM disks alone and create the new VM on the destination host. See this guide for more details https://www.starwindsoftware.com/v2v-he ... erver.html

Followed the guide with no luck.
tried with a windows vm and a linux vm. There must be something else....
thanks
Max

Hi Max,

Please try enabling compatibility mode while converting the disk.