charlin's Posts

Hi VMWare experts, I am having problem with automation script because the string passed in the ovftool command uses credential vsphere.local\userXYZ instead of just userXYZ It appears that ... See more...
Hi VMWare experts, I am having problem with automation script because the string passed in the ovftool command uses credential vsphere.local\userXYZ instead of just userXYZ It appears that the backsplash in the 'vsphere.local\user' cause the command line to be misinterpreted, so the automation script that calls ovftool to deploy VMs kept failing.  It erred with "cURL error of ‘couldn’t resolve hostname" even though there is nothing wrong with any hosts or hostname resolution on the network. On a Win-based vCenter I was able to reconfigure it so that instead of requiring login user format of 'vsphere.local\userXYZ', it will now accept user = 'userXYZ'.  With that change, ovftool.exe command string is now progress correctly and VMs are deployed.  I could reconfigure Window-based vCenter to not use just user = userXYZ (instead of vsphere.local\account), but I could not figure out how to get vCSA to stop requiring the format of vsphere.local\userXYZ. The string segment in the long ovftool.exe command line looked like this … This works: "vi://userXYZ:password@tm-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi112.cisco.com" This does not work: "vi://vsphere.local\userXYZ:password@lin-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi111.cisco.com" Is there anyway to configure vCenter Virtual Appliance to use log in format of user = userXYZ instead of user = vsphere.local\userXYZ?   Or is there some way of reformatting the string so that OS can interpret it correctly even with backsplash '\' is used in the string? Thank you Charles The complete ovftool.exe command is shown below: "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --acceptAllEulas --skipManifestCheck --diskMode=thin --name=linsys2-vm1 --deploymentOption=vm_typeA --datastore=EMC-LUN1 --net:"Network Adapter 1"="VLAN 410 - 172.27.14.0/24" --net:"Network Adapter 2"="VLAN 410 - 172.27.14.0/24" --vmFolder=   --prop:cisco_hostname.Proj=linsys2-vm1 --prop:cisco_ip_0.Proj=172.27.14.135 --prop:cisco_dnsDomain.Proj=cisco.com --prop:cisco_netmask_0.Proj=255.255.255.0 --prop:cisco_gateway_0.Proj=172.27.14.1 --prop:cisco_dns1_0.Proj=172.27.200.199 --prop:cisco_dns2_0.Proj=173.36.131.10 --prop:cisco_language.Proj=English v:\ova\projectX_1.0.0.ova "vi://vsphere.local\userXYZ:password@lin-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi111.cisco.com" Opening OVA source: v:\ova\projectX_1.0.0.ova The manifest does not validate Error: cURL error: Couldn't resolve host name Completed with errors Installation Done!
Hi VMWare experts, I am having problem with automation script because the string passed in the ovftool command uses credential vsphere.local\userXYZ instead of just userXYZ.   It appears... See more...
Hi VMWare experts, I am having problem with automation script because the string passed in the ovftool command uses credential vsphere.local\userXYZ instead of just userXYZ.   It appears that the backsplash in the 'vsphere.local\user' cause the command line to be misinterpreted, so the automation script that calls ovftool to deploy VMs kept failing.  It erred with "cURL error of ‘couldn’t resolve hostname" even though there is nothing wrong with any hosts or hostname resolution on the network. On a Win-based vCenter I was able to reconfigure it so that instead of requiring login user format of 'vsphere.local\userXYZ', it will now accept user = 'userXYZ'.  With that change, ovftool.exe command string is now progress correctly and VMs are deployed.   I could do that on Window-based vCenter, but I could not set up vApp vCenter to use just 'userXYZ'. The string segment in the long ovftool.exe command line looked like this … This works: "vi://userXYZ:password@tm-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi112.cisco.com" This does not work: "vi://vsphere.local\userXYZ:password@lin-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi111.cisco.com" Is there anyway to configure vCenter Virtual Appliance to use log in format of user = userXYZ instead of user = vsphere.local\userXYZ?   Or is there some way of reformatting the string so that OS can interpret it correctly even with backsplash '\' is used in the string? Thank you Charles The complete ovftool.exe command is shown below: "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --acceptAllEulas --skipManifestCheck --diskMode=thin --name=linsys2-vm1 --deploymentOption =vm_typeA --datastore=EMC-LUN1 --net:"Network Adapter 1"="VLAN 410 - 172.27.14.0/24" --net:"Network Adapter 2"="VLAN 410 - 172.27.14.0/24" --vmFold er=   --prop:cisco_hostname.Proj=linsys2-vm1 --prop:cisco_ip_0.Proj=172.27.14.135 --prop:cisco_dnsDomain.Proj=cisco.com --prop:cisco_netmask_0.Proj=255.255.255.0 --prop:cisco_gateway_0.Proj=172.27.14.1 --prop:cisco_dns1_0.Proj=172.27.200.199 --prop:cisco_dns2_0.Proj=173.36.131.10 --prop:cisco_language.Proj=English v:\ova\projectX_1.0.0.ova "vi://vsphere.local\userXYZ:password@lin-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi111.cisco.com" Opening OVA source: v:\ova\projectX_1.0.0.ova The manifest does not validate Error: cURL error: Couldn't resolve host name Completed with errors Installation Done!
hi, I am building an application and running on a particular OS, and packaging it into a OVF template.  So when you deploy the OVF, you get the virtual machine which runs the application. D... See more...
hi, I am building an application and running on a particular OS, and packaging it into a OVF template.  So when you deploy the OVF, you get the virtual machine which runs the application. During the OVF template deployment, I am prompted to choose "thick  eager zero", "thick lazy zero", or "thin" provisioning. Is there possible for me to control what choices are selectable here?  For example, I want to gray out the "thin provisioning" option, so that my VM is only created with either eager zero or lazy zero provisioning. Question 2:   How much of performance hit, if any, is there with lazy zero as opposed to eager zero?   On one hand, I wan to reduce the amount of time it takes to deploy the OVF, and I believe lazy zero might be faster (I could be wrong thought, let me know).    But on the other hand, my application is real CPU intensive and requires real-time processing, so does lazy zero impose some performance penalty here? Question 3:  If I cannot control selection of provisioning druing the OVF template deployment screens, then is there a point later on during the whole OVF deployment where I can insert code to verify the configuration/properties of the VM that is to be created, so as to detect that the disk size is not what I expect (for example, thick would have been 200 GB, but I detect the storage provisioned is only going to be 50 GB).   If I can do that then that would offer me another way to prevent (and disallow) people from deploying the OVF with thin provisioning. thank you, Charles
hi, What is the best combination of sockets (physical CPUs) x cores/socket that would best utilize SMP function of the Guest OS (Linux)? For example, if an ESXi 5.0 host has 4 physical CPUs... See more...
hi, What is the best combination of sockets (physical CPUs) x cores/socket that would best utilize SMP function of the Guest OS (Linux)? For example, if an ESXi 5.0 host has 4 physical CPUs, each CPU has 10 cores, total of 40 vCPU are available to VMs. If I want to build a virtual machine that needs 8 vCPU, what is best combo to get 8? Combos: 1 physical x 8 cores 2 physical x 4 cores 4 phsicals x 2 cores Is it better to use max number of sockets (physical CPUs), which means combo #3 is better choice? Or is it better to maximize use of cores/CPU, which means combo #1 is better choice? thanks Charles
thanks for the quick response. allow me to summarize my understanding (let me know if I misunderstood). In order for my application (which reside across multiple VMs and spanning multiple E... See more...
thanks for the quick response. allow me to summarize my understanding (let me know if I misunderstood). In order for my application (which reside across multiple VMs and spanning multiple ESXi 5 hosts) to communicate between each others and with some other applications using IPv6 addressing: 1.   doesn't matter if I use vApp vCenter or Win-based vCenter, because the 'IPv6 support' feature described under vCenter product only means whether or not you can configure your vCenter with IPv6.    Even if you cannot configure your vCenter with IPv6 address, the hosts and VMs that are being managed by this vCenter can still use IPv6, provided #2 (below) is configured. 2.   Each ESXi host must have its network (vSwitch properties) configured to 'enable IPv6 support on this host system', in order for all the VMs (that are residing on this host) to be able to use IPv6 addressing. Is the above summary correct? thank you Charles
hi, If I am building some VM machines (VMs reside on multiple hosts, but all VMs grouped together and working as a full application) and part of the application uses IPv6 addressing, and If I ... See more...
hi, If I am building some VM machines (VMs reside on multiple hosts, but all VMs grouped together and working as a full application) and part of the application uses IPv6 addressing, and If I am building them under a vmware infrastructure consisting of vCenter and ESXi hosts, does this infrastructure automatically support IPv6 (i.e, default settings of ESXi 5.0 hosts and vCenter)?     Or are there IPv6 enable/disable settings that need to be turn on in order for the application to work? Reason I am asking is because: a)   VMware provides a Linux-based vCenter vApp, but vmware doc states that it currently does not support IPv6. b)   In vCenter, when I select each host and go into network configuration, I see "enable IPv6" check button. thank you for your advice Charles