In Linux you can just change the IP (if not using DHCP) and edit /etc/hostname and reboot to make a unique hostname. When you get to the "select a hard disk" part, select the VMDK file you just cloned in the previous step.Ħ) You may have trouble with a cloned machine in Windows you'll need to run sysprep to make it unique. # vmkfstools -i imageA/imageA.vmdk imageB/imageB.vmdkĥ) From VI Client, create a new VM and select the custom option. I assume that most of new VMware users are not much friendly with CLI (command line interface) and show the possibility to clone a VM with some free tools which co use GUI first.
There are workarounds and tools which helps. You can find the PID with "ps aux | grep inetd".Ĥ) Use vmkfstools to clone the. The ESXi Free Version is limited and cloning of VMs is not possible through the vSphere client's menu. Exit and restart inetd with "kill -HUP " where is the process ID of inetd. You are now in a bare-bones Unix shell.Ģ) (optional) Enable ssh so you can do the rest remotely: use vi to edit the /etc/nf file and uncomment the line that starts with "ssh". You will get a bunch of dire warnings about this being an unsupported mode. Here's what I did note that I'm running local storage only on an older host machine:ġ) From the ESXi console, hit Alt-F1, then type "unsupported".
I've read about some people using the free version of Converter, but this didn't work for me (Converter keeps hanging partway through the operation). Again, test and production have to be isolated.In the free verison of ESXi, it's not obvious how to clone a VM, since you don't have VirtualCenter available. Thinking further, you could just power down the VM, copy that whole folder over, then power it back up and work on it in test. I do not know the licensing rules covering this, because you're technically running 4 copies of windows on two licenses.Įdit: There are other files in the VM folder as well, they are small, make copies and take them with the VMDK file.
Other than maybe setting the static IPs back if windows thinks it has new network cards and maybe reactivating if it complains, you should be good. If that's the case, when you import, select you MOVED them when it asks, not that you COPIED them. I would assume your test environment is cut off or segregated from the main network. Vmkfstools -i "/vmfs/volumes/Main_Datastore/server/server_1.vmdk" -d thin "/vmfs/volumes/Spare_Datastore/server/server_1.vmdk"īeing a DC shouldn't matter at all UNLESS you boot them both up on the same network. Then, move the cloned vmdk to your other server however you wish and import.īelow is making sure it comes over as a thin disk to another datastore, adjust as needed to put it to same datastore/dif folder or whatnot: If you are connected directly to host (like many free edition or 1 or 2 user shops are), then you have to use the CLI to do the clone as such.
I BELIEVE that right click then clone is only there if your vsphere client is connected to vcenter.
0 kommentar(er)
