BinaryData Posted November 27, 2015 Share Posted November 27, 2015 I think you're mixing up cloning ESX which is physical and cloning a VM which is virtual... The thing with the export to OVA is I don't know if it creates all virtual new hardware, like NIC's and MAC addresses, etc... Or if it's an actual clone... I haven't done it this way ever... Well I have but I haven't looked into those parts to see what happens. Aaron, I mentioned earlier why he couldn't just "Clone" the HDD. Essentially image Drive A, to the new Drive B, and call it good. Which, people suggest to not do. I think that's what BudMan is referring too. offroadaaron 1 Share Link to comment Share on other sites More sharing options...
+BudMan MVC Posted November 27, 2015 MVC Share Posted November 27, 2015 There is nothing saying he cant just clone the HDD to the SSD... This would keep everything the same and be a very easy solution to his problem.. Not like he is cloning it and using new hardware.. There is nothing wrong with cloning the disk.. Link to comment Share on other sites More sharing options...
binaryzero Posted November 27, 2015 Share Posted November 27, 2015 I would not recommend cloning a disk with a type 1 hypervisor - best practice is move the VMs off, fresh install hypervisor, migrate back. Do it right if you're going to do it. Clone the VMs all you like, just make sure you use sysprep Link to comment Share on other sites More sharing options...
Recommended Posts