To fix this, I need to find the MAC address of the new VM, edit ifcfg-ethN and add this MAC to the HWADDR= field.The file /etc/sysconfig/network-scripts/ifcfg-ethN has the MAC address of the interface on the first machine. Linux doesn't know about this new MAC address and thus networking doesn't work.VMware Fusion or vCenter will assign a new MAC address to the network interface on the cloned VM.
The idea is that we take the minimal VM, clone it and add more software later. This is a bare-bones VM with a minimal set of software and a functioning network stack.Many of you are familiar with the problem, and it is described at VMware KB: " Networking does not work in a cloned Linux virtual machine (2002767). This is kind of odd because I’ve had more success with this method for importing physicals into VMware Fusion, than I have had with other methods of “importing” OSes into VMware Fusion….I've run into the following problem on both VMware Fusion (for Macs) and with VMware ESXi/vSphere.
I tried this – a number of times, and it did not work. Watch out for the format of the disk – as it does not default to “Thin Provisioning”. Select a host or cluster in vCenter, and choose Deploy OVF Template… Again, this failed in vSphere 6.5 U1, but was successful in vSphere 6.7. Personally I’ve found the import/export process in vCenter/ESX a bit 50:50…. Once exported you can login to either VMware vCenter or VMware ESX to import there. Select the VM in Fusion, and in the File menu, choose Export to OVF
I prefer OVA as its pre-compressed and gives you a single file to deal with – as OVF gives you a text-based “descriptor” file and whole bunch of VMDK files. Once connected and authenticated to the vCenter or ESXi host – you can drag and drop a VMware Fusion VM like so:Īnother method is to export the VM from Fusion into a the OVF/OVA format. VMware Fusion has a “Connect to Server” option Hard to tell if the vSphere uplift was the decisive difference, or whether it was a case of just try, try and try again. This initially failed when the target was vSphere6.5 U1, but worked with vSphere 6.7. METHOD1: Connect to Server from VMware Fusion That way if your jumpbox is toast you don’t loose that PowersHell script you have been perfecting all week.
So it was all a waste of time really – I could have just deployed a fresh copy of Windows 10.Īnyway, I’ve learn my lesson the hardware – always backup your Jumpbox and make sure any work in progress is held elsewhere such as Dropbox, Google Drive or OneDrive. Ironically, after completing the move – because Windows10 was sitting on a different virtualization hardware platform – it de-activated itself – and wouldn’t reactivate. So I thought heck might as well import to vSphere, and avoid re-installing and that annoying watermark in the right-hand corner of my RDP desktop. In the meantime I realise I had an activated version of Windows10 running in VMware Fusion. I didn’t have a backup (which was stupid of me) and Windows wasn’t activated. I recently lost my Windows10 Jumpbox due to a power failure. If at first you don’t succeed give it another go. Executive Summary: There are lot of methods.