Camero's Posts

It is recommended to use the vCenter Converter[VMware vCenter Converter: P2V Virtual Machine Converter | United States] when you export VMs from the hosted Virtualization products [workstation, Fusion, Player] to native virtualization platform i.e ESX. Retry the export using vCenter Converter.

Hello , We would like to learn more about your environment. If it is possible, please provide answers to the following questions -Does the issue happen with all of the VMs or only certain VMs are facing with this issue while the user tries to perform vMotion? -If the issue happens with only certain VMs, could you please provide the detail about the VM configuration. VM HW version, Guest OS, N/W  count etc. -High level topology of the Network that your current Environment uses for the VMs (that are facing this issue) -- vDS, vSwitches per host  etc.

Hello Chao Sun, Could you post the error message from the logs file or attach the  logs. It would help us determine cause of the problem. log location can be determined by following VMware KB:    Location of VMware vCenter Server 6.0 log files Provide the logs from - vSphere client Webclient -Upgrade logs (Cancel the installation and it automatically collects the support bundle. extract the support bundle and attach vim-vcs-msi.log, vminst.log & vc-install.txt

Following KB is recommended for your scenario VMware KB: Upgrading to vCenter Server 6.0 best practices Run through the KB and determine the needs of your Organization and select the best model that serves your needs. A short guide to decide on design for vSphere 6.0 . Top 5 Tips When Considering vCenter Architecture Design in vSphere 6.0 http://www.vmware.com/files/pdf/products/vsphere/Top-5-Tips-When-Considering-vCenter-Architecture-Design-In-vSphere6.pdfhttp://www.vmware.com/files/pdf/products/vsphere/Top-5-Tips-When-Considering-vCenter-Architecture-Design-In-vSphere6.pdf

John, It is not clear when you state "All of them are are the same domain".  Is this the Single Sign-On(SSO) domain, which is created while installing PSC. Also it is not clear if both vCenter servers are using same or different external PSCs with same SSO domain and Site name. A.  Assuming if both vCenter servers are configured to use the same external PSC and same domain (SSO domain, which is created while deploying PSC) then the vCenter servers are already in enhanced linked mode. You don't need to perform any operation. This configuration is the simplest form of enhanced linked mode explained in the following docs.. === 1. New features in vSphere 6.0 http://www.vmware.com/files/pdf/vsphere/VMware-vSphere-Platform-Whats-New.pdf (refer to page 2. Using Enhanced Linked Mode >> vSphere 6.0 Documentation Center === B.  Assuming both vCenter Servers are configured to use different external PSC , but PSCs are joined( step -6 vSphere 6.0 Documentation Center  ) to the same SSO domain, Then also you don't need to perform any additional operation as the configuration enables the enhanced linked mode by default. C.  Assuming both vCenters are configured to use different external PSCs with different SSO domains, then I don't see a direct solution which can convert the current deployment to enhanced linked mode ...                          VC1 connected to PSC1 (SSO-domain1)                               X<<<No link b/w PSCs>>>X                          VC2 connected to PSC2 (SSO-domain2) below are the issues in this model.. 1. PSC are not replicating and are configured with own SSO Domain 2. Re-pointing across PSCs is supported in same domain and across sites from 6.0U1 : KB>> VMware KB: Repointing the VMware vCenter Server 6.0 between sites in a vSphere Domain Even if we re-point vCenter server from one PSC to another one, the permissions, roles, tags configured with one PSC and used by the vCenter may not carry forward to the other PSC, as the PSCs were never replicating that info. I would recommend to refer to following documentation before considering any deployment of vcenter server 1. Top 5 Tips When Considering vCenter Architecture Design in vSphere 6.0 http://www.vmware.com/files/pdf/products/vsphere/Top-5-Tips-When-Considering-vCenter-Architecture-Design-In-vSphere6.pdf 2. vCenter Server 6 Deployment Topologies and High Availability - VMware vSphere Blog - VMware Blogs 3.  VMware KB: VMware Platform Services Controller 6.0 FAQs

Following white paper gives you the basic fundamentals of Virtualization- https://www.vmware.com/pdf/virtualization.pdf You may already know what is virtualization, since there seems to be some confusion here when it comes to the hardware, I thought of providing the link to clear your doubts if any. As a.p. stated,  ESXi like any other OS, needs to be in running state, which is when vCenter server can connect to the ESXi.  If you have resource constraints (limted Hardware) you may use the Player (Virtual Machines & Multiple Operating Systems: VMware Workstation Player | United States) installed on any regular OS (windows or Linux) and create required VMs to run ESXi, vCenter server (with windows based) or vCSA(appliance) .