Accelerate Hybrid Cloud AI Workloads Solution Brief

Total Page:16

File Type:pdf, Size:1020Kb

Accelerate Hybrid Cloud AI Workloads Solution Brief Solution Brief Data Center | Hybrid Cloud Accelerate Hybrid Cloud AI Workloads Ease your journey to hybrid/multicloud with a reference architecture for Intel® technology and VMware Cloud Foundation Executive Summary To remain competitive in today’s world, organizations need a modern data center. Companies using these data centers must accelerate their product development, compete more successfully at a lower cost, and Solution Benefits reduce their downtime and maintenance overhead. Technology must move and change with the times—solutions for hosting applications and Intel’s VMware Cloud Foundation services must innovate and change as well. reference architecture takes advantage of Intel® compute, Companies with older and outdated data centers will want to meet these memory, storage, and networking challenges by upgrading to hybrid cloud solutions, where the data center innovations to help enable can easily and seamlessly interface between on‑premises and cloud software-defined data centers and systems. Based on VMware Cloud Foundation with VMware Tanzu, Intel hybrid/multicloudOptional adoption. partner logo goes here addressed these requirements by offering a hybrid/multicloud reference • Fast AI inference. AI workloads architecture—available in a Base and Plus configuration—that is easily can benefit from innovations deployable and manageable for virtual machines (VMs) and containers. from Intel such as Intel® DL Boost. • Flexibility and portability. VMware Cloud Foundation helps enable enterprises to run their workloads where it makes most sense, whether that’s Private Public on‑premises, in a public cloud, Cloud Cloud or in several clouds at once. VMware Cloud Foundation VMware VMware VMware VMware vSphere vRealize Suite vSA S‑T VMware SDDC Manager Figure 1. VMware Cloud Foundation supports software-defined data centers that can benefit greatly from Intel® compute, memory, storage, and networking technologies. Solution Brief | Accelerate Hybrid Cloud AI Workloads 2 Business Challenge: Building a Hybrid Cloud • Machine-learning inference. Once a model is trained, it Machine-Learning Architecture can be run on new data sets to uncover hidden insights. Inference is compute-intensive, and can benefit from A data center and the machine learning that a data center innovations from Intel such as Intel® Deep Learning Boost enables needs to run optimally for a business to stay (Intel® DL Boost) with Vector Neural Network Instructions competitive. Balancing high performance and cost is a (VNNI)—available starting with vSphere 7 and ESXi 7.0, continual challenge. Enterprises seek infrastructure that which are foundational components of the VMware Cloud is characterized by less downtime, less setup time, easier Foundation 4 platform. maintenance, and lower overhead costs—without sacrificing • Data warehousing and analytics. Data warehouses are performance. Legacy data centers cannot take advantage considered one of the core components of business of the cost efficiencies and new technologies available in a intelligence. They are a central location to store data from one hybrid/multicloud environment. Such data centers cannot or more disparate sources as well as current and historical adapt to changing workload requirements quickly and nimbly. data. The VMware hybrid/multicloud platform supports data For companies with outdated data center technologies, warehousing, including industry‑proven solutions based on meeting these challenges involves replacing legacy hardware Microsoft SQL Server 2019 or Oracle Database 19c. and software with modern, hybrid‑cloud‑capable solutions that can accelerate the entire software and hardware provisioning, deployment, and maintenance lifecycle along with application development, testing, and delivery. But, especially for machine learning, companies may be daunted A Closer Look at Intel® DL Boost and VNNI by assembling and maintaining hybrid cloud infrastructure. 2nd Gen Intel® Xeon® Scalable processors offer Machine learning requires large datasets that are difficult to something unique that is not available with any other get into the cloud, and machine‑learning models must be processor on the market: Intel® DL Boost with VNNI. continuously retrained and updated. In addition, data for This technology takes advantage of, and improves machine learning can be sensitive, highly regulated, or may upon, Intel® AVX-512. VNNI improves AI performance contain intellectual property, which raises the data’s security by combining three instructions into one—thereby concerns. Intel and VMware have teamed up to help take optimizing the use of compute resources and utilizing the the guesswork out of building a machine‑learning solution. cache more effectively and avoiding potential bandwidth VMware Cloud Foundation is a hybrid cloud platform that bottlenecks. In Intel benchmarks, VNNI speeds the runs on Intel® hardware, offering an easily deployable and delivery of inference results by up to 30x, compared to manageable hybrid/multicloud platform for managing VMs the previous-generation Intel Xeon Scalable processor.1 and orchestrating containers. Typical Workloads in the Hybrid/Multicloud Data Center Solution Value: High Performance in the The combination of VMware Cloud Foundation and Intel® Hybrid/Multicloud Environment technology running on VMs or in containers can support a wide variety of use cases: VMware Cloud Foundation is a full‑stack HCI solution that helps accelerate adoption of hybrid/multicloud • Machine-learning training. Image classification is one of environments. When combined with Intel technology, the most popular use cases for deep learning. Training VMware Cloud Foundation provides consistently high such models can be time‑consuming and, without the performance, reduced data center footprint, and efficient right tools, requires specialized skills. The VMware operations management. Cloud Foundation platform works with various machine‑ learning frameworks, including DataRobot, which is a With the end-to-end solution that Intel and VMware offer, popular automated machine‑learning platform that takes enterprises can quickly launch database processing and advantage of optimizations for Intel® architecture. With AI, and scale workloads to accommodate future needs. The a library of hundreds of powerful open‑source machine‑ unified cloud solution presented in this solution brief can learning algorithms, the DataRobot platform applies many run containerized applications and traditional VMs that are best practices to machine learning and helps to accelerate located in an on‑premises data center as well as in the public and scale data science capabilities while increasing cloud, such as on Amazon Web Services. transparency, accuracy, and collaboration. Solution Brief | Accelerate Hybrid Cloud AI Workloads 3 Container provisioning and lifecycle management are This solution provides infrastructure and operations across provided by VMware Tanzu Kubernetes Grid (TKG). The private and public clouds with excellent performance and hybrid/multicloud structure of the solution allows enterprises reliability from Intel® hardware components. to extend available resources and easily migrate workloads Users can also take advantage of Intel DL Boost with VNNI. from on‑premises to the cloud and back. Intel conducted experiments to show the improvement of Enterprises can use Intel® Optane™ technology to boost inference performance with an Intel architecture‑optimized their VMware Cloud Foundation workload performance by container stack that uses the new VNNI instruction set. placing data closer to the CPU. This technology is a new Our tests benchmarked the ResNet50 v1.5 topology with class of non-volatile memory and storage media that fills the int8 and fp32 precision, using the Intel® Optimization gap between high‑performing volatile memory and lower‑ for TensorFlow container stack with Intel’s Model Zoo performing NAND storage and HDDs. By placing data closer pretrained models. We ran three tests:3 to the CPU, Intel Optane technology helps architects to confidently deploy an agile, high-performing infrastructure • Compare the performance improvement of Intel DL that helps organizations create innovative services and Boost with VNNI using int8 precision against fp32 optimize their infrastructure investments. precision. As shown in Figure 2, int8 precision enabled a 4.1x improvement for the Base configuration and a Intel Optane technology can be deployed in two different ways: 4.38x improvement for the Plus configuration. For a small • Intel® Optane™ persistent memory (PMem) gives enterprises decrease in precision, performance quadrupled. the ability to extract more from larger datasets by combining • Compare throughput from the default TensorFlow more capacity and native persistence in a DIMM form factor. container against a container using the Intel Optimization Data can be accessed, processed, and analyzed in near real for TensorFlow. Framework optimizations from the Intel time to deliver deep insights, improve operations, and create Optimization for TensorFlow can provide 2.33x improvement new revenue streams. for the Base configuration and 2.61x performance • Intel® Optane™ SSDs help remove data bottlenecks to improvement for the Plus configuration. accelerate transactions and time to insights, so users get what • Compare the results of running VMware Cloud Foundation they need, when they need it. With high quality of service 4.0.1 (which takes advantage of Intel DL Boost and VNNI) and at least 6x faster performance
Recommended publications
  • SPP 2019.09.0 Component Release Notes
    SPP 2019.09.0 Component Release Notes BIOS - System ROM Driver - Chipset Driver - Network Driver - Storage Driver - Storage Controller Driver - Storage Fibre Channel and Fibre Channel Over Ethernet Driver - System Driver - System Management Driver - Video Firmware - Blade Infrastructure Firmware - Lights-Out Management Firmware - Network Firmware - NVDIMM Firmware - PCIe NVMe Storage Disk Firmware - Power Management Firmware - SAS Storage Disk Firmware - SATA Storage Disk Firmware - Storage Controller Firmware - Storage Fibre Channel Firmware - System Firmware (Entitlement Required) - Storage Controller Software - Lights-Out Management Software - Management Software - Network Software - Storage Controller Software - Storage Fibre Channel Software - Storage Fibre Channel HBA Software - System Management BIOS - System ROM Top Online ROM Flash Component for Linux - HPE ProLiant DL380 Gen9/DL360 Gen9 (P89) Servers Version: 2.74_07-21-2019 (Optional) Filename: RPMS/i386/firmware-system-p89-2.74_2019_07_21-1.1.i386.rpm Important Note! Important Notes: None Deliverable Name: HPE ProLiant DL360/DL380 Gen9 System ROM - P89 Release Version: 2.74_07-21-2019 Last Recommended or Critical Revision: 2.72_03-25-2019 Previous Revision: 2.72_03-25-2019 Firmware Dependencies: None Enhancements/New Features: This revision of the System ROM includes the latest revision of the Intel microcode which provides mitigation for an Intel sighting where the system may experience a machine check after updating to the latest System ROM which contained a fix for an Intel TSX (Transactional Synchronizations Extensions) sightings. The previous microcode was first introduced in the v2.70 System ROM. This issue only impacts systems configured with Intel Xeon v4 Series processors. This issue is not unique to HPE servers. Problems Fixed: Addressed an extremely rare issue where a system booting to VMware may experience a PSOD in legacy boot mode.
    [Show full text]
  • Microcode Revision Guidance August 31, 2019 MCU Recommendations
    microcode revision guidance August 31, 2019 MCU Recommendations Section 1 – Planned microcode updates • Provides details on Intel microcode updates currently planned or available and corresponding to Intel-SA-00233 published June 18, 2019. • Changes from prior revision(s) will be highlighted in yellow. Section 2 – No planned microcode updates • Products for which Intel does not plan to release microcode updates. This includes products previously identified as such. LEGEND: Production Status: • Planned – Intel is planning on releasing a MCU at a future date. • Beta – Intel has released this production signed MCU under NDA for all customers to validate. • Production – Intel has completed all validation and is authorizing customers to use this MCU in a production environment.
    [Show full text]
  • SDG Adhoc Reporting
    VMware Deliverable Release Notes This document does not apply to HPE Superdome servers. For information on HPE Superdome, see the following links: HPE Integrity Superdome X HPE Superdome Flex Information on HPE Synergy supported VMware ESXi OS releases, HPE ESXi Custom Images and HPE Synergy Custom SPPs is available at: VMware OS Support Tool for HPE Synergy Information on HPE Synergy Software Releases is available at: HPE Synergy Software Releases - Overview SPP 2021.04.0 Release Notes for VMware vSphere 6.5 BIOS (Login Required) - System ROM Driver - Network Driver - Storage Controller Firmware - Network Firmware - NVDIMM Firmware - Storage Controller Firmware - Storage Fibre Channel Software - Management Software - Storage Controller Software - Storage Fibre Channel Software - System Management BIOS (Login Required) - System ROM Top ROM Flash Firmware Package - HPE Apollo 2000 Gen10/HPE ProLiant XL170r/XL190r Gen10 (U38) Servers Version: 2.42_01-23-2021 (Recommended) Filename: U38_2.42_01_23_2021.fwpkg Important Note! Important Notes: None Deliverable Name: HPE Apollo 2000 Gen10/HPE ProLiant XL170r/XL190r Gen10 System ROM - U38 Release Version: 2.42_01-23-2021 Last Recommended or Critical Revision: 2.42_01-23-2021 Previous Revision: 2.40_10-26-2020 Firmware Dependencies: None Enhancements/New Features: Updated the support for Fast Fault Tolerant Memory Mode (ADDDC) to improve system uptime. Added support to the BIOS/Platform Configuration (RBSU) Time Zones to add Dublin/London (UTC+1). This support also requires the latest version of iLO Firmware, version 2.40 or later. Problems Fixed: This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions.
    [Show full text]
  • Class-Action Lawsuit
    Case 3:20-cv-00863-SI Document 1 Filed 05/29/20 Page 1 of 279 Steve D. Larson, OSB No. 863540 Email: [email protected] Jennifer S. Wagner, OSB No. 024470 Email: [email protected] STOLL STOLL BERNE LOKTING & SHLACHTER P.C. 209 SW Oak Street, Suite 500 Portland, Oregon 97204 Telephone: (503) 227-1600 Attorneys for Plaintiffs [Additional Counsel Listed on Signature Page.] UNITED STATES DISTRICT COURT DISTRICT OF OREGON PORTLAND DIVISION BLUE PEAK HOSTING, LLC, PAMELA Case No. GREEN, TITI RICAFORT, MARGARITE SIMPSON, and MICHAEL NELSON, on behalf of CLASS ACTION ALLEGATION themselves and all others similarly situated, COMPLAINT Plaintiffs, DEMAND FOR JURY TRIAL v. INTEL CORPORATION, a Delaware corporation, Defendant. CLASS ACTION ALLEGATION COMPLAINT Case 3:20-cv-00863-SI Document 1 Filed 05/29/20 Page 2 of 279 Plaintiffs Blue Peak Hosting, LLC, Pamela Green, Titi Ricafort, Margarite Sampson, and Michael Nelson, individually and on behalf of the members of the Class defined below, allege the following against Defendant Intel Corporation (“Intel” or “the Company”), based upon personal knowledge with respect to themselves and on information and belief derived from, among other things, the investigation of counsel and review of public documents as to all other matters. INTRODUCTION 1. Despite Intel’s intentional concealment of specific design choices that it long knew rendered its central processing units (“CPUs” or “processors”) unsecure, it was only in January 2018 that it was first revealed to the public that Intel’s CPUs have significant security vulnerabilities that gave unauthorized program instructions access to protected data. 2. A CPU is the “brain” in every computer and mobile device and processes all of the essential applications, including the handling of confidential information such as passwords and encryption keys.
    [Show full text]
  • NEC V. Intel: a Guide to Using "Clean Room" Procedures As Evidence, 10 Computer L.J
    The John Marshall Journal of Information Technology & Privacy Law Volume 10 Issue 4 Computer/Law Journal - Winter 1990 Article 1 Winter 1990 NEC v. Intel: A Guide to Using "Clean Room" Procedures as Evidence, 10 Computer L.J. 453 (1990) David S. Elkins Follow this and additional works at: https://repository.law.uic.edu/jitpl Part of the Computer Law Commons, Internet Law Commons, Privacy Law Commons, and the Science and Technology Law Commons Recommended Citation David S. Elkins, NEC v. Intel: A Guide to Using "Clean Room" Procedures as Evidence, 10 Computer L.J. 453 (1990) https://repository.law.uic.edu/jitpl/vol10/iss4/1 This Article is brought to you for free and open access by UIC Law Open Access Repository. It has been accepted for inclusion in The John Marshall Journal of Information Technology & Privacy Law by an authorized administrator of UIC Law Open Access Repository. For more information, please contact [email protected]. NEC V. INTEL: A GUIDE TO USING "CLEAN ROOM" PROCEDURES AS EVIDENCE DAVID S. ELKINS* I. INTRODUCTION The recent United States District Court decision in NEC Corp. v. Intel Corp.' has made a significant imprint on the field of copyright law in two respects. The case marks the first time that computer microcode 2 has been held copyrightable,3 and the first time that "clean room" procedures have been used as evidence in an infringement ac- tion.4 Simply put, clean room procedures comprise a method of creating a certain type of technology without the possibility of influence from outside sources. These procedures may be necessary in situations where the mere creation of the technology gives rise to an inference of copy- * J.D., King Hall School of Law, University of California, Davis, 1990; A.B., Univer- sity of California, Berkeley, 1986.
    [Show full text]
  • Beyond MOV ADD XOR – the Unusual and Unexpected
    Beyond MOV ADD XOR the unusual and unexpected in x86 Mateusz "j00ru" Jurczyk, Gynvael Coldwind CONFidence 2013, Kraków Who • Mateusz Jurczyk o Information Security Engineer @ Google o http://j00ru.vexillium.org/ o @j00ru • Gynvael Coldwind o Information Security Engineer @ Google o http://gynvael.coldwind.pl/ o @gynvael Agenda • Getting you up to speed with new x86 research. • Highlighting interesting facts and tricks. • Both x86 and x86-64 discussed. Security relevance • Local vulnerabilities in CPU ↔ OS integration. • Subtle CPU-specific information disclosure. • Exploit mitigations on CPU level. • Loosely related considerations and quirks. x86 - introduction not required • Intel first ships 8086 in 1978 o 16-bit extension of the 8-bit 8085. • Only 80386 and later are used today. o first shipped in 1985 o fully 32-bit architecture o designed with security in mind . code and i/o privilege levels . memory protection . segmentation x86 - produced by... Intel, AMD, VIA - yeah, we all know these. • Chips and Technologies - left market after failed 386 compatible chip failed to boot the Windows operating system. • NEC - sold early Intel architecture compatibles such as NEC V20 and NEC V30; product line transitioned to NEC internal architecture http://www.cpu-collection.de/ x86 - other manufacturers Eastern Bloc KM1810BM86 (USSR) http://www.cpu-collection.de/ x86 - other manufacturers Transmeta, Rise Technology, IDT, National Semiconductor, Cyrix, NexGen, Chips and Technologies, IBM, UMC, DM&P Electronics, ZF Micro, Zet IA-32, RDC Semiconductors, Nvidia, ALi, SiS, GlobalFoundries, TSMC, Fujitsu, SGS-Thomson, Texas Instruments, ... (via Wikipedia) At first, a simple architecture... At first, a simple architecture... x86 bursted with new functions • No eXecute bit (W^X, DEP) o completely redefined exploit development, together with ASLR • Supervisor Mode Execution Prevention • RDRAND instruction o cryptographically secure prng • Related: TPM, VT-d, IOMMU Overall..
    [Show full text]
  • SDG Adhoc Reporting
    VMware Deliverable Release Notes This document does not apply to HPE Superdome servers. For information on HPE Superdome, see the following links: HPE Integrity Superdome X HPE Superdome Flex Information on HPE Synergy supported VMware ESXi OS releases, HPE ESXi Custom Images and HPE Synergy Custom SPPs is available at: VMware OS Support Tool for HPE Synergy Information on HPE Synergy Software Releases is available at: HPE Synergy Software Releases - Overview VMware Upgrade Pack v1.4.2.1 Release Notes for VMware ESXi 7.0 U2 BIOS (Login Required) - System ROM Driver - Lights-Out Management Driver - Network Driver - Storage Controller Driver - System Management Firmware - Network Firmware - NVDIMM Firmware - Storage Controller Firmware - Storage Fibre Channel Software - Management Software - Storage Fibre Channel Software - System Management BIOS (Login Required) - System ROM Top ROM Flash Firmware Package - HPE Apollo 2000 Gen10/HPE ProLiant XL170r/XL190r Gen10 (U38) Servers Version: 2.42_01-23-2021 (Recommended) Filename: U38_2.42_01_23_2021.fwpkg Important Note! Important Notes: None Deliverable Name: HPE Apollo 2000 Gen10/HPE ProLiant XL170r/XL190r Gen10 System ROM - U38 Release Version: 2.42_01-23-2021 Last Recommended or Critical Revision: 2.42_01-23-2021 Previous Revision: 2.40_10-26-2020 Firmware Dependencies: None Enhancements/New Features: Updated the support for Fast Fault Tolerant Memory Mode (ADDDC) to improve system uptime. Added support to the BIOS/Platform Configuration (RBSU) Time Zones to add Dublin/London (UTC+1). This support also requires the latest version of iLO Firmware, version 2.40 or later. Problems Fixed: This revision of the System ROM includes the latest revision of the Intel microcode which provides a fix for a potential machine check exception under heavy stress with short loops of instructions.
    [Show full text]
  • Introduction
    Volume 3, Spring Issue, 1990 NEC v. INTEL : BREAKING NEW GROUND IN THE LAW OF COPYRIGHT Jorge Contreras,* Laura Handley,* and Terrence Yang* INTRODUCTION The status of copyright protection for computer programs has long been in a state of confusion. In NEC Corp. v. Intel Corp., 1 the U.S. Dis- trict Court for the Northern District of California shed some light on three previously unresolved issues in this murky and continually evolv- ing area of copyright. The court ruled that: (1) microcode embedded in certain Intel microprocessors constituted copyrightable material; (2) reverse engineering of the microcode did not infringe the microcode copyright; and (3)independent "clean room" development of similar microcode was persuasive evidence of non-infringement. The execution of a computer program within a computer involves a number of different, operational levels. 2 An applications programmer may write a program to'solve a problem in a high-level.problem-oriented language containing familiar words, variables, and operators. Examples of high-level languages include BASIC, C, FORTRAN, COBOL, and Pascal. However, high-level languages cannot be implemented as such by a computer, which is controlled by the operation of digital circuits. Before instructions can be executed, a program must undergo a series of transformations that enable it-to operate the computer's digital circuitry. The first step in this transformation may involve translation of the pro- gram by a compiler into an assembly-level program. Assembly languages generally reflect the internal organization and operation of the computer more than higher-level languages do, but are still incapable of directly controlling the computer.
    [Show full text]
  • Cacheout: Leaking Data on Intel Cpus Via Cache Evictions
    CacheOut: Leaking Data on Intel CPUs via Cache Evictions Stephan van Schaik* Marina Minkin Andrew Kwong University of Michigan University of Michigan University of Michigan [email protected] [email protected] [email protected] Daniel Genkin Yuval Yarom University of Michigan University of Adelaide and Data61 [email protected] [email protected] Abstract—Recent transient-execution attacks, such as RIDL, instructions, bypassing the CPU’s address and permission Fallout, and ZombieLoad, demonstrated that attackers can leak checks. Using these techniques, an attacker can siphon off data information while it transits through microarchitectural buffers. as it appears in the buffer, bypassing all previous hardware Named Microarchitectural Data Sampling (MDS) by Intel, these attacks are likened to “drinking from the firehose”, as the and software countermeasures and again breaking nearly all attacker has little control over what data is observed and from hardware-backed security domains. what origin. Unable to prevent the buffers from leaking, Intel Responding to the threat of unconstrained data extraction, issued countermeasures via microcode updates that overwrite the Intel deployed countermeasures for blocking data leakage from buffers when the CPU changes security domains. internal CPU buffers. For older hardware, Intel augmented a In this work we present CacheOut, a new microarchitectural attack that is capable of bypassing Intel’s buffer overwrite legacy x86 instruction, verw, to overwrite the contents of countermeasures. We observe that as data is being evicted from the leaking buffers. This countermeasure was subsequently the CPU’s L1 cache, it is often transferred back to the leaky CPU deployed by all major operating system vendors, performing buffers where it can be recovered by the attacker.
    [Show full text]
  • Undocumented X86 Instructions to Control the CPU at the Microarchitecture Level
    UNDOCUMENTED X86 INSTRUCTIONS TO CONTROL THE CPU AT THE MICROARCHITECTURE LEVEL IN MODERN INTEL PROCESSORS Mark Ermolov Dmitry Sklyarov Positive Technologies Positive Technologies [email protected] [email protected] Maxim Goryachy independent researcher [email protected] July 7, 2021 ABSTRACT At the beginning of 2020, we discovered the Red Unlock technique that allows extracting microcode (ucode) and targeting Intel Atom CPUs. Using the technique we were able to research the internal structure of the microcode and then x86 instructions implementation. We found two undocumented x86 instructions which are intendent to control the microarhitecture for debug purposes. In this paper we are going to introduce these instructions and explain the conditions under which they can be used on public-available platforms. We believe, this is a unique opportunity for third-party researchers to better understand the x86 architecture. Disclamer. All information is provided for educational purposes only. Follow these instructions at your own risk. Neither the authors nor their employer are responsible for any direct or consequential damage or loss arising from any person or organization acting or failing to act on the basis of information contained in this paper. Keywords Intel · Microcode · Undocumented · x86 1 Introduction The existence of undocumented mechanisms in the internals of modern CPUs has always been a concern for information security researchers and ordinary users. Assuming that such mechanisms do exist, the main worry is that
    [Show full text]
  • Red Hat Enterprise Linux 7 7.1 Release Notes
    Red Hat Enterprise Linux 7 7.1 Release Notes Release Notes for Red Hat Enterprise Linux 7.1 Last Updated: 2018-05-18 Red Hat Enterprise Linux 7 7.1 Release Notes Release Notes for Red Hat Enterprise Linux 7.1 Red Hat Customer Content Services Legal Notice Copyright © 2015-2017 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Product Support Notice © 2019 Avaya Inc
    Product Support Notice © 2019 Avaya Inc. All Rights Reserved. PSN # PSN027081u Avaya Proprietary – Use pursuant to the terms of your signed agreement or company policy. Original publication date: 10-Apr-19. This is Issue #1, published date: Severity/risk level Medium Urgency When convenient 10-Apr-19. Name of problem PSN027081u – Avaya Common Server R3 (HPE® DL360/380 G9) and R2 (DL360p/380p G8) v7.1 update including L1 Terminal Fault (L1TF) mitigation Products affected Common Server R3 (HPE® DL360/380 G9) Common Server R2 (HPE® DL360p/380p G8) Problem description HPE release notes specific to this update state that the latest revision of the Intel microcode provided in this update will address the following: • In combination with operating system and hypervisor updates, provides mitigation for the L1 Terminal Fault – OS/SMM (CVE-2018-3620) and L1 Terminal Fault – VMM (CVE-2018-3646) security vulnerabilities. • In combination with operating system updates, provides mitigation for the Speculative Store Bypass (also known as Variant 4) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3639 • Provides mitigation for the Rogue Register Read (also known as Variant 3a) security vulnerability. A Medium level CVE has been assigned to this issue with ID CVE-2018-3640. General Information for L1TF: An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization). This latest speculative execution side channel cache timing vulnerability is called L1 Terminal Fault (L1TF). There are three varieties of L1TF that have been identified.
    [Show full text]