StarWind Software

Convert FreeBSD VM from VMware Server 2 to vhd - prb

Hi,
Sorry for my bad English.

- I used StarWind V2V to convert old FreeBSD VMs currently running under VMware Server 2. By default, the HDDs in VMware Server are SCSI.
- The .vmdk -> .vhd conversion is performed by StarWind: ok
- Creation in Hyper-V : GEN1 + VHD attachment: ok. By default in Hyper-V, the HDDs are IDE.
- When starting the HyperV VM, it boots then crash because it can't mount the hard drives
For example, it can't find /dev/d0s1a.
- I tried setting the VHD to SCSI in Hyper-V instead of IDE, but in this case, the VM doesn't boot.

- I think my problem is that the VMware disks are SCSI but IDE in Hyper-V. I'm stuck...

- Is there an option to have StarWind V2V convert to SCSI HDDs?

is there a FreeBSD "Guru" to help with reconfiguration? (Knowing that the FreeBSDs in question are no longer supported, so no packages can be loaded.)

Thanks in advance for any suggestions.

Best regards

PS: I found a similar topic in this forum, similar to the link at :
viewtopic.php?f=15&t=7192&sid=24d33f696 ... e8b8425e26

Welcome to StarWind Forum!
The issue relates to the driver conflict between the VM and the destination hypervisor. It is not a V2V converter breaking something.

- Is there an option to have StarWind V2V convert to SCSI HDDs?

Yes, you can run the converter in recovery mode, yet there are pitfalls that relate specifically to the settings of that VM in the destination.
Also, try a different boot option; it could help.

Please also consider removing the VMware tools prior to the installation.

As a last resort, you could create a blank VHD(X) and try mirroring the data there. https://forums.freebsd.org/threads/disk ... ing.45653/ could be helpful.

Hi Yaroslav
- Thanks for the quick reply.

> The issue relates to the driver conflict between the VM and the destination hypervisor. It's not a V2V converter breaking something.

Yes...

- Is there an option to have StarWind V2V convert to SCSI HDDs?

> Yes, you can run the converter in recovery mode, yet there are pitfalls that relate specifically to the settings of that VM in the destination.

- I don't see the "recovery mode" option in the StarWind V2V interface to test this. Can you tell me where to find the "recovery mode" option?

Thanks in advance.

Sorry for my poor English.
Best regards.

- Is there an option to have StarWind V2V convert to SCSI HDDs?

Yes: V2V converter is hardware-agnositc.

- I don't see the "recovery mode" option in the StarWind V2V interface to test this. Can you tell me where to find the "recovery mode" option?

Check this out https://www.starwindsoftware.com/v2v-he ... 20continue..

Hi Yaroslav
- Thanks for the quick reply and for your efforts.

Regarding my question:
- Is there an option to have StarWind V2V convert to SCSI HDDs?
You answered: "Yes: V2V converter is hardware-agnostic."

I think I misspoke because my English is poor.
I'll try to rephrase:
- The source .VMDK on VMware Server is a SCSI VM HDD
- The destination .VHD on Hyper-V is an IDE VM HDD
My question is whether there is an option to convert V2V so that the destination VM is a .VHD with a SCSI HDD (and not an IDE one).

Regarding my question:
- I don't see the "recovery mode" option in the StarWind V2V interface to test this. Can you tell me where to find the "recovery mode" option? You replied with a link.

I spent a lot of time on the links in this documentation:
- I didn't find the "recovery mode" option.
- I also searched in the "Command Line Interface"
- I used the "search" button with "recovery" without success.
- I use the .vmdk file -> .vhd file conversion.
Here is the link describing what I'm using:
https://www.starwindsoftware.com/v2v-he ... DVHDX.html

I know the problem is in the FreeBSD VMs where the disks don't mount because the VMware SCSI references don't exist in HyperV. That's why I'm asking if it's possible to convert the VHD VM to a SCSI VM disk for HyperV.

I hope this is clearer now?

thanks

Best regards.

No worries. Things happen.
StarWind VSAN allows converting the VM with VM disks attached to SCSI bus.
You can try converting individual disks, this seems a viable workaround.