![]() Then obtain shell access to the ESXi server that has visibility to the VM’s Datastore. In essence fooling it into think it’s an older version and basically making it just skip the new config values. By editing this file we can make it think it’s a Version 7 VM rather than 8. Inside the VMX file for the VM there are a few critical lines that tell vSphere / ESXi what hardware version the VM is. Create a new VM on H/W version 7 and attach the disks from the original VM.Īll very safe ways but there is a fourth, and totally unsupported, quicker way to downgrade by hacking the VMX config file. Use VMware Converter and perform a V2V to H/W version 7.ģ. Revert to a previous snapshot while on H/W version 7.Ģ. VMware have three supported ways of downgrading.ġ. If it finds your H/W versin isn’t supported it won’t let you proceed. The OVF upload process in vCD 1.5 does a few sanity checks before starting an upload. The maximum H/W version supported is 7 while my environment is version 8 / 9. I’m currently in the progress of migrating a vSphere 5.1 environment to a vCloud Director 1.5 environment (with an ESXi 4.x back end). ![]() Until recently this never posed an issue. That usually includes the VM Hardware versions. I always make sure that everything is up to date and running the latest versions. I tend to run a pretty tight shop with my VMware infrastructure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |