Here's an example from a machine I converted which originally had Farm-Bridge and UNH-Bridge interfaces in VMWare server, and which had been configured such that the new interfaces should match the Farm-Bridge and UNH-Bridge interfaces on the Hypervisor:
This may have something to do with MAC addresses from VMware server not being compatible with vSphere Hypervisor (I've tried creating new interfaces and copying the old MAC addresses from the VMware Server machine and got an error that they were out of the acceptable range), and you end up with your original configurations which do not match the interfaces now on the new machine, and new interfaces that have default configurations. Follow these steps to convert the guest machines to vSphere Hypervisor.įirst, run the Converter client as an administrator The converter is a graphical application, so if you are connecting to the VMware Server host over the network you will need to foward X over SSH. Make sure you install both the server and client, but you do not need to enable remote access for the server.Ĭonverting to vSphere Hypervisor VMs is fairly simple. Generally (at least on CentOS/RHEL machines, I haven't tested it on others) you can accept the defaults for each prompt.
tar.gz file, and then run the "" script in the vmware-converter-distrib directory. The latest version (4.3) only supports Windows so in order to convert Linux virtual machines you'll need to download version 4.0.1. You can download VMware vCenter Converter Standalone for free from VMware's website. The converter will convert the machines and copy them to the hypervisor your choose. Doing so will allow you to convert that system's clients to vSphere Hypervisor machines. In order to convert VMware Server virtual machines you will need to install vCenter Converter Standalone on the VMware Server HOST system. VMware converter can be used for both Physical to Virtual (P2V) as well as Virtual to Virtual (V2V) conversion of machines to the vSphere Hypervisor VM format.
0 kommentar(er)
