StarWind Software

Hello,

I have a 2012R2 server that I'd like to migrate into my AWS environment.
The server is virtual, but I have no hypervisor access so I am performing a P2V migration.

I'm running into issues though - the conversion starts and seems to complete successfully.
I can see files being copied into the AWS S3 bucket created by Starwind V2V converter "v2v...."

I'm using the following instruction:
https://www.starwindsoftware.com/v2v-he ... vices.html

I did see:
https://www.starwindsoftware.com/v2v-he ... vices.html

Which suggests I need an "allow all" inbound rule on my default security group.
I'm assuming this doesn't need to be on the default security group but can be attached to the SG specified in the Starwind V2V configuration.
Is there a set of ports I can further lock this down to?
I am not sure if I need to make any amendment because I do end up with a VHD in the S3 bucket, but I get this failure at the end of the conversion.

End of log:
12/4 22:08:59.799 5b8 Facility ???INFO: P2V::getSectorsNext: countClusters - 4150288, dwCountBytes - 4150288
12/4 22:09:05.866 5b8 Facility ???INFO: CPPConverting::ConvertImage: Success
12/4 22:09:05.873 5b8 Facility ???WARNING: CPPConverting::ConverterAWS: Disk path is fail -
12/4 22:09:05.873 5b8 Facility ???ERROR: CPPConverting::Convert: FAILED

Has anyone experience of this error that may be able to help?

Thank you very much!

Hi,

You need to make the changes to allow conversion.
Can I please have the entire log?

Please find the latest log attached.

Thanks! Could you please try repeating the conversion with the AWS root user?

Thank you - I am running this using the secret key and access key created by the root user.

Typically I am selecting all of the disks in the server, but the failure occurs after the HDD0 (system drive) has been sent to S3 but before the other drives start to convert.

I can run the following command manually using the same secret and access keys via awscli
aws ec2 import-image --description "servername" --disk-containers "file:///data/containers.json"

This command makes the uploaded VHD file of HDD0 into a Snapshot, from which I can then generate an AMI template and then I am able to launch an instance from it and boot into the OS and log in (albeit with just the C: drive and no data drives)

This is my containers.json

Thanks for your update. My colleagues are still investigating this incident. I will keep you posted.
Many thanks!

Thank you for your patience!
My colleagues mentioned that StarWind V2V Converter works only with MBR partition.