Browsing Posts in vSphere

VMware has released (on Feb, 15th) a new vCSA version: vCenter Server 6.5 U1f, with build number 7801515. This release patches the vCSA operating system (Photon OS) mainly against two vulnerabilities: bounds-check bypass (Spectre-1, CVE-2017-5753) and rogue data cache load issues (Meltdown, CVE-2017-5754). As of now, there is still no patch for branch target injection vulnerability (Spectre-2, CVE-2017-5715). VMware has also updated the security advisory dealing with all of its virtual appliances updates for Spectre and Meltdown vulnerabilities, VMSA-2018-0007. But note that VMSA-2018-0004.2 has not been updated yet, and it still report that the suggested version for […]

After the special discount for all the eBook (and video) on Packt site, now it’s the turn for the printed book: for one week only, get 25% off all Packt print books as well as FREE shipping! A good opportunity if you want to buy the Mastering VMware vSphere 6.5 book, or also other books from Packt.

This is an article realized for StarWind blog and focused on the pro and cons of an upgrade to vSphere 6.5. See also the original post. VMware vSphere 6.5 is the latest version of the enterprise server virtual platform from VMware, but the new beta it’s already there for testers. Actually the next version it’s (in the beta) and you can register at

One month ago, the Mastering VMware vSphere 6.5 book has been published and we already have some interesting feedback. Considering that it’s the first book experience (not only for me but also for the other co-authors), and that neither of us it’s a native English speaker, we are really interested in more feedback (positive or negative) as possible, in order to improve, in the case of a new edition or a new book.

There are some cases where the VMware Tools installation, if you run it from the vSphere platform, remain pending and you cannot end this task anymore. Also if VMware Tools are up and running properly. It’s something boring because may block you in several other tasks.

Seems that the vSphere Web Client has some bugs, also with the latest vSphere 6.5 version. It should be the main web client (see a list of possible GUI clients in vSphere 6.5), but sometimes does not work as expected (without considering possible Flash bugs). If you are using vSphere vApp (a feature that requires a DRS enabled cluster), you may have some issues when you need to remove a VM outside from a vApp.

VMware vSphere, during its history and the different versions, has got several types of GUI clients. One of the most used (not the first, but the standard one since Virtual Infrastructure 3.0) was the vSphere Client for Windows. But on May 2016 VMware has announced that the Legacy C# Client (aka thick client, desktop client, or vSphere Client) will no longer be available with the vSphere 6.5 release, replaced by web-based clients. With VMware vSphere 6.5 there are mainly two different “Web Client”:  the vSphere Web Client (based on Flash and introduced in vSphere 5.0) […]

Meltdown and Spectre are critical vulnerabilities existing in several modern CPU: these hardware bugs allow programs to steal data which is currently processed on the computer. Meltdown and Spectre can affect personal computers, mobile devices, server and several cloud services. Actually, the only way to minimize those security risks is to patch your operating systems, but also the hypervisor level and the hardware level (if vendors provide a new firmware).

One month ago, VMware has released a new branch of the VMware Tools, the version VMware Tools 10.2.0 some a new interesting feature: the offline VIB bundle. With this package, you can simply upgrade the embedded VMware Tools components in your VMware ESXi hosts in order to continue to update your VMware Tools as usual!

Now that the PSOD on vSphere 6.5 and 10 Gbps NICs issue is finally solved seems that vSphere 6.5 critical bugs are closed, but it’s not totally true. During an upgrade from a vSphere 6.0, I’ve found a really strange iSCSI storage issues where all the VMs on the iSCSI datastore were so slow to become un-usable. First I was thinking about drivers or firmware, in the hosts and in the NIC (1 Gbps) or the firmware on the storage.

On October 2017, I wrote a post about a possible issue with vSphere 6.5 and 10 Gbps NICs (mostly standard on new deployment). The final result was a PSOD (Purple Screen Of the Death) and no solution was available (yet). VMware KB 2151749 describe this issue as related to possible upgrade at vSphere 6.5. But other customers have report the issue also on new deployment. Veeam, one of the first vendor to found this issues (from their customers), reports that the issues is due to network-intensive activities such as backup over NBD or vMotion randomly triggering one. […]

As written in a previous post, some months ago, I’ve started a huge personal project that consumes all my spare free time. This project was a new book on VMware vSphere 6.5, really ambitious considering that will be a “Mastering” book, but the title and part of the content were not negotiable with the editor. Finally, the book Mastering VMware vSphere 6.5 is done and it’s now available on Packt site (and in the future also on Amazon).

This is an article realized for StarWind blog and focused on the design and implementation of stretched cluster. A stretched cluster, sometimes called metro-cluster, is a deployment model in which two or more host servers are part of the same logical cluster but are located in separate geographical locations, usually two sites. In order to be in the same cluster, the shared storage must be reachable in both sites. Stretched cluster, usually, are used and provided high availability (HA) and load balancing features and capabilities and build active-active sites.

VMware vSAN should manage better VM snapshots compared with traditional storage and VMFS datastores. The reason is the new (v2) on-disk format in VSAN 6.0 and the new filesystem that is used: VirstoFS. VirstoFS is the first implementation of technology that was acquired when VMware bought a company called Virsto a number of years ago. Also there is a new sparse format called vsanSparse. These replace the traditional vmfsSparse format (redo logs).

© 2018 © 2013 vInfrastructure Blog | Hosted by Assyrus