AWS

Error when importing an OVA file to AWS: Client error – saved empty is empty

An OVA file is an Open Virtualization Appliance that contains a compressed, “installable” version of a virtual machine. When you open an OVA file it extracts the VM and imports it into whatever virtualization software you have installed on your computer.

This is one of the problems i ran into while importing an Ova File to AWS.
Error When importing an OVA file to AWS “client error: saved empty is empty”

Solution:

1: Use AWS license type AWS instead of BYOD

Yeah, if you import an image with “–license-type AWS”, AWS will activate windows by using their KMS every time server boots up. This is completed by ec2config service or ec2launch(2016). See check logs to find how Ec2WindowsActivate plugin works. To change this behavior, please modify config.xml of ec2config.

If you import an image with “–license-type BYOL”, AWS ec2config or ec2launch will ignore windows activation which makes you need to have your own licenses.

Note: Also, you can imagine AWS hourly rate gonna be higher than BYOL because AWS is paying licenses.

2. The grub system may not be supported 

3. The OS version is not supported.

Other references:
https://stackoverflow.com/questions/44719096/aws-ec2-import-image-windows-server-license-type
https://asyoulook.com/computers%20&%20internet/amazon-web-services-clienterror-saved-entry-is-empty-when-using-aws-import-image-command/580229 
http://www.vioja.com/clienterror-the-saved-entry-is-empty-when-using-the-aws-import-image-command/ 

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x