For anyone out there still using ESX(i) 3.5 you will need to apply a specific patch to your hosts to be able to continue updating these after June 2011. This patch updates a secure key which will allow future patches to be applied. Follow the links below to the VMware KB articles for further information. KB: 1030001 Critical Impact: VMware ESX 3.5, Patch ESX350-201012410-BG: Apply this patch to continue applying patches on ESX 3.5 hosts after June 2011 has been written for users of ESX. KB: 1030002 Critical Impact: VMware ESXi 3.5, Patch ESXe350-201012401-I-BG: Apply this patch to continue applying patches on ESXi 3.5 hosts after June 2011 has been written for users of ESXi.
Memory problems occur when a host uses more than 1016 dvPorts on a vDS
A few people have been talking about this lately, and what it actually means. Within the vSphere 4.1 U1 release notes the following statement has been made: Memory problems occur when a host uses more than 1016 dvPorts on a vDS * Although the maximum number of allowed dvPorts per host on vDS is 4096, memory problems can start occurring when the number of dvPorts for a host approaches 1016. When this occurs, you cannot add virtual machines or virtual adapters to the vDS. Workaround: Configure a maximum of 1016 dvPorts per host on a vDS. So what does this mean exactly? If a portgroup is created with 2000 dvPorts, how would this be created on a host? Would it create 2000 dvPorts for every host in the vDS? The Answer is NO. A host will only have the maximum number of configured proxy ports, which by default is 256. Proxy ports are used to map to one of the vDS ports when a VM is running on that host. If you run out of proxy ports you will not be able to add more VMs to the vDS on that host. A good point to note is that if
Read More…
PXE Manager for VMware vCenter
Today VMware have officially released PXE Manager for VMware vCenter written by Max Danieri. Max works in the Technical Services Cloud Practice. Before joining VMware Max wrote products like VMTS Patch Manager PXE Manager for vCenter enables ESXi host state (firmware) management and provisioning. Specifically, it allows: * Automated provisioning of new ESXi hosts stateless and stateful (no ESX) * ESXi host state (firmware) backup, restore, and archiving with retention * ESXi builds and VMtools management (only stateless ESXi) * Multi vCenter support * Multi network support with agents (Linux CentOS virtual appliance) * Wake on Lan for any host * Hosts memtest and inventory * vCenter plugin and much more… You can download the application by clicking here
VMware vCloud Director Q&A Part 3
This is part 3 of the Q&A article published last year. Eventually I will migrate these to the FAQ section of the site. If anyone has any questions that are not included in this Q&A or the other Q&A’s post a comment to http://www.virtual-blog.com/2011/01/q-a/ and I will answer and include in the FAQ. vCloud Director: vApp Cloning Q. I have a vAPP comprised of 10 VMs. When I add this vAPP to my cloud using the “Add to My Cloud…” option, I see from vCenter that it is cloning each VM in a serial fashion, not in parallel. I was hoping the 10 source VMs would be cloned in parallel to 10 new VMs. Is this expected behavior and are there any options to change this to clone in parallel to reduce the provisioning time? A. Serial cloning is the expected behavior. Cloning and deploying new vApps is always done in a serial manner, one VM at a time in the vApp. Cloning is parallel at the vApp level, i.e. if you tried to clone 2 vApps at once. vCloud Director: Powering on vApps Q. Is it possible to have a vApp that was provisioned by vCD to automatically power
Read More…
VMware vSphere Client for iPad
I cant believe this actually slipped by me. On 18th March, VMware officially released the vSphere iPad client. To use this client you need to download and install the vCenter Mobile Access appliance. The iPad client allows you to manage and control your VMware hosts and Virtual Machines running within a vCenter. The VMware vSphere Client for iPad is a companion interface to the traditional vSphere client, optimized for viewing and managing your vSphere environment on the go. With this client you can monitor the performance of vSphere hosts and virtual machines. Virtual machines can be started, stopped and suspended. vSphere hosts can be rebooted or put into maintenance mode. Features: Search for vSphere hosts and virtual machines in your vSphere environment Monitor the performance of vSphere hosts and virtual machines Manage virtual machines with the ability to start, stop and suspend View and restore your virtual machines’ snapshots Reboot vSphere hosts or put them into maintenance mode Diagnose vSphere hosts and virtual machines using built-in ping and traceroute tools Requirements: vCenter Mobile Access (vCMA) virtual appliance available from the VMware Labs: http://labs.vmware.com/flings/vcma Network connection to the vCMA virtual appliance; can use built-in VPN client VMware vSphere and VMware vCenter
Read More…
