Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Meltdown and Spectre Effects on vRealize Operations Manager 6.7 (53431)

Last Updated: 7/14/2020Categories: InformationalTotal Views: 2959Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

vRealize Operations Manager is not effected by Meltdown or Spectre.

In the interest of compliance and security protocols, Page Table Isolation (PTI) has been enabled in vRealize Operations Manager 6.7 for the underlying SLES Operating System.
Due to other performance optimizations in vRealize Operations Manager 6.7, there is no performance degradation with PTI enabled.

PTI can still be disabled on vRealize Operations Manager 6.7 by following the steps in the Resolution section.

Cause

Meltdown and Spectre vulnerabilities both require access to the server; this is critical for systems that have unprivileged user accounts and allow unprivileged users to login.
vRealize Operations Manager does not have unprivileged user accounts
The only way to log into a vRealize Operations Manager node is by using the root or admin accounts.

Impact / Risks

Potential Meltdown or Spectre related breaches may occur if unprivileged users are added to the vApp and PTI is disabled.

Resolution

PTI on vRealize Operations Manager 6.7 can be disabled at your own risk by following the steps below:

Log into the Admin UI as admin.

Click the Take Offline button to take the vRealize Operations Manager cluster offline.

Enter a Reason, and click OK.

Log into the Primary node as root via SSH or Console.

Open /boot/grub/menu.lst in a text editor.

In the line(s) starting with kernel, change pti=on to pti=off.

Example: kernel /vmlinuz-3.0.101-108.21-trace root=/dev/sda3 append   resume=/dev/sda2 splash=silent showopts vga=0x311 elevator=noop pti=off noexec=on nousb audit=1​

Note: Change the pti= entry on all kernel lines.

Save and close the file.

Repeat steps 4-7 on all other nodes in the cluster.

Issue a Guest Restart on each node via the vSphere Client.

Log into the Admin UI as admin.

Click the Bring Online button to bring the vRealize Operations Manager cluster online.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Manager

VMware vRealize Operations

Related Versions:

VMware vRealize Operations Manager 6.7.x

Take Our Survey

Support Assistant