Browsing Posts in vDesign

Reading Time: 9 minutesWith all those Meltdown, Spectre, Foreshadow, … bugs that affect several CPU, you may be interested in what can be the overall performance impact for all the related patches. There isn’t a simple answer, because it really varies by the processor vendor (Intel CPUs are more affected than AMD CPUs), probably also by CPU the family, for sure by the type of workloads (CPU bound workloads will be more affected, but it depends also on which instructions are used), … but also the type of environment.

Reading Time: 3 minutesVMware NSX Data Center for vSphere is the new name of NSX-v and NSX-t for the on-prem case, and version 6 is actually referring to the specific edition for VMware vSphere that use the vCenter Server UI has the main UI also for all the NSX part. There are other NSX products, but VMware has just announced a new minor version for the vSphere related product: NSX Data Center for vSphere v6.4.2 it’s out. The release notes describe all the new features and improvement of this release:

Reading Time: 7 minutesThe L1 Terminal Fault (aka Foreshadow) bug is another speculative execution side channel attack that affects Intel Core processors and Intel Xeon processors only. For VMware vSphere, there are some patches available as described in this document: VMSA-2018-0020. All patches have been released on August, 14th 2018.

Reading Time: 4 minutesThis is the year of the security threats originated by hardware level bugs. The year has begun with the Spectre and Metldown bug with several months of possible solutions, new BIOS, new patches… and new variants of those bugs (like Spectre V4 and V5). But we are far from the solution because other bugs came out. And more will come out… All the software used at the microprocessor level and all the optimizations will probably be a good vector for new attack patterns. As already written, we are still far from the solution.

Reading Time: 3 minutesIn the last Veeam Community Forums Digest newsletter there is an interesting note about possible performance issues in VMware vSphere backup based on hot-add transport mode. VMware has confirmed that the increased Hot Add times experienced by some Veeam customers who have installed Veeam Backup & Replication Update 3a and the reason is the latest Virtual Disk Development Kit (VDDK) 6.5 version used in U3a to support also vSphere 6.5 Update 2.

Reading Time: 3 minutesOne common way to backup the VMware vCenter Server Appliance (VCSA) is to manage as a common VM and use a backup solution to backup (and restore) the entire VM. But it’s approach does not always work, for example in the case of a database corruption the VM restore could be not working. Starting with vSphere 6.5 and the new VCSA 6.5 was possible to use also a native backup solution integrated with the vCenter Server Appliance Management Interface (VAMI). But it was a manual operation (some scripts are available to automate and schedule it).

Reading Time: 16 minutesThis is an article realized for StarWind blog and focused on the possible security threats in a virtual environment. See also the original post.

© 2025-2011 vInfrastructure Blog | Disclaimer & Copyright