DOCSLIB.ORG

Enabling Intel® Virtualization Technology Features and Benefits

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Enabling Intel® Virtualization Technology Features and Benefits WHITE PAPER Intel® Virtualization Technology Enterprise Server Enabling Intel® Virtualization Technology Features and Benefits Maximizing the benefits of virtualization with Intel’s new CPUs and chipsets EXECUTIVE SUMMARY Although virtualization has been accepted in most data centers, some users have not yet taken advantage of all the virtualization features available to them. This white paper describes the features available in Intel® Virtualization Technology (Intel® VT) that work with Intel’s new CPUs and chipsets, showing how they can benefit the end user and how to enable them. Intel® Virtualization Technology Goldberg. Thus, developers found it difficult Feature Brief and Usage Model to implement a virtual machine platform on Intel VT combines with software-based the x86 architecture without significant virtualization solutions to provide maximum overhead on the host machine. system utilization by consolidating multiple environments into a single server or PC. In 2005 and 2006, Intel and AMD, working By abstracting the software away from the independently, each resolved this by creat- underlying hardware, a world of new usage ing new processor extensions to the x86 models opens up that can reduce costs, architecture. Although the actual implemen- increase management efficiency, and tation of processor extensions differs strengthen security—all while making your between AMD and Intel, both achieve the computing infrastructure more resilient in same goal of allowing a virtual machine the event of a disaster. hypervisor to run an unmodified operating system without incurring significant emula- During the last four years, Intel has intro- tion performance penalties. duced several new features to Intel VT. Most of these features are well known, but others Intel VT is Intel’s hardware virtualization for may not be. the x86 architecture that helps consolidate multiple environments into a single server, This paper describes key features of Intel VT, workstation, or PC so that you need fewer how they fit into Intel’s platforms, and how to systems to complete the same tasks. maximize their benefits. The sections that follow explain some of Intel VT CPU-Based Features the key CPU-based features of Intel VT. The x86 processor architecture did not orig- inally meet the Formal Requirements for Intel® VT FlexPriority Virtualizable Third-Generation Architectures, Intel® VT FlexPriority is a processor exten- Marco Righini sion that optimizes virtualization software Intel Corporation a specification for virtualization created in efficiency by improving interrupt handling. [email protected] 1974 by Gerald J. Popek and Robert P. Enabling Intel® Virtualization Technology Features and Benefits To enable Intel VT FlexPriority, you enable With virtual processor IDs (VPID), a VM ID VPID is available on all new Intel Xeon processors Intel VT extensions. Like most hardware tag in the CPU hardware structures (e.g., starting with the 5500, 5600, and 7500 series. features, Intel VT FlexPriority must be TLB) associates cache lines with each VM VGuest Preemption Timer enabled by the hypervisor or virtual actively running on the CPU. This permits The Guest Preemption Timer is a mecha- machine monitor (VMM), which allows mul- the CPU to flush only the cache lines nism that enables a VMM to preempt the tiple operating systems to run concurrently associated with a particular VM when it execution of a guest OS. on a host computer. is flushed from the CPU, avoiding the need to reload cache lines for a VM that Programmable by VMM, the timer causes Intel VT FlexPriority eliminates most VM was not migrated and resulting in lower the VM to exit when the timer expires. It exits due to guest task priority registers overhead. has no impact on interrupt architecture. (TPR) access. This reduces the virtualiza- tion overhead and improves I/O through- put. Table 1 lists which Intel CPUs have Table 1. Intel Processors with Intel® VT FlexPriority Intel VT FlexPriority; Table 2 maps Intel VT features to CPUs. Figure 1 shows the Intel® Enhanced vMotion* Example reduction of EXITs and also looks at the Microarchitecture Compatibility (EVC) Setting I/O throughput measured (best-case 45nm Intel® Core™ Intel® Xeon® processor (45nm) Intel Xeon processor scenario). processor family Intel Core 2 processor 5400 or 7400 series Intel® VT FlexMigration Next-generation Intel® Intel Xeon processor Intel Xeon processor Intel® VT FlexMigration is a feature of Intel microarchitecture Intel Core i7 processor (45nm) 5500 or 7500 series Virtualization Technology that enables you Intel Xeon processor Intel Xeon processor Intel Xeon processor to build one compatible virtualization pool and 5600 series Intel Core i7 processor (32nm ) 5600 series conduct live virtual machine (VM) migration across all Intel® Core™ microarchitecture-based servers. It gives you the power to choose the Table 2. Intel Virtualization Technology Feature and CPU Mapping right server platform to best optimize per- formance, cost, power, and reliability. Intel® Xeon® Processor 7400 7500/ 5500 5600 3300/ 3400 Combined with support from a virtualization Series 6500 Series Series 3100 Series software provider, this feature allows IT to Series Series maximize flexibility by providing the ability VT-x Base to build a single live migration compatibility Intel® VT FlexPriority pool with multiple generations of Intel Xeon Intel® VT FlexMigration processor-based servers. Extended Page For details on Intel VT FlexMigration, visit Tables (EPT) http://communities.intel.com/docs/DOC-4124. Virtual Processor Virtual Processor IDs (VPID) ID (VPID) Traditionally, every time a hypervisor Guest Preemption switched execution between different VMs, Timer the VM and its data structure had to be Descriptor-Table flushed out of the transition look-aside Exiting buffers (TLB) associated with the CPU Pause-Loop Exiting caches, since the hypervisor had no informa- TXT tion on which cache line was associated with any particular VM. Real Mode Support 2 Enabling Intel® Virtualization Technology Features and Benefits This feature helps VMM vendors fulfill flexi- Extended Page Table (EPT) hardware features built into the CPU and bility and quality of service guarantees. It Typical Intel® architecture 32-page tables chipset. This hardware-based security pro- can help when you need to switch tasks or (referenced by control register CR3) trans- vides a foundation on which trusted plat- allocate a certain amount of CPU power to a late from linear addresses to guest-physical form solutions can be built to protect the task. For telecom and networking applica- addresses. With the Extended Page Table platform from software-based attacks. tions, it makes virtualization a useful tool— (EPT) feature, a separate set of page tables and possibly a must-have feature. (EPTs) translate from guest-physical Figure 3 shows how Intel TXT works. addresses to host-physical addresses that Descriptor Table Exiting Features of Intel TXT include: are used to access memory. As a result, the This feature allows a VMM to protect a guest OS can be allowed to modify its own guest OS from internal attack by preventing • Verified Launch. An Intel TXT page tables and directly handle page faults. relocation of key system data structures. hardware-based chain of trust enables launch of MLE into a known, This allows a VMM to avoid the VM exits Pause-Loop Exiting expected state. Changes to MLE associated with page-table virtualization, This feature is a hardware assist to enable can be detected via hash-based which is a major source of virtualization detection of spin locks in guest software measurements. and avoid lock-holder preemption. It helps to overhead without EPT. reduce overhead and improve performance. • Protected Configuration. Intel TXT Figure 2 shows how the EPT works. hardware protects the launched con- Real Mode Support Intel® Trusted Execution Technology figurations from malicious software, This feature allows guests to operate in Intel® Trusted Execution Technology (Intel® maintaining the integrity of the real mode, removing the performance TXT) provides a hardware-based security measured launched environment’s overhead and complexity of an emulator. foundation on which to build and maintain identity. a chain of trust to protect the platform Uses include: • Secret Protection. Intel TXT from software-based attacks. hardware removes residual data • Early VMM load The goal of Intel TXT is to provide an accu- at improper MLE shut-down, protect- • Guest boot and resume rate measurement, at launch, of the meas- ing data from memory snooping ured launch environment (MLE) through the software. Without Intel® VT FlexPriority With Intel VT FlexPriority Figure 1. Reduction of EXITs with Intel® VT FlexPriority 3 Enabling Intel® Virtualization Technology Features and Benefits Intel® VT for Directed I/O (Intel® VT-d) Intel® VT-d is a feature integrated into the This has both pros and cons: In computing, an input/output memory man- chipset and therefore not related to the CPU. agement unit (IOMMU) is a memory manage- Before Intel VT-d and hypervisors supporting it, • Pros: This hides any type of change ment unit (MMU) that connects a digital any VM running on top of a VMM was seeing between the hardware vendors and media adapter (DMA)-capable I/O bus to the emulated, or para-virtualized, devices. Figure 4 makes it possible for VMs to migrate main memory. Like a traditional MMU, which shows how Intel VT-d works. easily. translates CPU-visible virtual addresses to • Cons: Performance takes a hit. This is physical addresses, the IOMMU takes care of No matter what type of hardware was physical- true even if the emulated device is mapping device-visible virtual addresses ly present in the server, the VM itself sees a vir- based on a para-virtualized or synthet- (also called device addresses or I/O address- tualized device. So, for example, on VMware ic driver, either in terms of CPU utiliza- es in this context) to physical addresses. vSphere*, you would typically see a VMXnet* tion, bandwidth, or latency. Some units also provide memory protection network card instead of the real network inter- from misbehaving devices.
Load more

