Reading Time: 3 minutesThe new VMware vSphere 6.5, recently available in GA, increase all configuration maximums to new limits (compared to the 6.0 and previous versions). Maybe we can say with no limit, or at least, to be serious, with really huge numbers compared to the actual needs and the existing compunting power. Those new limits are both for scalability aspect, but also to fit with possible performance requirements, considering that a bigger number of business critical applications are going in the virtual environment. For more information see the official docs Minimum & Maximum for VMware vSphere 6.5.
Most viewed posts
Installing ESXi 8 with an unsupported CPUVMware ESXi 8 has dropped the compatibility with a lot of old CPU models, a...
Upgrade Rocky Linux from 8.10 to 9.4Debian like distributions have a nice option to manage distribution upgrade...
ESXi – Partitions layout of system diskIn ESXi the partitions schema is automatically defined by the installation...
Download the legacy vSphere ClientThe legacy C# vSphere Client for Windows is no more available for vSphere 6...
STS Signing Certificates are about to expire on vCenter ServerThe vCenter Server Security Token Service (STS) is a Web service that issue...
ESXi free is back!One year ago, Broadcom killed the Free vSphere Hypervisor, but now, with th...
Check Horizon Connection Server replication statusHorizon allows you to configure one or more replica Connection Server insta...
Are you ready for Veeam Backup & Replication 13?Veeam Backup & Replication 13, the next next major release, will be pro...
How to disable cloud-init on Ubuntu ServerCloud-init is a powerful configuration tools used in several Linux distribu...
Browsing Posts tagged ESXi
Reading Time: 2 minutesWith the new vSphere 6.5 the legacy Windows vSphere Client is finally dead! Was supposed also during the beta of vSphere 6.0, but in the RC a new C# client has appear to avoid this kind of transition. But also to avoid the new limits dictated by the vSphere Web Client, like the huge depency from Acrobat Flash! With version 6.5 there are some interesting changes in the clients for VMware vSphere:
Reading Time: 4 minutesIf you are running an HP customized image of ESXi on some old Proliant server, you may have some issues as describe in KB 2094618 (The hp-ams process does not stop when restarting ESXi management agents on HP ProLiant G5, G6 and G7-series servers) When restarting ESXi management agents on HP ProLiant G5, G6 and G7-series servers running versions of HP Agentless Management Service (AMS) prior to 10.1.0 , you experience these symptoms: In the Recent Tasks pane of vCenter Server, you see multiple tasks in the In Progress state Virtual machines that still […]
Reading Time: 3 minutesVMware best practices for virtual networking, starting with vSphere 5, usually recommend the vmxnet3 virtual NIC adapter for all VMs with a “recent” operating systems: starting from NT 6.0 (Vista and Windows Server 2008) for Windows and for Linux that include this driver in the kernel, and for virtual machines version 7 and later. For those operating systems the choice is normally between the e1000 or the vmxnet3 adapter: the new virtual machine wizard suggest the e1000 for the recent Windows systems, but only because this driver is included in the OSes. Historically there were some […]
Reading Time: < 1 minuteWhen you create a new virtual machine in VMware vSphere (or also on a standalone ESXi) a default virtual hardware is choosed, according with the version of the ESXi. You can choose your own (with the custom wizard) or upgrade later, but note that the virtual hardware upgrade from the vSphere Client will always upgrade to the latest version supported by the host. Otherwise the upgrade from the vSphere Web Client you can choose the different version of virtual hardware.
Reading Time: 3 minutesVMware has announced the End of Availability (“EoA”) of all versions of vSphere Enterprise, vSphere with Operations Management Standard and vSphere with Operations Management Enterprise. The EoA effective date is June 30, 2016. After these dates, you will only be able to purchase these products on an exception basis VMware has also announced price changes for vSphere with Operations Management Enterprise Plus from $4,245 per CPU to $4,395 per CPU, and VMware vCenter Server™ Standard from $4,995 per instance to $5,995 per instance (referenced pricing represents suggested MSRP for the U.S., in USD; regional prices […]
Reading Time: 3 minutesAs you probably know VMware vSphere 6.0 had a critical issue con its Change Block Tracking (CBT) implementation that can impact all incremental backup with “VMware native” backup program (all agent-less implementation using the VMware VDAP API). This issue occurs due to an issue with CBT in the disklib area, this causes the change tracking information of I/Os that occur during snapshot consolidation to be lost. The main backup payload data is never lost and it is always written to the backend device. However, the corresponding change tracking information entries which occur during the consolidation task are missed. […]
© 2025-2011 vInfrastructure Blog 
| Disclaimer & Copyright
| Disclaimer & Copyright