WO2007133741A1 - Launching hypervisor under running operating system - Google Patents
Launching hypervisor under running operating system Download PDFInfo
- Publication number
- WO2007133741A1 WO2007133741A1 PCT/US2007/011545 US2007011545W WO2007133741A1 WO 2007133741 A1 WO2007133741 A1 WO 2007133741A1 US 2007011545 W US2007011545 W US 2007011545W WO 2007133741 A1 WO2007133741 A1 WO 2007133741A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- operating system
- hypervisor
- act
- computer
- virtual machine
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45545—Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0253—Garbage collection, i.e. reclamation of unreferenced memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
Definitions
- One of the primary functions of an operating system is to interface with physical resources on a computing system.
- a typical operating system might guard against accessing the physical resources in an inappropriate manner. For example, when one application is using a particular segment of memory, the operating system may protect that segment of memory from being altered by another application managed by that same operating system. Otherwise, the applications might not function as expected. Such access guards are often based on the assumption that the operating system is the only operating system running on the computing system.
- a hypervisor is a software layer that is configured to be interposed between one or more running operating systems and protected physical resources (such as processors, I/O ports, memory, interrupts, etc.).
- the hypervisor functionally multiplexes the protected physical resources for the operating systems, and manifests the resources to each operating system in a virtualized manner. For instance, as a simple example, suppose that there are two operating systems running on a computing system that has one processor and 1 Gigabyte (GB) of Random Access Memory (RAM).
- the hypervisor may allocate half of the processor cycles to each operating system, and half of the memory (512 Megabytes (MB) of RAM) to each operating system.
- the hypervisor may provide a virtualized range of RAM addressed to each operating system such that it appears to both operating systems that there is only 512 MB of RAM available.
- the hypervisor When the operating system attempts to communicate with a physical resource and vice versa, the hypervisor performs appropriate buffering and transformations to allow each operating system, to experience its environment as though it was the only operating system running on the computing system. Furthermore, the hypervisor does this is a manner that the physical resources on the computing system may be shared by multiple operating system instances while still being protected.
- hypervisors are launched prior to running an operating system. This allows the hypervisor to start the operating system in a virtual machine by presenting a virtualized view of the physical resources.
- the hypervisor includes extensive code for discovering the physical resources and their essential characteristics. Since physical resource discovery is done before there are any running operating systems, the operating system cannot be relied upon in this discovery process. Accordingly, the code for discovering physical resources in a hypervisor may be quite complex.
- some embodiments described herein relate to the launching of a hypervisor after there is already a running operating system.
- the running operating system may be used instead of the hypervisor to discover the physical resources running on the computing system.
- the hypervisor may rely on the operating system to discover the resources, rather than having to have code that performs the same functionality.
- Figure 1 illustrates a computing environment in which embodiments of the present invention may be employed
- Figure 2 illustrates a flowchart of a method for launching a hypervisor using a running operating system
- Figure 3 illustrates a flowchart of a method for launching additional operating system instances
- Figure 4A illustrates a configuration in which a root operating system, in the absence of a hypervisor, is in direct communication with physical resources of the computing system;
- Figure 4B illustrates a configuration in which the operating system has launched a hypervisor to act as an intermediary between the operating system and the physical resources;
- Figure 4C illustrates a configuration in which additional operating systems have been launched and supported by the hypervisor.
- Figure 5 illustrates a flowchart of a method for transporting the operating system to the environment of the hypervisor.
- a hypervisor may be launched after there is already a running operating system.
- the running operating system may be used instead of the hypervisor to discover the physical resources running on the computing system.
- Other operating system instances may be launched after the hypervisor is operational.
- Computing systems are now increasingly taking a wide variety of forms.
- Computing systems may, for example, be handheld devices, appliances, laptop computers, desktop computers, mainframes, distributed computing systems, or even devices that have not conventionally considered a computing system.
- the term "computing system” is defined broadly as including any device or system (or combination thereof) that includes at least one processor, and a memory capable of having thereon computer-executable instructions that may be executed by the processor.
- the memory may take any form and may depend on the nature and form of the computing system.
- a computing system may be distributed over a network environment and may include multiple constituent computing systems.
- a computing system 100 typically includes at least one processing unit 102 and memory 104.
- the memory 104 may be physical system memory, which may be volatile, non-volatile, or some combination of the two.
- An example of volatile memory includes Random Access Memory (RAM).
- Examples of non- volatile memory include Read Only Memory (ROM), flash memory, or the like.
- RAM Random Access Memory
- Examples of non- volatile memory include Read Only Memory (ROM), flash memory, or the like.
- ROM Read Only Memory
- flash memory or the like.
- the term "memory” may also be used herein to refer to non-volatile mass storage such as physical storage media. Such storage may be removable or non-removable, and may include (but is not limited to) PCMCIA cards, magnetic and optical disks, magnetic tape, and the like.
- module can refer to software objects or routines that execute on the computing system.
- the different components, modules, engines, and services described herein may be implemented as objects or processes that execute on the computing system (e.g., as separate threads). While the system and methods described herein may be implemented in software, implementations in hardware, and in combinations of software and hardware are also possible and contemplated.
- FIG. 1 In the description that follows, embodiments of the invention are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors of the associated computing system that performs the act direct the operation of the computing system in response to having executed computer-executable instructions. An example of such an operation involves the manipulation of data.
- the computer-executable instructions (and the manipulated data) may be stored in the memory 104 of the computing system 100.
- Computing system 100 may also contain communication channels 108 that allow the computing system 100 to communicate with other computing systems over, for example, network 110. Communication channels 108 are examples of communications media.
- Communications media typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information-delivery media.
- communications media include wired media, such as wired networks and direct- wired connections, and wireless media such as acoustic, radio, infrared, and other wireless media.
- the term computer-readable media as used herein includes both storage media and communications media.
- Embodiments within the scope of the present invention also include computer- readable media for carrying or having computer-executable instructions or data structures stored thereon.
- Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer.
- Such computer-readable media can comprise physical storage and/or memory media such as RAM, ROM, EEPROM 5 CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
- Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
- FIG. 2 illustrates a flowchart of a method 200 for a running operating system to launch a hypervisor.
- a "hypervisor" is a software layer that is configured to be disposed between one or more running operating systems and protected physical resources.
- the hypervisor functionally multiplexes the protected physical resources for the operating systems, and manifests the resources to each operating system in a virtualized manner.
- the hypervisor acts as a special kind of abstraction layer between the operating system and the physical resources of the computing system.
- GB Gigabyte
- RAM Random Access Memory
- the hypervisor may allocate half of the processor cycles to each operating system, and half of the memory (512 Megabytes (MB) of RAM) to each operating system. Furthermore, the hypervisor may provide a virtualized range of RAM addressed to each operating system such that it appears to both operating systems that there is only 512 MB of RAM available. When the operating system attempts to communicate with a physical resource and vice versa, the hypervisor performs appropriate buffering and transformations to allow each operating system to experience its environment as though it was the only operating system running on the computing system. [026] Unlike conventional hypervisor configurations, embodiments of the present invention permit the hypervisor to be launched after the operating system has been launched, even if the operating system has already discovered the physical resources of the computing system. The operating system that starts the hypervisor passes information representing the state of the discovered physical resources to the hypervisor. Thus, the hypervisor need not have separate code to discover the physical resources of the computing system.
- the operating system may pause execution and pass control to the hypervisor.
- the hypervisor could then set up a virtual machine instance to handle future access requests to any protected resources of the computing system's physical resources.
- the virtual machine instance is initialized with state that is consistent with the operating system's concept of the protected physical resources.
- the operating system resumes in the virtual machine environment.
- the operating system interfaces with the physical resources indirectly through the hypervisor, rather than directly with the physical resources. The change is transparent to the operating system since the virtual machine that is dedicated to communication with the operating system honors the information the operating system had previously discovered about the physical resources.
- the operating system may not be possible for the operating system to discover a protected physical resource without the use of the hypervisor, and then interface later indirectly with that same protected physical resource through the hypervisor in a transparent manner.
- the operating system may be configured to understand that it might later be operating through a hypervisor, and to thus ignore any of the physical resources that cannot later be virtualized in a transparent manner.
- the operating system loader may be configured to inform other operating system components not to use particular protected physical v resources.
- the method 200 begins when the root operating system is launched (act 201).
- a "root” operating system is the operating system that launches the hypervisor, as contrasted with operating systems that may be launched after the hypervisor is operational.
- Figure 4A illustrates a configuration 400A at this stage of operation in which the operating system 401 communicates directly 404 with the physical resources 402 of the computing system in the absence of a hypervisor.
- the root operating system then performs several acts that are illustrated in the left column of Figure 2 under the column header "ROOT OPERATING SYSTEM". For instance, the root operating system discovers at least one physical resource (act 211A). Operating systems typically have instructions that discover the physical resources of the computing system that are executed soon after launching the operating system.
- the operating system 401 discovers physical resource state 403. Discovering physical resources of a computing system can be a complex task. [031] In order to resume the operating system in the state before the launch of the hypervisor, the operating system captures the state of the physical machine prior to the launching the hypervisor. In one embodiment, the captured state includes the state of all the physical processors and the physical APICs. The physical processor state includes:
- Ds Debug registers
- RIP Instruction Pointer
- RSP Stack Pointer
- RFLAGS Flags Register
- Segment state for CS, DS, SS, ES, FS, GS and TR segments including the segment bases, limits and access rights.
- GDTR Global Descriptor Table Register
- IDTR Interrupt Descriptor Table Register
- LDTR Local Descriptor Table Register
- the physical Local APIC state may includes:
- ISR In-Service-Register
- TPR Task Priority Register
- Physical nodes including those that have no associated resources at boot time but may be populated at runtime
- the operating system also launches the hypervisor (act 211B) that is to be interposed between the operating system and the physical resources.
- the hypervisor 405 is interposed between the root operating system 401 and the physical resources 402.
- the operating system provides state information for at least the physical resources to be protected to the hypervisor (act 212).
- This state information includes all the information that a hypervisor would need to discover the relevant state of the protected physical resources that are to be guarded by the hypervisor.
- the state information might include the capture state described above. At the very least, the state information includes at least an identification of the corresponding physical resources.
- the operating system passes control to the hypervisor.
- the hypervisor then performs acts as illustrated in the right column of Figure 2 under the heading "HYPERVISOR".
- the hypervisor then performs tasks necessary to virtualize the protected physical resources of the computing system to the root operating system (act 221).
- the hypervisor may create a virtual machine instance for the root operating system (act 231).
- block 421 represents a virtual machine instance for the operating system 401.
- the virtual machine instance 421 will serve as a proxy for the physical resources 402 for the operating system 401.
- the virtual machine instance 421 will receive service requests from the operating system 401 for the physical resources, and will perform appropriate transformations and buffering of the requests depending on the state information accessible to the virtual machine instance 421.
- the virtual machine instance 421 will then cause the hypervisor 405 to request the appropriate service from the physical resources 402.
- the virtual machine instance 421 will potentially also report back the results of the request to the operating system 401 with appropriate transformations and buffering as needed.
- the virtual machine instance 421 will behave differently depending on the state information accessible to the virtual machine instance.
- the hypervisor honors the state information that the operating system 401 has already discovered regarding the physical resources 402.
- the hypervisor 405 initializes the virtual machine instance 421 with at least some of the state information provided by the operating system (act 232).
- the hypervisor 405 may initialize the virtual machine with the capture state provided by the operating system.
- the virtual machine instance 421 is initialized with state consistent with the information representing the physical resources detected by the operating system.
- the operating system is then resumed in the virtual machine environment (act 233 and act 214).
- the physical resources 402 are virtualized for the operating system 401 through the use of the virtual machine instance 421 and the hypervisor 405. Since the state information used by the virtual machine 421 is consistent with the state information discovered by the operating system 401, the change is transparent to the operating system 401 is some embodiments.
- the virtualization is provided via a virtual processor abstraction which emulates the behavior of the physical processor. Similarly it provides a virtual APIC which emulates the behavior of the physical APIC. This is achieved as follows:
- the state of the virtual processor is initialized to the captured state of the physical processor.
- the state of the virtual APIC is initialized to the captured state of the physical Local APIC.
- the hypervisor installs intercepts to prevent the operating system from accessing privileged physical hardware resources. For example, the guest physical address ' where the local APIC was previously located prior to launching the hypervisor is marked as not present so that all accesses to the local APIC are trapped into the hypervisor.
- the hypervisor may launch additional operating systems, either instances of the same operating system, or instances of different operating systems. For example, referring to Figure 4C, operating systems 412 and 413 amongst potentially others as represented by the ellipses 414 may additionally be launched.
- Figure 3 illustrates a flowchart of a method 300 for virtualizing physical resources to the additional operating systems as well.
- the hypervisor first launches a corresponding virtual machine instance (act 301), through which the operating system is then launched (act 302).
- the hypervisor uses the corresponding virtual machine instance to virtualize the physical resource(s) to the corresponding additional operating system (act 303).
- the operating system that launches the hypervisor may be in a different environment type. For instance, perhaps the operating system is operating in 32- bit mode, whereas the hypervisor to be launched is to operate in 64-bit mode, or vice versa. Similarly, the operating system and the hypervisor may be operating in different paging modes. Some embodiments of the present invention allow the operating system to launch the hypervisor even if the operating system and hypervisor are operating in different environments.
- Figure 5 illustrates a flowchart of a method 500 for the operating system to enter the environment of the hypervisor in preparation for launching the hypervisor. From act 201 of Figure 5 in which the operating system is launched, the operating system first renders inactionable any non-maskable interrupts (act 501), and masks any maskable interrupts. Non-maskable interrupts may be rendered inactionable in a number of different ways. After all, when the operating system is in transition to the hypervisor operating environment, care should be taken to ensure that no interrupts or exceptions occur before the initial state of the hypervisor is loaded.
- NMIs Non-maskable interrupts
- the temporary page tables can map the temporary EDT, the NMI handler and stack at their original virtual addresses and their respective physical addresses. This ensures that if an NMI arrives when the processor is running with the temporary page tables it will be correctly delivered to the handler.
- a temporary virtual machine instance is created (act 502).
- the operating system then initializes the temporary virtual machine instance with an instruction that causes an intercept (act 503).
- An intercept is a transfer of control from the operating system to the hypervisor.
- the virtual machine instance executes the instructions that causes the intercept, and the intercept is thus generated (act 505).
- the temporary virtual machine instance starts executing using the hypervisor state (act 506), thereby causing the operating system to continue operation in hypervisor mode (act 507).
- the operating system may then launch the hypervisor.
- the temporary virtual machine instance may be destroyed (act 508), since it was only needed to put the operating system into the hypervisor mode necessary to launch the hypervisor.
- embodiments of the present invention permit a hypervisor to be launched even after there is already a running operating system present on the computing system.
- the operating system may launch the hypervisor even if the operating system and hypervisor are in different environments.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
- Hardware Redundancy (AREA)
Abstract
Description
Claims
Priority Applications (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP07777032.9A EP2024826B1 (en) | 2006-05-15 | 2007-05-14 | Launching hypervisor under running operating system |
ES07777032T ES2744379T3 (en) | 2006-05-15 | 2007-05-14 | Launch of the hypervisor under the running operating system |
CN2007800177917A CN101449240B (en) | 2006-05-15 | 2007-05-14 | Launching hypervisor under running operating system |
MX2008014548A MX2008014548A (en) | 2006-05-15 | 2007-05-14 | Launching hypervisor under running operating system. |
JP2009511012A JP2009537897A (en) | 2006-05-15 | 2007-05-14 | Booting the hypervisor under a running operating system |
CA002648874A CA2648874A1 (en) | 2006-05-15 | 2007-05-14 | Launching hypervisor under running operating system |
BRPI0711369A BRPI0711369A8 (en) | 2006-05-15 | 2007-05-14 | LAUNCHING HYPERVISOR UNDER RUNNING OPERATING SYSTEM |
AU2007249730A AU2007249730A1 (en) | 2006-05-15 | 2007-05-14 | Launching hypervisor under running operating system |
NO20084432A NO20084432L (en) | 2006-05-15 | 2008-10-21 | Launch of hypervisor under running operating system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/383,455 US8176485B2 (en) | 2006-05-15 | 2006-05-15 | Launching hypervisor under running operating system |
US11/383,455 | 2006-05-15 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007133741A1 true WO2007133741A1 (en) | 2007-11-22 |
Family
ID=38686563
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2007/011545 WO2007133741A1 (en) | 2006-05-15 | 2007-05-14 | Launching hypervisor under running operating system |
Country Status (14)
Country | Link |
---|---|
US (1) | US8176485B2 (en) |
EP (1) | EP2024826B1 (en) |
JP (1) | JP2009537897A (en) |
KR (1) | KR20090009866A (en) |
CN (1) | CN101449240B (en) |
AU (1) | AU2007249730A1 (en) |
BR (1) | BRPI0711369A8 (en) |
CA (1) | CA2648874A1 (en) |
ES (1) | ES2744379T3 (en) |
MX (1) | MX2008014548A (en) |
NO (1) | NO20084432L (en) |
RU (1) | RU2446447C2 (en) |
TW (1) | TW200813833A (en) |
WO (1) | WO2007133741A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011526390A (en) * | 2008-06-27 | 2011-10-06 | マイクロソフト コーポレーション | Lazy processing of interrupt message end in virtual environment |
Families Citing this family (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8898355B2 (en) * | 2007-03-29 | 2014-11-25 | Lenovo (Singapore) Pte. Ltd. | Diskless client using a hypervisor |
US7941657B2 (en) * | 2007-03-30 | 2011-05-10 | Lenovo (Singapore) Pte. Ltd | Multi-mode mobile computer with hypervisor affording diskless and local disk operating environments |
US8310336B2 (en) | 2008-10-10 | 2012-11-13 | Masimo Corporation | Systems and methods for storing, analyzing, retrieving and displaying streaming medical data |
US8156298B1 (en) * | 2007-10-24 | 2012-04-10 | Adam Stubblefield | Virtualization-based security apparatuses, methods, and systems |
US9262194B2 (en) * | 2008-06-10 | 2016-02-16 | Apple Inc. | Virtual machine communications |
US9323894B2 (en) | 2011-08-19 | 2016-04-26 | Masimo Corporation | Health care sanitation monitoring system |
US10032002B2 (en) | 2009-03-04 | 2018-07-24 | Masimo Corporation | Medical monitoring system |
JP5749658B2 (en) | 2009-03-04 | 2015-07-15 | マシモ・コーポレイション | Medical monitoring system |
US10007758B2 (en) | 2009-03-04 | 2018-06-26 | Masimo Corporation | Medical monitoring system |
US20100234718A1 (en) * | 2009-03-12 | 2010-09-16 | Anand Sampath | Open architecture medical communication system |
US8135818B2 (en) * | 2009-06-22 | 2012-03-13 | Red Hat Israel, Ltd. | Automatic virtual machine migration in mixed SBC/CBC environment |
US8738781B2 (en) | 2009-06-22 | 2014-05-27 | Red Hat Israel, Ltd. | Launching a virtual machine associated with a client during startup |
US8281018B2 (en) * | 2009-06-22 | 2012-10-02 | Red Hat Israel, Ltd. | Method for automatically providing a client with access to an associated virtual machine |
US8341213B2 (en) * | 2009-06-22 | 2012-12-25 | Red Hat Israel, Ltd. | Method for improving boot time of a client having a virtualized operating environment |
KR101640769B1 (en) | 2009-11-06 | 2016-07-19 | 삼성전자주식회사 | Virtual system and instruction executing method thereof |
KR101284791B1 (en) * | 2009-12-04 | 2013-07-10 | 한국전자통신연구원 | Method and apparatus for implementing computer operating system using mobile terminal |
KR20110072922A (en) * | 2009-12-23 | 2011-06-29 | 삼성전자주식회사 | Method for implementing additional extended feature in image forming apparatus and image forming apparatus for performing thereof |
US8839239B2 (en) * | 2010-06-15 | 2014-09-16 | Microsoft Corporation | Protection of virtual machines executing on a host device |
KR101105528B1 (en) * | 2010-06-29 | 2012-01-13 | 삼성에스디에스 주식회사 | Terminal device for advertisement and method for advertisement using the same |
US9075642B1 (en) * | 2011-09-30 | 2015-07-07 | Emc Corporation | Controlling access to resources using independent and nested hypervisors in a storage system environment |
KR101692733B1 (en) * | 2012-01-30 | 2017-01-04 | 엘지전자 주식회사 | Method for managing virtual machine and device therefor |
US8958420B1 (en) * | 2012-03-30 | 2015-02-17 | Juniper Networks, Inc. | Methods and apparatus for virtualizing switch control plane engine |
RU2537814C9 (en) * | 2013-02-06 | 2018-07-13 | Закрытое акционерное общество "Крафтвэй корпорэйшн ПЛС" | Method of launching hypervisor in computer system at early computer booting stage |
RU2538286C9 (en) * | 2013-02-06 | 2018-07-12 | Закрытое акционерное общество "Крафтвэй корпорэйшн ПЛС" | Method of launching hypervisor in computer system at early computer booting stage |
CN104714821B (en) * | 2013-12-17 | 2018-07-31 | 华为技术有限公司 | Operation system example creation method and device |
US10720195B2 (en) | 2015-09-25 | 2020-07-21 | Intel Corporation | Efficient memory activation at runtime |
RU2609761C1 (en) * | 2015-09-30 | 2017-02-02 | Акционерное общество "Лаборатория Касперского" | Method for code performance in hypervisor mode |
US10108446B1 (en) * | 2015-12-11 | 2018-10-23 | Fireeye, Inc. | Late load technique for deploying a virtualization layer underneath a running operating system |
US20210026950A1 (en) * | 2016-03-07 | 2021-01-28 | Crowdstrike, Inc. | Hypervisor-based redirection of system calls and interrupt-based task offloading |
US10318311B2 (en) * | 2016-06-30 | 2019-06-11 | Amazon Technologies, Inc. | Memory allocation techniques at partially-offloaded virtualization managers |
US10127068B2 (en) | 2016-06-30 | 2018-11-13 | Amazon Technologies, Inc. | Performance variability reduction using an opportunistic hypervisor |
KR102203648B1 (en) * | 2018-03-20 | 2021-01-15 | 미쓰비시덴키 가부시키가이샤 | Information processing apparatus, method, and program |
WO2020124354A1 (en) * | 2018-12-18 | 2020-06-25 | Intel Corporation | Computing method and apparatus with multi-phase/level boot |
CN112579014A (en) * | 2019-09-27 | 2021-03-30 | 宝能汽车集团有限公司 | Multi-screen display method and system based on Hypervisor, vehicle and storage medium |
RU2770136C1 (en) * | 2021-04-22 | 2022-04-14 | Общество С Ограниченной Ответственностью "Кировский Региональный Центр Деловой Информации" | Method for protecting a computer system from unauthorised access to information, implemented at the hardware platform level by means of virtualisation mechanisms, and apparatus for implementation thereof |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040139437A1 (en) * | 2000-06-08 | 2004-07-15 | Arndt Richard Louis | Hypervisor virtualization of OS console and operator panel |
US20050055192A1 (en) * | 2000-12-21 | 2005-03-10 | Microsoft Corporation | System and method for the logical substitution of processor control in an emulated computing environment |
US6892383B1 (en) * | 2000-06-08 | 2005-05-10 | International Business Machines Corporation | Hypervisor function sets |
US20060136667A1 (en) * | 2004-12-17 | 2006-06-22 | International Business Machines Corporation | System, method and program to preserve a cache of a virtual machine |
US20070022427A1 (en) * | 2003-12-12 | 2007-01-25 | Arndt Richard L | Hypervisor virtualization of OS console and operator panel |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5437033A (en) * | 1990-11-16 | 1995-07-25 | Hitachi, Ltd. | System for recovery from a virtual machine monitor failure with a continuous guest dispatched to a nonguest mode |
US6530078B1 (en) * | 1998-03-26 | 2003-03-04 | Alexander V. Shmid | Virtual machines in OS/390 for execution of any guest system |
US6567933B1 (en) * | 1999-02-19 | 2003-05-20 | Texas Instruments Incorporated | Emulation suspension mode with stop mode extension |
US7093239B1 (en) * | 2000-07-14 | 2006-08-15 | Internet Security Systems, Inc. | Computer immune system and method for detecting unwanted code in a computer system |
US7035963B2 (en) * | 2000-12-27 | 2006-04-25 | Intel Corporation | Method for resolving address space conflicts between a virtual machine monitor and a guest operating system |
GB0112781D0 (en) | 2001-05-25 | 2001-07-18 | Global Continuity Plc | Method for rapid recovery from a network file server failure |
US7428485B2 (en) * | 2001-08-24 | 2008-09-23 | International Business Machines Corporation | System for yielding to a processor |
JP2003202964A (en) * | 2002-01-09 | 2003-07-18 | Hitachi Ltd | Method for controlling computer system, computer system, method for controlling storage device and storage device |
US20050160423A1 (en) * | 2002-12-16 | 2005-07-21 | Bantz David F. | Enabling a guest virtual machine in a windows environment for policy-based participation in grid computations |
US20060070065A1 (en) * | 2004-09-29 | 2006-03-30 | Zimmer Vincent J | Memory support for heterogeneous virtual machine guests |
US7647589B1 (en) * | 2005-02-07 | 2010-01-12 | Parallels Software International, Inc. | Methods and systems for safe execution of guest code in virtual machine context |
-
2006
- 2006-05-15 US US11/383,455 patent/US8176485B2/en active Active
-
2007
- 2007-05-03 TW TW096115773A patent/TW200813833A/en unknown
- 2007-05-14 RU RU2008145040/08A patent/RU2446447C2/en active
- 2007-05-14 AU AU2007249730A patent/AU2007249730A1/en not_active Abandoned
- 2007-05-14 EP EP07777032.9A patent/EP2024826B1/en active Active
- 2007-05-14 CN CN2007800177917A patent/CN101449240B/en active Active
- 2007-05-14 ES ES07777032T patent/ES2744379T3/en active Active
- 2007-05-14 WO PCT/US2007/011545 patent/WO2007133741A1/en active Application Filing
- 2007-05-14 MX MX2008014548A patent/MX2008014548A/en not_active Application Discontinuation
- 2007-05-14 CA CA002648874A patent/CA2648874A1/en not_active Abandoned
- 2007-05-14 JP JP2009511012A patent/JP2009537897A/en not_active Withdrawn
- 2007-05-14 BR BRPI0711369A patent/BRPI0711369A8/en not_active Application Discontinuation
- 2007-05-14 KR KR1020087027870A patent/KR20090009866A/en not_active Application Discontinuation
-
2008
- 2008-10-21 NO NO20084432A patent/NO20084432L/en not_active Application Discontinuation
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040139437A1 (en) * | 2000-06-08 | 2004-07-15 | Arndt Richard Louis | Hypervisor virtualization of OS console and operator panel |
US6892383B1 (en) * | 2000-06-08 | 2005-05-10 | International Business Machines Corporation | Hypervisor function sets |
US20050055192A1 (en) * | 2000-12-21 | 2005-03-10 | Microsoft Corporation | System and method for the logical substitution of processor control in an emulated computing environment |
US20070022427A1 (en) * | 2003-12-12 | 2007-01-25 | Arndt Richard L | Hypervisor virtualization of OS console and operator panel |
US20060136667A1 (en) * | 2004-12-17 | 2006-06-22 | International Business Machines Corporation | System, method and program to preserve a cache of a virtual machine |
Non-Patent Citations (2)
Title |
---|
KING S. T. ET AL.: "Operating System Support for Virtual Machines", PROCEEDINGS OF THE USENIX ANNUAL TECHNICAL CONFERENCE, 4 June 2003 (2003-06-04), pages 71 - 84, XP002332821 |
See also references of EP2024826A4 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011526390A (en) * | 2008-06-27 | 2011-10-06 | マイクロソフト コーポレーション | Lazy processing of interrupt message end in virtual environment |
Also Published As
Publication number | Publication date |
---|---|
MX2008014548A (en) | 2008-11-27 |
BRPI0711369A2 (en) | 2011-11-01 |
JP2009537897A (en) | 2009-10-29 |
TW200813833A (en) | 2008-03-16 |
KR20090009866A (en) | 2009-01-23 |
BRPI0711369A8 (en) | 2017-01-17 |
CN101449240A (en) | 2009-06-03 |
RU2446447C2 (en) | 2012-03-27 |
RU2008145040A (en) | 2010-05-20 |
AU2007249730A1 (en) | 2007-11-22 |
NO20084432L (en) | 2008-12-12 |
US8176485B2 (en) | 2012-05-08 |
EP2024826A1 (en) | 2009-02-18 |
CN101449240B (en) | 2012-06-06 |
ES2744379T3 (en) | 2020-02-24 |
US20070266389A1 (en) | 2007-11-15 |
EP2024826A4 (en) | 2012-07-11 |
CA2648874A1 (en) | 2007-11-22 |
EP2024826B1 (en) | 2019-06-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8176485B2 (en) | Launching hypervisor under running operating system | |
US10108446B1 (en) | Late load technique for deploying a virtualization layer underneath a running operating system | |
KR101019937B1 (en) | Secure operating system switching | |
US7603713B1 (en) | Method for accelerating hardware emulator used for malware detection and analysis | |
US7209994B1 (en) | Processor that maintains virtual interrupt state and injects virtual interrupts into virtual machine guests | |
US7945436B2 (en) | Pass-through and emulation in a virtual machine environment | |
US8321931B2 (en) | Method and apparatus for sequential hypervisor invocation | |
US8612633B2 (en) | Virtual machine fast emulation assist | |
EP3048551B1 (en) | Systems and methods for active operating system kernel protection | |
US11256534B2 (en) | System and method for trapping system calls for remote execution | |
US8091086B1 (en) | System and method for virtualization using an open bus hypervisor | |
US9465617B1 (en) | Implementing upcall from secure to non-secure mode by injecting exception into non-secure mode | |
US10489185B2 (en) | Hypervisor-assisted approach for locating operating system data structures based on attribute matching | |
US20180267818A1 (en) | Hypervisor-assisted approach for locating operating system data structures based on notification data | |
US7552434B2 (en) | Method of performing kernel task upon initial execution of process at user level | |
US10514945B2 (en) | Host-based virtual machine introspection with dynamic guest assistance | |
JP2007507779A (en) | operating system | |
Im et al. | On-demand virtualization for live migration in bare metal cloud | |
Im et al. | On-demand Virtualization for Post-copy OS Migration in Bare-metal Cloud | |
RU2585978C2 (en) | Method of invoking system functions in conditions of use of agents for protecting operating system kernel | |
US11188367B2 (en) | Guest operating system physical memory page protection using hypervisor | |
RU2596577C2 (en) | Method of creating a system call handler |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200780017791.7 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07777032 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2648874 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007249730 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 5841/CHENP/2008 Country of ref document: IN |
|
ENP | Entry into the national phase |
Ref document number: 2007249730 Country of ref document: AU Date of ref document: 20070514 Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/a/2008/014548 Country of ref document: MX |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008145040 Country of ref document: RU Ref document number: 2009511012 Country of ref document: JP Ref document number: 1020087027870 Country of ref document: KR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007777032 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: PI0711369 Country of ref document: BR Kind code of ref document: A2 Effective date: 20081112 |