Sitting on 99% for hour+

[jshorr@gtimports.net]

Hello,

I am testing a V2V from Vcenter 7.x/ESxi 6.7 to Hyper-V 2022. Testing with a template that's obviously shut off, single 100GB disk, thick provizion lazy. I kicked it off several hours ago and saw expected bandwidth between two sites. Then about an hour ago it reached 99% and the bandwidth dropped drastically but did not completely stop. It is currently doing something at about 6Mbps whereas it was first at 200Mbps for a few hours. On the Hyper-V server there is a now a VHDX file that says 64GB size, 100GB size on disk. It is not getting any larger. Every time I view the properties of the file in windows it updates the modified time of the file, but otherwise it doesn't. Anyone know what is happening here, is it still doing something, if so what? The last log file entry was from when it first started. It is still suck on "converting".

Thank you

[yaroslav (staff)]

Welcome to StarWind Forum. Please share the conversion logs from C:\Program Files\StarWind Software\StarWind V2V Converter\logs.

[jshorr@gtimports.net]

The log file name: 'logs\V2V_Log-20240316-153104.log' (PID 1456)
3/16 15:31:04.905 144 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
3/16 15:31:04.921 144 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.413
3/16 15:31:04.921 144 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
3/16 15:31:04.921 144 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
3/16 15:31:04.952 144 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 14393
3/16 15:31:04.984 144 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - d9640000
3/16 15:31:04.984 144 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - d9640000
3/16 15:31:14.453 144 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eESXConnection
3/16 15:31:53.455 144 Facility ???INFO: WrapperESXI::connect: m_url - https://10.37.130.160/sdk
3/16 15:31:53.502 144 Facility ???INFO: WrapperESXI::connect: fullName - Administrator vsphere.local, key - 521fe56c-7328-6fd8-1cef-4661c5a4fb82
3/16 15:31:53.502 144 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputVM
3/16 15:31:53.752 144 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 6.7.0
3/16 15:31:53.752 144 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 6.7.0
3/16 15:31:53.752 144 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 6.7.0
3/16 15:32:05.863 144 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
3/16 15:32:30.057 144 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettingsAzure
3/16 15:32:54.871 144 Facility ???INFO: WrapperHyperV::connect: Host - \\10.140.66.205\root\virtualization\v2
3/16 15:32:56.339 144 Facility ???INFO: WrapperHyperV::init_version: HyperV version: 10.0.20348
3/16 15:32:56.386 144 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHDDSelect
3/16 15:33:12.685 144 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHYPERVConnectionTo
3/16 15:33:12.685 968 Facility ???INFO: CPPConverting::Convert: InConvertType: 6, OutConvertType: 8
3/16 15:33:12.685 968 Facility ???INFO: CPPConverting::ConvertDisks: pathInput: [GTI-ISCSI-STORAGE09] Windows Server 2019 Template/Windows Server 2019 Template.vmdk, pathOutput: C:\test\Windows Server 2019 Template\Virtual Hard Disks\Windows Server 2019 Templat.vhdx
3/16 15:33:13.138 968 Facility ???INFO: ESXVmdk::ParseFile: sFilename - [GTI-ISCSI-STORAGE09] Windows Server 2019 Template/Windows Server 2019 Template.vmdk
3/16 15:33:13.138 968 Facility ???INFO: ESXVmdk::ParseFile: m_cvmxSpec - moref=vm-25369
3/16 15:33:13.138 968 Facility ???INFO: ESXVmdk::ParseFile: sslThumbprint - 3A:C7:E2:E3:2A:9E:CB:17:23:91:CA:70:91:DA:32:04:86:A6:99:18
3/16 15:33:14.763 968 Facility ???INFO: CPPConverting::ConvertDisks: CreateInputImage: 0
3/16 15:33:16.231 968 Facility ???INFO: CPPConverting::ConvertDisks: CreateOutputImage: 0
3/16 15:36:53.479 1010 Facility ???INFO: VMConverter::ESXIConverter::Connection::<lambda_8874940e4602bbfc5e7b4b277e23eb86>::operator (): No_timeout ESX connection

This is all from when it first started. Now some more interesting stuff, at some point it started sending full bandwidth again, and is still going. Also I looked at the documentation, and I note that when I started this it never asked me that I recall to specify the disk type or whether I wanted it to automatically attach to Hyper-V.

[jshorr@gtimports.net]

It just finished. It took 2.5 hours for 100GB. The file size is now the full 100Mb. It never asked me if I wanted to make expanding etc. Maybe my esxi version is too low? What was it doing for all that time not sending any significant bandwidth?

[yaroslav (staff)]

Greetings,

Thanks for your update.
I looked into the log and noticed this line

Code: Select all

3/16 15:33:12.685 968 Facility ???INFO: CPPConverting::Convert: InConvertType: 6, OutConvertType: 8

This log entry says the conversion to run from a Microsoft VHD pre-allocated image (the internal label is 6) to a Microsoft VHDX growable 4k image (the internal label is 8 ). The file was read to be a pre-allocated (fixed) device.
Before that I see

Code: Select all

3/16 15:31:53.752 144 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 6.7.0

This line though indicates a conversion from ESXi 6.7

Can you please tell me more about the disk you are converting?

[jshorr@gtimports.net]

Regular esxi thick provisioned disk

[yaroslav (staff)]

Are you converting it to a dynamic disk?
Are these physical hosts or are they VMs in cloud?

[jshorr@gtimports.net]

Hello I’m not doing anything other than running through the Starwind wizard. From on premise esxi. Overall the speed is unbearably slow.

[yaroslav (staff)]

Can you please log a call with support@starwind.com using this thread and 1130479 as your references?