What's New in vSphere 8

-

 vSphere 8 offers several new features and enhancements, including ¹:

- *vSphere Distributed Services Engine*: This feature unlocks the power of Data Processing Units (DPUs) for hardware-accelerated data processing, improving infrastructure performance, security, and simplifying DPU lifecycle management.

- *vSphere with Tanzu*: This feature consolidates Tanzu Kubernetes offerings into a single unified Kubernetes runtime, allowing for increased availability and flexibility.

- *Lifecycle Management*: vSphere 8 introduces DPU support for vSphere Lifecycle Manager, automatically remediating the ESXi installation on a DPU in lock-step with the host ESXi version.

- *AI & ML*: vSphere 8 offers unified management for AI/ML hardware accelerators, making it simpler to consume complementary hardware devices.

- *Guest OS & Workloads*: vSphere 8 introduces Virtual Hardware version 20, which brings new virtual hardware innovations, enhances guest services for applications, and increases performance and scale for certain workloads.

- *Resource Management*: vSphere 8 offers enhanced DRS performance, significantly improving when PMEM is present by leveraging memory statistics, resulting in optimal placement decisions for VMs without affecting performance and resource consumption.

- *Security & Compliance*: vSphere 8 takes further measures to be secure by default, including preventing the execution of untrusted binaries, only supporting TLS 1.2, and running ESXi daemons and processes in their own sandboxed domain.

Additionally, vSphere 8 Update 2 offers ²:

- *Reduced Downtime Upgrade*: This feature reduces the downtime required for vCenter upgrades, allowing for a migration-based approach that keeps vCenter services online during the upgrade process.

- *Resilient vCenter Patching*: This feature provides clearer guidance on taking vCenter backups before patching and updating, and automatically performs a LVM snapshot before patch/update tasks.

Comments

Post a Comment

Popular posts from this blog

VMware:- Esxi Log File Locations

-
Enable SSH and connect the host through CLI tool-  *Authentication- /var/log/auth.log *ESXi host agent log - /var/log/hostd.log *Shell log - /var/log/shell.log *System messages - /var/log/syslog.log *vCenter Server agent log - /var/log/vpxa.log *Virtual machines - The same directory as the affected virtual machine's configuration files, named vmware.log and vmware*.log. For example, /vmfs/volumes/datastore/virtual machine/vmware.log *VMkernel - /var/log/vmkernel.log *VMkernel summary - /var/log/vmksummary.log *VMkernel warnings - /var/log/vmkwarning.log *Quick Boot - /var/log/loadESX.log *Trusted infrastructure agent - /var/run/log/kmxa.log *Key Provider Service - /var/run/log/kmxd.log *Attestation Service - /var/run/log/attestd.log *ESX Token Service - /var/run/log/esxtokend.log *ESX API Forwarder - /var/run/log/esxapiadapter.log
Read more

ESX and vCenter Alarms

-
Image
  Definition An  Alarms  is a   notification  that are activated in response to an event, a set of conditions, or the state of an inventory object. An alarm definition consists of the following elements in the vSphere Client: ·  Name and description - Provides an identifying label and description. ·  Targets - Defines the type of object that is  monitored. -  VM\  DataSore \N\W  etc. ·  Alarm Rules - Defines the event, condition, or state that triggers the alarm and defines the notification severity. It also defines operations that occur in response to triggered alarms. ·  Last modified - The last modified date and time of the defined alarm.   Alarm categories – Alarms have the following severity levels: ·  Normal –  green  -   Status is Good. The health of the object is Normal ·  Warning – yellow  -  Status is Warning – The Object experiencing Some Problem ·  Ale...
Read more

Convert VMware Snapshot into Memory Dump

-
Image
  Convert VMware Snapshot into Memory Dump Background   This document explains about generating a memory dump for a VMWare Virtual Machine when the machine becomes unresponsive. VM becomes unresponsive for various reasons, you may not be able to get into any OS related settings or access any application. Even users may get not be able to access any shares or resources of this machine.   In this type of situation Memory dump would be required to  analyze  the cause. Even if the OS is configured to generate a Memory Dump for System Crashes, it would not be able to generate a Memory Dump for System Unresponsiveness most of the  times. But  with a VMWare VM, you can take a snapshot of the machine when it is unresponsive and then use vmss2core.exe tool to convert the snapshot to a Memory Dump. The target audience for this information is any technician that is responsible for creating and deleting snapshot in the Levi virtualization environment.   Note ...
Read more