Hardware and Software Support for Virtualization

Bugnion, Edouard; Nieh, Jason; Tsafrir, Dan

doi:10.2200/s00754ed1v01y201701cac038

Cited by 26 publications

(23 citation statements)

References 75 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Гипервизор предоставляет гостю набор виртуальных устройств, затем он перехватывает обращения гостя к устройствам ввода-вывода и эмулирует их, используя в том числе и реальные устройства. Такой принцип виртуализации ввода-вывода характеризуется как интерпозиция [1].…”

Section: интерпозиция ввода-выводаunclassified

Input/output virtualization of Elbrus microprocessors

Rybakov

Polyakov²

2020

Radiopromyshlennost

View full text Add to dashboard Cite

The article describes and compares the methods of input-output (I/O) virtualization, adapted for the Elbrus architecture. The presented methods of software emulation and paravirtualization of devices do not require hardware support and provide complete isolation of real devices from virtual ones at the hypervisor level, which allows for better consolidation of physical I/O. Direct assignment of the device to the guest provides better performance over the other methods, but requires hardware modifications in the I/O Memory Management Unit (IOMMU). Hardware support for I/O virtualization was implemented in the new generation of Elbrus microprocessors. The research results can help the users of the Elbrus platform virtualization to setup a detailed configuration of the virtual machine I/O to optimize each guest system for specific tasks.

show abstract

Section: интерпозиция ввода-выводаunclassified

Input/output virtualization of Elbrus microprocessors

Rybakov

Polyakov²

2020

Radiopromyshlennost

View full text Add to dashboard Cite

show abstract

“…Threat due to DMA-capable hardware devices (HY-DV5): The security threat from a DMA-capable device is that, since the VM controls the device, it can program the device to perform DMA operations directed at any physical (host) memory location, including the areas belonging to other VMs or the hypervisor [6]. Thus, the direct device assignment has the potential to subvert the isolation between VMs (rather making the MMU enforced isolation function (part of HY-BF1) meaningless).…”

Section: Potential Threat To Hy-bf2mentioning

confidence: 99%

Security recommendations for server-based hypervisor platforms

Chandramouli¹

2018

View full text Add to dashboard Cite

i Authority This publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130.Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose.There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.Comments on this publication may be submitted to: All comments are subject to release under the Freedom of Information Act (FOIA).NIST SP 800-125A REV. 1 SECURITY RECOMMENDATIONS FOR SERVER-BASED HYPERVISOR PLATFORMS ii Reports on Computer Systems TechnologyThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development ...

show abstract

“…Hypervisor allocates the sufficient processing units and memories to each virtual machine [2]. Essentially, virtualization environments come in two forms: hosted virtualization form (Figure 2.a) and bare-metal also called native virtualization ( Figure 2.b) [11]. In Bare-metal hypervisor, there is no need to install a server operating system first, so the hypervisor has direct access to hardware resources [10].…”

Section: Figure 1b Multiple Operating Systems Share Hardware Resourcesmentioning

confidence: 99%

“…Unlike native hypervisor, the hosted hypervisor is like applications that install on a guest operating system. The hosted hypervisor manages the virtual machines, communicates and interacts with operating system of the host machine to access its resources [11]. Parallel Desktop, Microsoft Virtual PC and VMware Workstation pro are the most common hosted hypervisors.…”

Section: Figure 1b Multiple Operating Systems Share Hardware Resourcesmentioning

confidence: 99%

Virtualization Environment for Computer Labs to Maintain Security, Stability and Availability

Alameen¹

2017

IJCA

View full text Add to dashboard Cite

Academic organizations are supposed to seek certain balance between the concerns of security, stability and availability of shared computer labs to achieve the course learning objectives. Some academic activities in computer science courses require students to control and configure some laboratory devices. Students in advanced courses may use some risky applications for some learning activities. It may affect the stability, availability and security of the working nature in the shared lab and networks. Virtualization Platform has the ability to overcome these concerns to achieve learning objectives. Virtualization technologies allow students to access and control the computer settings as well as the working environment in advanced applications without affecting the operational availability of computer labs throughout the college day. Virtualization enables computer security teachers to train their students on many hands-on activities without exposing or causing damages to computer labs. This paper presents the usage of virtualization technology in such environment, the opportunities and benefits of using this technology in computer security oriented courses. The paper also discusses the use of the VMware workstation pro as a sandbox for risky lab activities in computer security courses. Here the Desktop Virtualization offers great opportunities to teach advanced skills in computer security courses. Also, this paper outlines the challenges and limitations of virtualization along with some recommendations to address these limitations.

show abstract

Hardware and Software Support for Virtualization

Cited by 26 publications

References 75 publications

Input/output virtualization of Elbrus microprocessors

Input/output virtualization of Elbrus microprocessors

Security recommendations for server-based hypervisor platforms

Virtualization Environment for Computer Labs to Maintain Security, Stability and Availability

Contact Info

Product

Resources

About