Instantiated Virtual Machine will not boot to operating system

Products

• VMware Cloud Director

Issue/Introduction

• During instantiation of vApp the virtual machine, the initial power on will not boot to Operating system.
• In Linux: Recovery boot with grub menu is observed
• In windows:  No file/operating system found is displayed.
• Same issue happens when deploying new virtual machine from template used.

Environment

10.x

Cause

During upload of image (ovf, iso file, ect.) to content library the files can become corrupted and investigation of files are needed.

Resolution

• The initial investigation of files can be completed using MD5 checksum to confirm the uploaded file matches the original file see kb: using MD5sum to verify the integrity of copied files 
• In some cases when the file does not match the original file, it will be necessary to confirm that the template is reuploaded to the content library using the following document: Upload an ovf package to create a vapp template
• If the initial file matches the original file then there is a plausible file corruption with vmdk and some investigation to the original image files (iso, ovf, vmdk, etc) will need to be reviewed and validated as working, please work with the templates vendor to ensure a working template was provided.

Additional Information

If sha256hash is required, please refer to KB: How to Get Hash of a File for SHA256 and/or MD5