StarWind Software

Posted: **Tue Jul 23, 2024 5:59 pm**

Hello,

Using version 9.0.1.509. Converted displays that it's 100% complete, the window shows:

Success
Invalid parameter
Conversion failed.

Last few lines of the logs are showing:

Code: Select all

7/23 10:54:31.634 16e0 Facility ???INFO: CPPConverting::ConvertDisks: CreateInputImage: 0
7/23 10:54:35.946 16e0 Facility ???INFO: WrapperS3::initS3Client: Created S3 client in us-east-1 region
7/23 10:54:37.261 16e0 Facility ???INFO: AWSDisk::CreateOutputImage: Create bucket name - v2v-converter-bucket-xxxxx-7af7-4cd6-b0e1-3b07618228a
7/23 10:54:37.571 16e0 Facility ???INFO: CPPConverting::ConvertDisks: CreateOutputImage: 0
7/23 10:57:21.678 1918 Facility ???INFO: VMConverter::ESXIConverter::Connection::<lambda_xxxxx602bbfc5e7b4b277e23eb86>::operator (): No_timeout ESX connection
7/23 11:35:35.304 16e0 Facility ???INFO: CPPConverting::ConvertImage: Success
7/23 11:35:35.350 16e0 Facility ???WARNING: CPPConverting::ConverterAWS: Disk path is fail - 
7/23 11:35:35.350 16e0 Facility ???ERROR: CPPConverting::Convert: FAILED

I originally ran the tool as the root user. Thinking there might be some permissions issue, I created a new user and granted:

AdministratorAccess
AmazonEC2FullAccess
AmazonS3FullAccess
IAMUserChangePassword

But still receive the same "Disk path is fail". The S3 bucket that's created has a copy of HDD.vhd.

Any pointers to complete this migration would be helpful, thanks!

Posted: **Thu Jul 25, 2024 1:20 pm**

Hi,

Thanks for your post.
Could you please let me know if the instance is some sort of "AWS-ready" instance?

Posted: **Thu Jul 25, 2024 3:33 pm**

yaroslav (staff) wrote: ↑
Thu Jul 25, 2024 1:20 pm
Could you please let me know if the instance is some sort of "AWS-ready" instance?

No, it's just a Windows VM in ESX.

Posted: **Thu Jul 25, 2024 4:06 pm**

Hi,

Thanks for your udpate. Can you try running a P2V conversion from inside of that VM?
Please consider using the root account for troubleshooting purposes.

Posted: **Wed Jul 31, 2024 3:28 pm**

Ugh, It's a Windows XP VM (!!) and p2v converter won't run on it. This is probably not possible given the age of the VM.

Posted: **Wed Jul 31, 2024 3:47 pm**

Thanks for your udpate. Can you try running a P2V conversion from inside of that VM?

Posted: **Wed Jul 31, 2024 7:13 pm**

yaroslav (staff) wrote: ↑
Wed Jul 31, 2024 3:47 pm
Can you try running a P2V conversion from inside of that VM?

It reports this error launching:
Internal error: Cannot expand "pf64" constant on this version of Windows.

Posted: **Thu Aug 01, 2024 8:53 am**

Hi,

Can I get the full conversion log of V2V from ESXi to AWS?
Also, are there any non-ASCII symbols in the VM name?

StarWind Software

ESX to AWS error: Disk path is fail

ESX to AWS error: Disk path is fail

Re: ESX to AWS error: Disk path is fail

Re: ESX to AWS error: Disk path is fail

Re: ESX to AWS error: Disk path is fail

Re: ESX to AWS error: Disk path is fail

Re: ESX to AWS error: Disk path is fail

Re: ESX to AWS error: Disk path is fail

Re: ESX to AWS error: Disk path is fail