The new VMware Virtual SAN (or vSAN) 6.6 adds several enchaments and new features as described in the announce notes. Some interesting news are related to security aspects and how data-at-rest could be protected: one option could be new vSphere 6.5 VM encryption format but now it’s also possible use the native vSAN encryption. Duncan’s post explains the difference of those two approaches.
The new VMware Virtual SAN (or vSAN) 6.6 adds several enchaments and new features as described in the announce notes. Most of those aspects are related to data and cluster resiliency (as expected by a storage solution), including:
VMware has announced the discontinuation of its third party virtual switch (vSwitch) program, and plans to deprecate the VMware vSphere APIs used by third party switches in the release following vSphere 6.5 Update 1. Subsequent vSphere versions will have the third party vSwitch APIs completely removed and third party vSwitches will no longer work. In the past years, VMware has recommended the Nexus 1000V users to move into the VMware vSphere Distributed Switch to avoid future problems, now it’s clear the product version where you can go.
Recently VMware has released a few security patches that will prevent a guest from execute code on the ESXi host and breaking the isolation of a virtual machine. This has been possible based on heap buffer overflow and uninitialized stack memory usage in SVGA, using this bug may allow a guest to execute code on the host. Note that this particular issue impacts ESXi 6.0 or later as also latest version of VMware Workstation, Player and Fusion.
If you are using the legacy VMware vSphere Client on Windows 10 you may have some issues with the VM console that display only a part of the screen and leave blank other parts. You can use other clients (like the Web Client if you have vCenter or the Host UI if you have at least ESXi 6.0U2), but maybe you will have other issues (for example on ESXi 6.0 host UI console mouse may not work well or not at all).
In VMware vSphere there was an hystorical limit of VMDK disks around 2 TB (2 TB – 512 B), but the real “usable” was also less due to the need to make a snapshots on it (if you want use native backup solutions) and depending on the block size (for more informations see Veeam KB 1091). Starting with vSphere 5.5 was finally possibile have bigger disks up to 62 TB (that I will call just “jumbo” disks), but again with several limits describe in VMware KB 2058287 (Support for virtual machine disks larger than 2 TB […]
Now that the new VMware vSphere 6.5 is in GA, most people are starting considering to upgrade (or start from scratch) with this version, instead of vSphere 6.0 (or also 5.5). But please consider this product like a major release, there are several changes, but also new features and scalability properties that make interesting for each new environment, but also for existing customers (with an active subscription if you have a 5.5 version, so that you can also upgrade your 5.x license keys). But like each new version you have to make some consideration first […]
After the official announce at the last VMworld EU, finally VMware vSphere 6.5 is now GA and available for the download. There are several news in the Web client, in new vCenter, in the availability, in VSAN 6.5, in the new security features, new scalability and lot of other stuff.
The 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.
The 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 […]
VMware 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 […]