introducing-vmware-tools-10-1-and-10-0-12

The next major release of VMware Tools. Please find a repost of VMware article from Eric Gray from VMware VSphere Blog.

The collection of in-guest drivers and agents that optimize VM performance and increase manageability – will be delivered with VMware vSphere 6.5, and is also downloadable as of today from My VMware. As usual, this version of VMware Tools is compatible with previous vSphere releases, and several enhancements improve the overall manageability experience when used in conjunction with vSphere 6.5.

Bundling of Tools for most popular guests only

VMware ESXi 6.5 includes VMware Tools for the most commonly used guest operating systems; Tools for other guests are available for download from My VMware. Similarly, Tools updates for those same bundled guests will be distributed through Update Manager, as they have been in the past, via the tools-light VIB.

Bifurcation of Tools for legacy and current guests

This release of VMware Tools is comprised of two separate delivery vehicles. VMware Tools 10.1 will be available for OEM-supported guest operating systems only. Legacy guests that have fallen out of support by their respective vendors will be covered by “frozen” VMware Tools 10.0.12. The frozen Tools will not receive feature enhancements going forward. Note, therefore, that the logical upgrade path from 10.0.9 is not 10.0.12 for the vast majority of workloads – rather, it is 10.1.  For more information about support categorization for guest operating systems, see KB 2015161.

The following table depicts the two changes described above:

VMware Tools

Photo courtesy of VMware vSphere Blog

Guest OS granularity changes

With Tools 10.1 and 10.0.12 there are now two ISO images for certain families of guest operating systems in order to accommodate the bifurcation described above. Consequently, the configurable guest OS attribute for some guests in vSphere 6.5 has become more precise in order to support this change.

The most notable example of this change is CentOS: In vSphere 6.5, CentOS guest selections are available for CentOS 7, CentOS 6, and CentOS 4/5. In previous vSphere releases, these versions were all combined into a single selection: CentOS 4/5/6/7. Administrators can either edit the guest OS type or leverage the new VM configuration option tools.hint.imageName to ensure the proper ISO image is mounted to these VMs for Tools install and upgrade.

Please be aware that current Linux distributions ship with Open VM Tools, so most CentOS 7 VMs are likely running OVTs and are not affected by the above scenario. However, for those customers that have chosen to run the vSphere-bundled “Tar Tools” instead, please keep this change in mind.

Detailed display of type and version information in the Web Client

VMware Tools have always had two different designations: one is a human-readable version number, such as 10.0.7, and the other is an internal code, like 10247. With vSphere 6.5, the Web Client now displays both variations of the version number as well as the specific type of Tools installed in the guest OS, such as MSI, OSP, OVT, or TAR Tools.

VMware Tools

Photo courtesy of VMware vSphere Blog

Signed ISO images

VMware Tools have always been distributed as ISO images that can be mounted to individual VMs in order to install or upgrade. VMware ESXi 6.5 introduces a new layer of security by cryptographically verifying these ISO images each time they are accessed. To facilitate this verification, Tools distributions now include additional files with appropriate hashes. If manually extracting, moving, or curating a Tools repository, please ensure all of the supporting bundled files remain together.

Future Tools upgrades for older vSphere VMs

Given the very broad backward and forward compatibility of VMware Tools, it is possible that some customers are running VMs with the Tools that shipped as part of very old vSphere releases. vSphere 5.0 and 5.1 recently reached End of Support, and the VMware Tools that were bundled with those releases are also destined for a similar fate. Therefore, this is a great time to start planning to upgrade Tools 8.x and 9.0.x to the current version. In the future, those older Tools releases will not be directly upgradable to the latest Tools; instead, a two-phase upgrade will be required at that time.

New and more detailed documentation

One of the goals of decoupling the release of VMware Tools and vSphere was to enable more detailed information about updates through release notes. Starting with Tools 10.1, release notes will be further enhanced to include a table documenting the precise version number of each individual driver and component. Going beyond release notes, we now also offer stand-alone documentation for VMware Tools 10.1, including more information about management and functionality of the various elements.

Concluding

We hope that the new efforts to treat VMware Tools as top-tier products are beneficial to all customers. The enhanced documentation, security, and product functionality should be welcome news to vSphere administrators everywhere. The continued bundling certain popular Tools versions for supported and legacy guests, along with updates through VUM, ought to quell some of the concerns raised last year when we first announced the separation of Tools and vSphere.

Download: VMware Tools 10.1 and VMware Tools 10.0.12

Here are some other articles and tips regarding VMware Tools:

Sign up for our newsletter today!

Sign up for Performance Analyzer today and start 30 days for free.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.