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...
Check Horizon Connection Server replication statusHorizon allows you to configure one or more replica Connection Server insta...
Veeam Managed Hardened Repository installation and configurationThe Veeam Managed Hardened Repository is a bootable ISO based on Rocky Linu...
Are you ready for Veeam Backup & Replication 13?Veeam Backup & Replication 13, the next next major release, will be pro...
VMware Standalone Converter guest OS support (2024)VMware® vCenter Converter Standalone provides an easy-to-use solu...
Reassign the schema master on an Horizon Connection ServerHorizon allows you to configure one or more replica Connection Server insta...
Moving the Veeam Backup Catalog to another driveAs descrived in the previous post (Optimize the consumed space of the Veeam...
Enable UEFI boot in VMware WorkstationIn VMware Workstation 17.6.1, when I create a Rocky Linux VM, there is no w...
Upgrade Rocky Linux from 8.10 to 9.4Debian like distributions have a nice option to manage distribution upgrade...
ESXi free is back!One year ago, Broadcom killed the Free vSphere Hypervisor, but now, with th...
Browsing Posts tagged vCenter
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: 3 minutesThe new release of VMware vSphere 6.5 will finally add some interesting news of the vCenter Server. Not only the virtual appliance (Linux based) version is not fully featured (was almost in version 6.0, but still with the big limit of VMware Update Manager available only for Windows), but now has some features only for this version and the Windows one become the limited version. First sign was the Fling for the migration from a vCenter edition to the VCSA: the official Windows vCenter Server to vCenter Server Appliance (VCSA) Migration Tool which is part […]
Reading Time: 2 minutesVMware ha da poco annunciato due importanti novità sui client per vSphere, sia per il vecchio client Windows sia per quello Web: il client legacy basato su C# ed eseguibile solo su sistemi Windows non sarà più disponibile dalla prossima versione di vSphere (finalmente, visto che il cliente era persino più grosso di ESXi). Le versioni 5.5 e 6.0 non saranno affette il cliente web basato su Adobe Flash sarà presto sostituito (finalmente) da un client web totalmente HTML5 (al momento già disponibile come Fling).
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: 2 minutesVMware vSphere 6.0 has got some issues, like the several related to CBT and data protection, during the first years of its life. Mostly is finally resolved, but you may still have strange issuesespecially during the upgrade procedure (most when you start from a vSphere 5.1 version). I notice, after an upgrade, also a strange behavior with vMotion where live VM migration fails with this error: A general system error occurred: PBM error occurred during PreMigrateCheckCallback: No connection could be made because the target machine actively refused it.
Reading Time: 4 minutesSe state pianificando un aggiornamento in-place verso vCenter Server 6.0 (mi riferisco alla versione installabile per Windows) allora dovrete leggere molto attentamente le varie informazioni presenti nella pagina vSphere Upgrade Center. Naturalmente l’aggiornamento non è l’unica opzione. In alternativa è anche possibile creare un nuovo vCenter Server e passare tutto sul nuovo sistema. Anzi… potrebbe essere persino l’occasione per passare al vCenter Server Appliance (e c’è pure un Flings che vi aiuterà a migrare i dati). Però in alcuni scenari è necessario mantenere il vCenter (ad esempio per il nome DNS) e procedere con un […]
© 2025-2011 vInfrastructure Blog 
| Disclaimer & Copyright
| Disclaimer & Copyright