Recommended publications
  • Understanding Full Virtualization, Paravirtualization, and Hardware Assist
    VMware Understanding Full Virtualization, Paravirtualization, and Hardware Assist Contents Introduction .................................................................................................................1 Overview of x86 Virtualization..................................................................................2 CPU Virtualization .......................................................................................................3 The Challenges of x86 Hardware Virtualization ...........................................................................................................3 Technique 1 - Full Virtualization using Binary Translation......................................................................................4 Technique 2 - OS Assisted Virtualization or Paravirtualization.............................................................................5 Technique 3 - Hardware Assisted Virtualization ..........................................................................................................6 Memory Virtualization................................................................................................6 Device and I/O Virtualization.....................................................................................7 Summarizing the Current State of x86 Virtualization Techniques......................8 Full Virtualization with Binary Translation is the Most Established Technology Today..........................8 Hardware Assist is the Future of Virtualization, but the Real Gains Have
    [Show full text]
  • PCI DSS Virtualization Guidelines
    Standard: PCI Data Security Standard (PCI DSS) Version: 2.0 Date: June 2011 Author: Virtualization Special Interest Group PCI Security Standards Council Information Supplement: PCI DSS Virtualization Guidelines Information Supplement • PCI DSS Virtualization Guidelines • June 2011 Table of Contents 1 Introduction ....................................................................................................................... 3 1.1 Audience ................................................................................................................ 3 1.2 Intended Use .......................................................................................................... 4 2 Virtualization Overview .................................................................................................... 5 2.1 Virtualization Concepts and Classes ..................................................................... 5 2.2 Virtual System Components and Scoping Guidance ............................................. 7 3 Risks for Virtualized Environments .............................................................................. 10 3.1 Vulnerabilities in the Physical Environment Apply in a Virtual Environment ....... 10 3.2 Hypervisor Creates New Attack Surface ............................................................. 10 3.3 Increased Complexity of Virtualized Systems and Networks .............................. 11 3.4 More Than One Function per Physical System ................................................... 11 3.5 Mixing VMs of
    [Show full text]
  • Virtualization and Shared Infrastructure Data Storage for IT in Kosovo Institutions Gani Zogaj
    Rochester Institute of Technology RIT Scholar Works Theses Thesis/Dissertation Collections 2012 Virtualization and shared Infrastructure data storage for IT in Kosovo institutions Gani Zogaj Follow this and additional works at: http://scholarworks.rit.edu/theses Recommended Citation Zogaj, Gani, "Virtualization and shared Infrastructure data storage for IT in Kosovo institutions" (2012). Thesis. Rochester Institute of Technology. Accessed from This Master's Project is brought to you for free and open access by the Thesis/Dissertation Collections at RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. AMERICAN UNIVERSITY IN KOSOVO MASTER OF SCIENCE IN PROFESSIONAL STUDIES Virtualization and Shared Infrastructure Data Storage for IT in Kosovo institutions “Submitted as a Capstone Project Report in partial fulfillment of a Master of Science degree in Professional Studies at American University in Kosovo” By Gani ZOGAJ November, 2012 Virtualization and Shared Infrastructure Data Storage for IT in Kosovo institutions ACKNOWLEDGEMENTS First, I would like to thank God for giving me health for completing my Master’s Degree studies. I would like to express my gratitude to my supervisor of capstone proposal, Bryan, for his support and for giving me suggestions and recommendations throughout the Capstone Project work. Finally, I would like to thank my wife, Shkendije, and my lovely daughters, Elisa and Erona, who I love so much, for their understanding while I was preparing the Capstone Project and I couldn’t spend enough time with them. 2 Virtualization and Shared Infrastructure Data Storage for IT in Kosovo institutions Table of Contents Figures and Tables………………………………………………….……………….……….……5 List of Acronyms………………………………………………………………....………….……6 Executive Summary……………………………………………………..………………...………8 Chapter 1…………………………………………………………………………...…………….11 1.
    [Show full text]
  • Oracle® Linux Virtualization Manager Getting Started Guide
    Oracle® Linux Virtualization Manager Getting Started Guide F25124-11 September 2021 Oracle Legal Notices Copyright © 2019, 2021 Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Firecracker: Lightweight Virtualization for Serverless Applications
    Firecracker: Lightweight Virtualization for Serverless Applications Alexandru Agache, Marc Brooker, Andreea Florescu, Alexandra Iordache, Anthony Liguori, Rolf Neugebauer, Phil Piwonka, and Diana-Maria Popa, Amazon Web Services https://www.usenix.org/conference/nsdi20/presentation/agache This paper is included in the Proceedings of the 17th USENIX Symposium on Networked Systems Design and Implementation (NSDI ’20) February 25–27, 2020 • Santa Clara, CA, USA 978-1-939133-13-7 Open access to the Proceedings of the 17th USENIX Symposium on Networked Systems Design and Implementation (NSDI ’20) is sponsored by Firecracker: Lightweight Virtualization for Serverless Applications Alexandru Agache Marc Brooker Andreea Florescu Amazon Web Services Amazon Web Services Amazon Web Services Alexandra Iordache Anthony Liguori Rolf Neugebauer Amazon Web Services Amazon Web Services Amazon Web Services Phil Piwonka Diana-Maria Popa Amazon Web Services Amazon Web Services Abstract vantage over traditional server provisioning processes: mul- titenancy allows servers to be shared across a large num- Serverless containers and functions are widely used for de- ber of workloads, and the ability to provision new func- ploying and managing software in the cloud. Their popularity tions and containers in milliseconds allows capacity to be is due to reduced cost of operations, improved utilization of switched between workloads quickly as demand changes. hardware, and faster scaling than traditional deployment meth- Serverless is also attracting the attention of the research com- ods. The economics and scale of serverless applications de- munity [21,26,27,44,47], including work on scaling out video mand that workloads from multiple customers run on the same encoding [13], linear algebra [20, 53] and parallel compila- hardware with minimal overhead, while preserving strong se- tion [12].
    [Show full text]
  • Reference Architecture: Lenovo Client Virtualization (LCV) with Thinksystem Servers
    Reference Architecture: Lenovo Client Virtualization (LCV) with ThinkSystem Servers Last update: 10 June 2019 Version 1.3 Base Reference Architecture Describes Lenovo clients, document for all LCV servers, storage, and networking solutions hardware used in LCV solutions LCV covers both virtual Contains system performance desktops and hosted considerations and performance desktops testing methodology and tools Mike Perks Pawan Sharma Table of Contents 1 Introduction ............................................................................................... 1 2 Business problem and business value ................................................... 2 3 Requirements ............................................................................................ 3 4 Architectural overview ............................................................................. 6 5 Component model .................................................................................... 7 5.1 Management services ............................................................................................ 10 5.2 Support services .................................................................................................... 11 5.2.1 Lenovo Thin Client Manager ...................................................................................................... 11 5.2.2 Chromebook management console ........................................................................................... 12 5.3 Storage .................................................................................................................
    [Show full text]
  • Paravirtualization (PV)
    Full and Para Virtualization Dr. Sanjay P. Ahuja, Ph.D. Fidelity National Financial Distinguished Professor of CIS School of Computing, UNF x86 Hardware Virtualization The x86 architecture offers four levels of privilege known as Ring 0, 1, 2 and 3 to operating systems and applications to manage access to the computer hardware. While user level applications typically run in Ring 3, the operating system needs to have direct access to the memory and hardware and must execute its privileged instructions in Ring 0. x86 privilege level architecture without virtualization Technique 1: Full Virtualization using Binary Translation This approach relies on binary translation to trap (into the VMM) and to virtualize certain sensitive and non-virtualizable instructions with new sequences of instructions that have the intended effect on the virtual hardware. Meanwhile, user level code is directly executed on the processor for high performance virtualization. Binary translation approach to x86 virtualization Full Virtualization using Binary Translation This combination of binary translation and direct execution provides Full Virtualization as the guest OS is completely decoupled from the underlying hardware by the virtualization layer. The guest OS is not aware it is being virtualized and requires no modification. The hypervisor translates all operating system instructions at run-time on the fly and caches the results for future use, while user level instructions run unmodified at native speed. VMware’s virtualization products such as VMWare ESXi and Microsoft Virtual Server are examples of full virtualization. Full Virtualization using Binary Translation The performance of full virtualization may not be ideal because it involves binary translation at run-time which is time consuming and can incur a large performance overhead.
    [Show full text]
  • Red Hat Virtualization 4.3 Planning and Prerequisites Guide
    Red Hat Virtualization 4.3 Planning and Prerequisites Guide Planning for the Installation and Configuration of Red Hat Virtualization 4.3 Last Updated: 2019-05-09 Red Hat Virtualization 4.3 Planning and Prerequisites Guide Planning for the Installation and Configuration of Red Hat Virtualization 4.3 Red Hat Virtualization Documentation Team Red Hat Customer Content Services [email protected] Legal Notice Copyright © 2019 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. 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.
    [Show full text]
  • IT Modernization with Nutanix – a Cloud-Smart Approach
    SOLUTION BRIEF IT Modernization with Nutanix - A Cloud- Smart Approach Nutanix simplifies legacy IT infrastructure while simultaneously enabling IT-as-a-Service by providing the secure and intelligent automation capabilities cloud-based datacenter architectures require THE BUSINESS VALUE Federal agencies are increasingly being asked to spend less time on infrastructure OF NUTANIX and allocate more time and budget to application services that add business value. Despite a continuous stream of IT hardware and software enhancements, • 60% lower cost of operations the infrastructure challenges and costs faced by agencies continue to rise. • 39% lower IT infrastructure costs Traditional IT infrastructure and virtualization software required to meet agency needs are complex and expensive, and datacenter management has become • 534% 5-year ROI painful. Far too much time, effort, and budget are focused on just keeping the • 61% more IT staff efficiencies lights on and the ability to support an agile continuous development environment with no downtime is not possible today. • 7 month payback Today, IT is distributed. There’s no longer just one cloud. Business applications run • 97% fewer outages in private, public, and distributed clouds. But with many clouds, come many • 73% less staff time to deploy silos–different management tools, infrastructure technologies, and consumption compute resources models – all of which make IT more complex. • 68% less staff time to deploy Legacy infrastructure—with separate silos of proprietary hardware-based servers, storage resources storage, storage networks, and virtualization—is not well suited to meet the growing demand or agility needed to service cloud or numerous enterprise workloads including virtualized, bare metal, container-based, DevSecOps automation use cases, or hybrid cloud architectures.
    [Show full text]
  • Malware Collection and Analysis Via Hardware Virtualization Tamas K
    University of Connecticut OpenCommons@UConn Doctoral Dissertations University of Connecticut Graduate School 12-1-2015 Malware Collection and Analysis via Hardware Virtualization Tamas K. Lengyel [email protected] Follow this and additional works at: https://opencommons.uconn.edu/dissertations Recommended Citation Lengyel, Tamas K., "Malware Collection and Analysis via Hardware Virtualization" (2015). Doctoral Dissertations. 964. https://opencommons.uconn.edu/dissertations/964 Malware Collection and Analysis via Hardware Virtualization Tamas Kristof Lengyel University of Connecticut 2015 Abstract Malware is one of the biggest security threat today and deploying effective defen- sive solutions requires the collection and rapid analysis of a continuously increasing number of samples. The collection and analysis is greatly complicated by the pro- liferation of metamorphic malware as the efficacy of signature-based static analysis systems is greatly reduced. While honeypots and dynamic malware analysis has been effectively deployed to combat the problem, significant challenges remain. The rapidly increasing number of malware samples poses a particular challenge as it greatly inflates the cost of the hardware required to process the influx. As modern malware also deploys anti-debugging and obfuscation techniques, the time it takes to formulate effective solutions is further exacerbated. There is a clear need for effective scalability in automated malware collection and analysis. At the same time, modern malware can both detect the monitoring environment and hide in unmonitored corners of the system. It has also been observed that mal- ware modifies its run-time behavior to lead the analysis system astray when it detects a monitoring environment. Consequently, it is critical to create a stealthy environment to hide the presence of the data collection from the external attacker.
    [Show full text]
  • BEST PRACTICES for DATA CENTRE VIRTUALIZATION (ITSP.70.010) March 2020
    UNCLASSIFIED CYBER CENTRE DATA CENTRE VIRTUALIZATION REPORT: BEST PRACTICES FOR DATA CENTRE VIRTUALIZATION (ITSP.70.010) March 2020 PRACTITIONER TLP:WHITE 1 ITSP.70.010 UNCLASSIFIED FOREWORD ITSP.70.010 Cyber Centre Data Centre Virtualization Report: Best Practices for Data Centre Virtualization is an UNCLASSIFIED publication, issued under the authority of the Head, Canadian Centre for Cyber Security (Cyber Centre). For more information, email or phone our Contact Centre: Cyber Centre Contact Centre [email protected] 613-949-7048 or 1-833-CYBER-88 EFFECTIVE DATE This publication takes effect on (03/27/2020). REVISION HISTORY Revision Amendments Date 1 First release. March 27, 2020 2 ITSP.70.010 UNCLASSIFIED OVERVIEW To improve efficiency and streamline operations, many organizations are virtualizing their data centres. However, some are doing so without a proper understanding of the security implications of their decisions on the overall security posture of the data centre. By increasing their consolidation ratios (i.e. the number of virtual machines that can operate on each physical host machine), many organizations may unintentionally compromise their network security architecture. Moreover, any attempt to replace many of the physical isolation mechanisms with logical equivalents may introduce unacceptable risk into their network architecture. Not only are virtualized data centres (VDCs) susceptible to most of the vulnerabilities inherent in traditional data centres, but they introduce new vulnerabilities specific to this environment. While complex virtualization threats (e.g. System Management Mode (SMM) rootkits, side-channel attacks, and hyperjacking) must be addressed, it is the more practical threats that are of greater risk to the VDC.
    [Show full text]
  • Stmicroelectronics Introduces Stellar Case Study
    STMicroelectronics Introduces Stellar Case Study The first automotive MCU with real-time virtualization for powertrain, smart gateway and domain controllers Goal Car manufacturers are defining new architectures that integrate multiple vehicle functions into centralized systems called domain or zone controllers. STMicroelectronics Stellar family enables users to create safe, secure and deterministic solutions for these new architectures to address vehicle electrification and vehicle systems where powertrain, braking and vehicle dynamics functions are integrated. Challenge The powertrain is traditionally a very complex automotive application that sets demanding latency constraints to meet strict real-time responses and requires advanced timer functionalities, accurate analog capabilities and high-level safety guarantees. These challenges have been recently further emphasized by the integration of electrification features such as charging, battery management, inverter traction control, and the evolution of vehicle architectures into domain and zone-oriented architectures. For next-generation architectures, automotive microcontrollers must be able to provide more capabilities than ever before. Alongside offering all the features for traditional powertrain applications they must also have a high level of connectivity, increased routing capabilities, and features to guarantee software separation. This compartmentalization of software must enable the safe integration of multiple virtual ECUs in the same physical box. In fact, this increasing software complexity and integration can only be managed with a better utilization of hardware resources, simplified maintenance of the different modules and separate containers for the multiple virtual ECUs. These virtual ECUs can coexist in the same physical MCU only if freedom from interference (FFI) and secure compartmentalization of software functions is guaranteed while supporting concurrent multiple ASIL safety levels.
    [Show full text]