EP1628214B1 - Vorrichtungen und Verfahren zum Ausführen eines Betriebssystems in einer virtuellen Maschine Umgebung - Google Patents

Vorrichtungen und Verfahren zum Ausführen eines Betriebssystems in einer virtuellen Maschine Umgebung Download PDF

Info

Publication number
EP1628214B1
EP1628214B1 EP05105586A EP05105586A EP1628214B1 EP 1628214 B1 EP1628214 B1 EP 1628214B1 EP 05105586 A EP05105586 A EP 05105586A EP 05105586 A EP05105586 A EP 05105586A EP 1628214 B1 EP1628214 B1 EP 1628214B1
Authority
EP
European Patent Office
Prior art keywords
operating system
virtual machine
host
computer
guest
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Not-in-force
Application number
EP05105586A
Other languages
English (en)
French (fr)
Other versions
EP1628214A2 (de
EP1628214A3 (de
Inventor
Rene Antonio Vega
Eric P. Traut
Mike Neil
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Corp
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corp filed Critical Microsoft Corp
Publication of EP1628214A2 publication Critical patent/EP1628214A2/de
Publication of EP1628214A3 publication Critical patent/EP1628214A3/de
Application granted granted Critical
Publication of EP1628214B1 publication Critical patent/EP1628214B1/de
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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
    • 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/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • 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/4555—Para-virtualisation, i.e. guest operating system has to be modified

Definitions

  • Patent Application No. 10/274,298 (Atty. Docket No. MSFT-2564 / 304108.01), filed on October 18, 2002 and entitled, "SOFTWARE LICENSE ENFORCEMENT MECHANISM FOR AN EMULATED COMPUTING ENVIRONMENT,"
  • the present invention generally relates to the field virtual machines (also known as "processor virtualization") and software that executes in a virtual machine environment. More specifically, the present invention relates to systems and methods for implementing an operating system that is able to ascertain whether it is running in a virtual machine environment and that is able to modify its behavior accordingly.
  • Computers include general purpose central processing units (CPUs) that are designed to execute a specific set of system instructions.
  • CPUs central processing units
  • a group of processors that have similar architecture or design specifications may be considered to be members of the same processor family. Examples of current processor families include the Motorola 680X0 processor family, manufactured by Motorola, Inc. of Phoenix, Arizona; the Intel 80X86 processor family, manufactured by Intel Corporation of Sunnyvale, California; and the PowerPC processor family, which is manufactured by Motorola, Inc. and used in computers manufactured by Apple Computer, Inc. of Cupertino, California.
  • processors may vary wi dely within a family according to their clock speed and other performance parameters.
  • Each family of microprocessors executes instructions that are unique to the processor family.
  • the collective set of instructions that a processor or family of processors can ex ecute is known as the processor's instruction set.
  • the instruction set used by the Intel 80X86 processor family is incompatible with the instruction set used by the PowerPC processor family.
  • the Intel 80X86 instruction set is based on the Complex Instruction Set Computer (CISC) format.
  • the Motorola PowerPC instruction set is based on the Reduced Instruction Set Computer (RISC) farmat.
  • CISC processors use a large number of instructions, some of which can perform rather complicated functions, but which require generally many clock cycles to execute.
  • RISC processors use a smaller number of available instructions to perform a simpler set of functions that are executed at a much higher rate.
  • the uniqueness of the processor family among computer systems also typically results in incompatibility among the other elements of hardware architecture of the computer systems.
  • a computer system manufactured with a processor from the Intel 80X86 processor family will have a hardware architecture that is different from the hardware architecture of a computer system manufactured with a processor from the PowerPC processor family. Because of the uniqueness of the processor instruction set and a computer system's hardware architecture, application software programs are typically written to run on a particular computer system running a particular operating system.
  • a field of technology has developed in which a given computer having one type of CPU, called a host, will include an emulator program that allows the host computer to emulate the instructions of an unrelated type of CPU, called a guest.
  • the host computer will execute an application that will cause one or more host instructions to be called in response to a given guest instruction.
  • the host computer can both run software design for its own hardware architecture and software written for computers having an umrelated hardware architecture.
  • a computer system manufactured by Apple Computer may run operating systems and program written for PC-based computer systems.
  • an emulator program may also be possible to use an emulator program to operate concurrently on a single CPU multiple incompatible operating systems.
  • an emulator program can host one of the two operating systems, allowing the otherwise incompatible operating systems to run concurrently on the same computer system.
  • the guest computer system When a guest computer system is emulated on a host computer system, the guest computer system is said to be a "virtual machine" as the guest computer system only exists in the host computer system as a pure software representation of the operation of one specific hardware architecture.
  • the terms emulator, virtual machine, and processor emulation are sometimes used interchangeably to denote the ability to mimic or emulate the hardware architecture of an entire computer system.
  • the Virtual PC software created by Connectix Corporation of San Mateo, California emulates an entire computer that includes an Intel 80X86 Pentium processor and various motherboard components and cards. The operation of these components is emulated in the virtual machine that is being run on the host machine.
  • An emulator program executing on the operating system software and hardware architecture of the host computer, such as a computer system having a PowerPC processor, mimics the operation of the entire guest computer system.
  • the emulator program acts as the interchange between the hardware architecture of the host machine and the instructions transmitted by the software running within the emulated environment.
  • This emulator program may be a host operating system (HOS), which is an operating system running directly on the physical computer hardware.
  • HOS host operating system
  • the emulated environment might also be a virtual machine monitor (VMM) which is a software layer that runs directly above the hardware and which virtualizes all the resources of the machine by exposing interfaces that are the same as the hardware the VMM is virtualizing (which enables the VMM to go unnoticed by operating system layers running above it).
  • a host operating system and a VMM may run side-by-side on the same physical hardware.
  • OSs In conventional operating systems (OSs), certain OS activities are performed with an assumption that the operating system is running on dedicated physical hardware. In a virtual machine environment, these activities can be detrimental to the other guest OSs that are running concurrently on the same physical hardware. These detrimental activities tie up operating system resources (designed to run on dedicated physical hardware, not in a virtual environment), because the operating system assumes that the hardware is dedicated to it, and has no knowledge of other operating systems using the resources or waiting to use them. What is needed is a way to modify the behavior of a guest OS such that it is not detrimental to other guest OSs that are running in a virtual machine environment. Pages 1-14 of the Proceedings of the Usemix Annual Technical Conference (June 2002) disclose Denali, lightweight virtual machines for distributed and networked applications.
  • the invention refers to the method of claim 1, the system of claim 7 and the computer-readable medium of claim 13. Preferred embodiments are disclosed in the dependent claims.
  • the present invention includes systems for and methods of implementing an operating system that is capable of ascertaining whether it is operating in a virtual machine environment and is further capable of modifying its behavior to operate more efficiently in a vi rtual machine environment.
  • Embodiments of the present invention are directed to a system for and method of providing operating systems that are aware that they are operating in a virtual machine environment and, as a result of this realization, are able to reduce some of the performance overhead which has been historically problematic with the virtual machine environment.
  • the introduction of a shared communication area between the host operating system and the guest operating systems provides a mechanism for communication between guests and host without passing control of the computer between host and guests.
  • One example of the type of communications passed between guest operating systems and host relates to thread scheduling.
  • guest operating systems send additional information (such as execution priorities) to the host operating system, which allows the host operating system to make more-efficient thread scheduling decisions, because the host has more information regarding the overall demand (including that of guests) for processor time.
  • Fig. 1 is a block diagram representing a computer system in which aspects of the present invention may be incorporated;
  • Fig. 2 illustrates the logical layering of the hardware and software architecture for an emulated operating environment in a computer system
  • Fig. 3A illustrates a virtualized computing system
  • Fig. 3B illustrates an alternative embodiment of a virtualized computing system comprising a virtual machine monitor running alongside a host operating system
  • Fig. 4 illustrates a virtualized computing system from Fig. 3A further comprising a host operating system with VM-aware guest operating systems;
  • Fig. 5 is a flowchart that illustrates a method of implementing a VM-aware guest operating system with the capability to modify its behavior in order to improve efficiency in a virtual machine environment;
  • Fig. 6 illustrates an exemplary virtualized computing system comprising a host operating system with shared communication areas between the host operating system and VM-aware guest operating systems;
  • Fig. 7 is a flowchart that illustrates an exemplary method of scheduling threads in a VM-aware operating system according to the present invention.
  • Fig. 1 Numerous embodiments of the present invention may execute on a computer.
  • Fig. 1 and the following discussion is intended to provide a brief general description of a suitable computing environment in which the invention may be implemented.
  • the in vention will be described in the general context of computer executable instructions, such as program modules, being executed by a computer, such as a client workstation or a server.
  • program modules include routines, programs, objects, components, data structures and the like that perform particular tasks or implement particular abstract data types.
  • the invention may be practiced with other computer system configurations, including hand held devices, multi processor systems, microprocessor based or programmable consumer electronics, network PCs, minicomputers, mainframe computers and the like.
  • the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote memory storage devices.
  • an exemplary general purpose computing system includes a conventional personal computer 20 or the like, including a processing unit 21, a system memory 22, and a system bus 23 that couples various system components including the system memory to the processing unit 21.
  • the system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
  • the system memory includes read only memory (ROM) 24 and random access memory (RAM) 25.
  • ROM read only memory
  • RAM random access memory
  • the personal computer 20 may further include a hard disk drive 27 for reading from and writing to a hard disk, not shown, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM or other optical media.
  • the hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical drive interface 34, respectively.
  • the drives and their associated computer readable media provide non volatile storage of computer readable instructions, data structures, program modules and other data for the personal computer 20.
  • exemplary environment described herein employs a hard disk, a removable magnetic disk 29 and a removable optical disk 31, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs) and the like may also be used in the exemplary operating environment.
  • RAMs random access memories
  • ROMs read only memories
  • a number of program modules may be stored on the hard disk, magnetic disk 29, optical disk 31, ROM 24 or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37 and program data 38.
  • a user may enter commands and information into the personal computer 20 through input devices such as a keyboard 40 and pointing device 42.
  • Other input devices may include a microphone, joystick, game pad, satellite disk, scanner or the like.
  • serial port interface 46 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port or universal serial bus (USB).
  • a monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48.
  • the exemplary system of Fig. 1 also includes a host adapter 55, Small Computer System Interface (SCSI) bus 56, and an external storage device 62 connected to the SCSI bus 56.
  • SCSI Small Computer System Interface
  • the personal computer 20 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 49.
  • the remote computer 49 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the personal computer 20, although only a memory storage device 50 has been illustrated in Fig. 1 .
  • the logical connections depicted in Fig. 1 include a local area network (LAN) 51 and a wide area network (WAN) 52.
  • LAN local area network
  • WAN wide area network
  • the personal computer 20 When used in a LAN networking environment, the personal computer 20 is connected to the LAN 51 through a network interface or adapter 53. When used in a WAN networking environment, the personal computer 20 typically includes a modem 54 or other means for establishing communications over the wide area network 52, such as the Internet.
  • the modem 54 which may be internal or external, is connected to the system bus 23 via the serial port interface 46.
  • program modules depicted relative to the personal computer 20, or portions thereof may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
  • numerous embodiments of the present invention are particularly well-suited for computerized systems, nothing in this document is intended to limit the invention to such embodiments.
  • computer systems generally comprise one or more layers of software running on a foundational layer of hardware. This layering is done for reasons of abstraction. By defining the interface for a given layer of software, that layer can be implemented differently by other layers above it. In a well-designed computer system, each layer only knows about (and only relies upon) the immediate layer beneath it. This allows a layer or a "stack" (multiple adjoining layers) to be replaced without negatively impacting the layers above said layer or stack.
  • software applications upper layers
  • lower layers typically rely on lower levels of the operating system (lower layers) to write files to some form of permanent storage, and these applications do not need to understand the difference between writing data to a floppy disk, a hard drive, or a network folder. If this lower layer is replaced with new operating system components for writing files, the operation of the upper layer software applications remains unaffected.
  • VM virtual machine
  • Fig. 2 is a diagram representing the logical layering of the hardware and software architecture for an emulated operating environment in a computer system.
  • An emulation program 94 runs on a host operating system and/or hardware architecture 92.
  • Emulation program 94 emulates a guest hardware architecture 96 and a guest operating system 98.
  • Software application 100 in turn runs on guest operating system 98.
  • software application 100 can run on the computer system 90 even though software application 100 is designed to run on an operating system that is generally incompatible with the host operating system and hardware architecture 92.
  • Fig. 3A illustrates a virtualized computing system comprising a host operating system software layer 104 running directly above physical computer hardware 102, and the host operating system (host OS) 104 virtualizes all the resources of the machine by exposing interfaces that are the same as the hardware the host OS is virtualizing (which enables the host OS to go unnoticed by operating system layers running above it).
  • host OS host operating system
  • a virtual machine monitor, or VMM, software layer 104' may be running in place of or alongside a host OS 104", the latter option being illustrated in Fig. 3B .
  • VMM virtual machine monitor
  • a host OS 104 the latter option being illustrated in Fig. 3B .
  • all discussion hereinafter shall be directed to the embodiment illustrated in Fig. 3A ; however, every aspect of such discussion shall equally apply to the embodiment of Fig. 3B wherein the VMM 104' of Fig. 3B essentially replaces, on a functional level, the role of the host OS 104 of Fig. 3A described herein below.
  • VM A 108 and VM B 110 are virtualized computer hardware representations that exist only as software constructions and which are made possible due to the presence of specialized software code that not only presents VMA 108 and VM B 110 to Guest OS A 112 and Guest OS B 114 respectively, but which also performs all of the software steps necessary for Guest OS A 112 and Guest OS B 114 to indirectly interact with the real physical computer hardware 102.
  • This complete functionality can generally be referred to as a virtual machine monitor (VMM) (shown only in Fig. 3B ) where, for certain embodiments (such as the one illustrated in Fig. 3A ), the VMM comprises part of the host operating system 104.
  • VMM virtual machine monitor
  • the VMM may be an application running above the host operating system 104 and interacting with the computer hardware only through said host operating system 104.
  • the VMM may comprise a partially independent software system that on some levels interacts indirectly with the computer hardware 102 via the host operating system 104 but on other levels the VMM interacts directly with the computer hardware 102 (similar to the way the host operating system interacts directly with the computer hardware).
  • the VMM may comprise a partially independent software system that on some levels interacts indirectly with the computer hardware 102 via the host operating system 104 but on other levels the VMM interacts directly with the computer hardware 102 (similar to the way the host operating system interacts directly with the computer hardware).
  • the VMM may comprise a fully independent software system that on all levels interacts directly with the computer hardware 102 (similar to the way the host operating system interacts directly with the computer hardware) without utilizing the host operating system 104 (although still interacting with said host operating system 104 insofar as coordinating use of said computer hardware 102 and avoiding conflicts and the like).
  • any reference to interaction between applications 116, 118, and 120 via VM A 108 and/or VM B 110 respectively should be interpreted to be in fact an interaction between the applications 116, 118, and 120 and a VMM.
  • any reference to interaction between applications VM A 108 and/or VM B 110 with the host operating system 104 and/or the computer hardware 102 should be interpreted to be in fact an interaction between the VMM and the host operating system 104 or the computer hardware 102 as appropriate.
  • VM A 108 which may be, for example, a virtualized Intel 386 processor
  • VM B 110 which may be, for example, a virtualized version of one of the Motorola 680X0 family of processors.
  • guest OSs guest operating systems
  • Above guest OS A 112 are running two applications, application A1 116 and application A2 118, and above guest OS B 114 is application B1 120.
  • virtual machines have been based upon the illusion that guest OSs (e.g., guest OS A 112) are running on dedicated hardware, when in fact they are sharing the hardware with other guest OSs (e.g., guest OS B 114).
  • Host OS 104 is responsible for maintaining this illusion.
  • the present invention relaxes this illusion and allows the guest OSs to ascertain whether they are running in a VM, and, subsequently, to alter their behavior, based on this realization. Behavior modifications are described that will increase the efficiency of guest QSs operating in a VM environment.
  • Fig. 4 illustrates a virtualized computing system similar to that shown in Fig. 3A , but in Fig. 4 , a VM-aware guest OS A 132 and a VM-aware guest OS B 134 have replaced guest OS A 112 and guest OS B 114, respectively.
  • VM-aware guest OS A 132 and VM-aware guest OS B 134 are operating systems that are able to ascertain whether they are operating in a virtual machine environment and, if so, are able to modify their behavior to operate more efficiently.
  • VM-aware guest OS A 132 and VM-aware guest OS B 134 of Fig. 4 is described in reference to Fig. 5 , which is a flowchart that illustrates a method 140 of implementing a VM-aware operating system with the capability to modify its behavior in order to improve efficiency in a virtual machine environment.
  • the method first comprises starting the VM-aware operating system (e.g., VM-aware guest OS A 132 or VM-aware guest OS B 134).
  • the VM-aware OS determines whether it is operating in a VM environment. This determination is done by any of a variety of methods, including the use of synthetic instructions, as described in U.S. Patent Application No. 10/685,051 filed on October 14, 2003and entitled, "SYSTEMS AND METHODS FOR USING SYNTHETIC INSTRUCTIONS IN A VIRTUAL MACHINE" (hereinafter the '051 patent application).
  • the '051 patent application describes a method for an operating system to determine whether it is running on a virtualized processor or running directly on an x86 processor, by executing a synthetic instruction (e.g., VMCPUID) for returning a value representing an identity for the central processing unit.
  • VMCPUID synthetic instruction
  • the guest OS concludes that the operating system is running on a virtualized processor; if an exception occurs in response to the synthetic instruction, the guest OS concludes that the operating system is running directly on an x86 processor.
  • Another method for determining whether the guest OS is running in a VM environment include running a series of tests threads and comparing performance of the current environment to historical results. In any event, if the VM-aware OS determines that it is not operating in a VM environment, method 140 proceeds to step 146. Alternatively, if the VM-aware OS determines that it is operating in a VM environment, method 140 proceeds to step 150.
  • the VM-aware OS operates in its "traditional” manner, because it is operating on dedicated hardware and is not in a VM environment.
  • the VM-aware operating system determines whether a "shut down” command has been received. If a "shut down” command is received, the VM-aware OS shuts down and method 130 ends. If no "shut down” command has been received, the VM-aware OS continues to operate in the "traditional” manner, as described in step 146.
  • the VM-aware OS modifies its behavior in order to operate more efficiently in a VM environment.
  • behavior modifications include, but are not limited to, 1) thread scheduling; and 2) utilizing synthetic instructions (as in the '051 patent application) that contain the execution priorities to host OS 104.
  • VM "synthetic instructions" are otherwise-illegal processor instructions that have special meanings to the VM.
  • the VM-aware OS determines whether a "shut down" command has been received. If a "shut down” command is received, the VM-aware OS shuts down and method 130 ends. If no "shut down” command has been received, the VM-aware OS continues to operate in its modified, high-efficiency mode, as described in step 150.
  • a scheduler assigns processors to an execution context or thread.
  • the scheduler reviews all ready threads and then schedules the threads for processing. If there is no work to be done, the scheduler loops while looking for work for a period of time before finally entering a busy-wait zone.
  • this behavior is not detrimental to performance. However, in a virtual machine environment, this behavior is detrimental to other guest operating systems that have work ready, but for which the processor is occupied. This looping and busy-waiting time contributes to the high-overhead level associated with running operating systems in a virtual machine environment.
  • Fig. 6 is an exemplary system and method for behavior modification.
  • the present invention is not limited to thread scheduling behavior modifications.
  • Fig. 6 illustrates a virtualized computing system comprising a shared communication area A 162 arranged between host OS 104 and VM-aware guest OS A 132. Similarly, a shared communication area B 164 is arranged between host OS 104 and VM-aware guest OS B 134.
  • This virtualized computing system provides a way for guest OSs to operate more efficiently.
  • the virtualized computing system described in Fig. 6 includes a way for a guest OS to provide additional thread information (such as information regarding the priority of thread and expected duration of time for the thread to run). When this information is combined with information from other guest OSs, the host OS has a much clearer picture of all of the demand for resources within the system and is, therefore, able to make decisions that will greatly improve the efficiency of the system.
  • Shared communication areas A 162 and B 164 are mechanisms which provide VM-aware guest OS A 132 and VM-aware guest OS B 134 an efficient way to transfer information to host OS 104 without passing control to host OS 104. Passing control to host OS 104 is time consuming, therefore detrimental to overall system performance, and therefore to be avoided, if possible.
  • shared communication area A 162 and shared communication area B 164 are embodied with shared memory space.
  • shared communication area A 162 and shared communication area B 164 are embodied by a direct communications link between VM-aware guest OS A 132 and VM-aware guest OS B 134, respectively.
  • VM-aware guest OS A 132 and VM-aware guest OS B 134 further contain a VM-aware scheduler A 166 and a VM-aware scheduler B 168, respectively.
  • VM-aware schedulers A 166 and B 168 operate on a set of ready threads that have execution properties (such as priority, deadline, and reserve (a portion of processor assigned to a thread). The execution properties are placed into shared communication areas A 162 and B 164.
  • the virtualized computing system described in Fig. 6 further includes a host scheduler 172 within host OS 104.
  • Host scheduler 172 makes scheduling decisions that are more efficient, based on two new features of the system: first, VM-aware guest OS A 132 and VM-aware guest OS B 134 are aware that they are operating in a VM environment and are able to send execution priorities to host scheduler 172 to enable more-efficient execution of all threads from a plurality of VM-aware guest OSs; second, shared communication areas A 162 and B 164 provide an efficient way to send information to host OS 104 without passing control to host OS 104.
  • Host scheduler 172 assigns a plurality of virtual processors 170A-170N to process the threads, according to the execution priorities placed into shared communication areas A 162 and B 164.
  • Host scheduler 172 reviews the execution priorities for all VM-aware guest OSs (e.g., VM-aware guest OS A 132 and VM-aware guest OS B 134), creates a composite run-list based on the priorities from all VM-aware guests OSs, and assigns virtual processors 170 to process the threads accordingly.
  • VM-aware guest OSs e.g., VM-aware guest OS A 132 and VM-aware guest OS B 134
  • Fig. 7 is a flowchart that illustrates an exemplary method 180 of scheduling threads in an operating system in accordance with the invention.
  • the method starts with the VM-aware guest OS A 132 determining whether it is operating in a VM environment. This determination is done by any of a variety of methods including but not limited to the use of synthetic instructions as described in the '051 application (described above). If yes, method 180 proceeds to step 192; if no, method 180 proceeds to step 184.
  • VM-aware guest OS A 132 processes a thread.
  • VM-aware guest OS A 132 determines whether more threads are ready to be processed, If yes, method 180 returns to step 184; if not, method 180 proceeds to step 188.
  • VM-aware guest OS A 132 determines whether a "shut down" command has been received; if so, VM-aware guest OS A, 132 shuts down and method 180 ends; if no "shut down" command has been received, method 180 proceeds to step 190.
  • VM-aware guest OS A 132 enters a busy-wait status while it waits for more threads to be processed and, after a specified amount of time, method 180 returns to step 186 for the guest OS A 132 to check for more threads to process.
  • VM-aware guest OS A 132 which is operating now operating in an enhanced "VM-aware" mode-starts by processing a thread and then, at step 194, VM-aware guest OS A 132 determines whether more threads are ready to be processed. If yes, method 180 returns to step 192 for further processing; if not, method 180 proceeds to step 195.
  • guest OS A 132 determines whether a "shut down" command has been received and, if so, guest OS A shuts down and method 180 ends; if not, then at step 196, VM-aware guest OS A 132 indicates to host OS 104 (or, for certain alternative embodiments, to VMM 104') that guest OS A 132 currently has no work to do (that is, no threads to process). In one example, this indication is sent by VM-aware guest OS A 132 via shared communications area A 162 as described above.
  • this indication is performed by VM-aware guest OS A 132 sending a synthetic instruction to host OS 104 (which is programmed to understand said synthetic instruction, of course) and then, at step 198, host OS 104 determines whether work from other VMs is ready to be processed.
  • VM-aware guest OS A 132 indicates to host OS 104 in step 196 that it does not have any work (via shared communications area B 132 or via a synthetic instruction, for example), host OS 104 determines whether there is a need for processor resources elsewhere and, if not, then host OS 104 allows guest OS A 132 to keep receiving processor resources which essentially enables guest OS A 132 to continue processing even though guest OS A 132 has no work to do at present and, thus, guest OS A 132 will enter a busy-wait loop at step 199 before returning to step 194 to see if there are more threads to execute.
  • host OS 104 determines that there is a need for processor resources elsewhere, then host OS 104, at stet 200, takes the processor resources for guest OS A 132 and temporarily gives them to another process running on host OS A 104 (such as another VM and guest operating system, e.g., guest OS B 134) before given them back to host OS A 104, effectively suspending guest OS A 132 until host OS 104 provides it with processor resources once again and then, at that time, guest OS A optionally continues to a busy-wait state (which is skipped for certain alternative embodiments) before proceeding back to step 194.
  • host OS 104 determines that there is a need for processor resources elsewhere, then host OS 104, at stet 200, takes the processor resources for guest OS A 132 and temporarily gives them to another process running on host OS A 104 (such as another VM and guest operating system, e.g., guest OS B 134) before given them back to host OS A 104, effectively suspending guest OS A 132 until host OS 104 provides it with processor resources once again and then, at that time
  • the various systems, methods, and techniques described herein may be implemented with hardware or software or, where appropriate, with a combination of both.
  • the methods and apparatus of the present invention may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy di skettes, CD-ROMs, hard drives, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.
  • the computer will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.
  • One or more programs are preferably implemented in a high level procedural or object oriented programming language to communicate with a computer system.
  • the program(s) can be implemented in assembly or machine language, if desired.
  • the language may be a compiled or interpreted language, and combined with hardware implementations.
  • the methods and apparatus of the present invention may also be embodied in the form of program code that is transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via any other form of transmission, wherein, when the program code is received and loaded into and executed by a machine, such as an EPROM, a gate array, a programmable logic device (PLD), a client computer, a video recorder or the like, the machine becomes an apparatus for practicing the invention.
  • a machine such as an EPROM, a gate array, a programmable logic device (PLD), a client computer, a video recorder or the like
  • PLD programmable logic device
  • client computer a client computer
  • video recorder or the like
  • the program code When implemented on a general-purpose processor, the program code combines with the processor to provide a unique apparatus that operates to perform the indexing functionality of the present invention.

Claims (9)

  1. Ein Verfahren für ein Betriebssystem, durch Reduktion von Ausführungsmehraufwand die Effizienz zu erhöhen, wenn es auf einer virtuellen Maschine arbeitet,
    wobei das Verfahren umfasst, durch Ausführung einer synthetischen Anweisung zu bestimmen (144; 182), ob das Betriebssystem auf einer virtuellen Maschine (108; 110) arbeitet oder direkt auf einem x86-Prozessor, wobei das Betriebssystem im ersten Fall seine Ausführung ändert (150) um effizienter auf der genannten virtuellen Maschine zu arbeiten oder das Betriebssystem im zweiten Fall so effizient wie für eine zugehörige Standard-Hardwareumgebung möglich arbeitet,
    wobei das Ändern der Ausführung durch das Betriebssystem, um effizienter auf der virtuellen Maschine zu arbeiten, die Verwendung eines gemeinsamen Kommunikationsbereichs (162; 164) zwischen dem Betriebssystem (132; 134) und einem Host-Betriebssystem (104) beinhaltet, um Information zu übertragen ohne Kontrolle abzugeben,
    wobei der gemeinsame Kommunikationsbereich vom Betriebssystem dazu verwendet wird, zusätzliche Information an das Host-Betriebssystem zu senden, was dem Host-Betriebssystem erlaubt, effizientere Terminierungsentscheidungen für Ausführungsstränge zu treffen,
    wobei die zusätzliche Information solche Information ist, die die Priorität eines Ausführungsstrangs oder die erwartete Laufzeit eines Ausführungsstrangs betrifft,
    und wobei eine synthetische Anweisung eine Anweisung ist, die für die x86-Architektur unzulässig ist, aber verständlich für die virtuelle Maschine.
  2. Das Verfahren von Anspruch 1, das zusätzlich die Verwendung mindestens einer synthetischen Anweisung umfasst, die Ausführungsprioritäten für das Host-Betriebssystem enthält.
  3. Das Verfahren von Anspruch 1, bei dem die effizienteren Terminierungsentscheidungen von mindestens einem Steuerungsprogramm (172) im Host-Betriebssystem getroffen werden, um effektiver mindestens ein Prozessorbetriebsmittel einzusetzen.
  4. Ein System für ein Betriebssystem, um durch Reduktion von Ausführungsmehraufwand die Effizienz zu erhöhen, wenn es auf einer virtuellen Maschine arbeitet,
    wobei das System
    mindestens ein Untersystem umfasst, das dazu dient, durch Ausführung einer synthetischen Anweisung zu bestimmen (144; 182), ob das Betriebssystem auf einer virtuellen Maschine (108; 110) arbeitet oder direkt auf einem x86-Prozessor, und das Betriebssystem im ersten Fall seine Ausführung ändert (150), um effizienter auf der genannten virtuellen Maschine zu arbeiten, oder das Betriebssystem im zweiten Fall so effizient wie für eine zugehörige Standard-Hardwareumgebung möglich arbeitet,
    und weiterhin mindestens ein Untersystem umfasst, mit dem das genannte Element des genannten Betriebssystems seine Ausführung durch die Verwendung eines gemeinsamen Kommunikationsbereichs (162; 164) zwischen dem Betriebssystem (132; 134) und einem Host-Betriebssystem (104) zum Übertragen von Information ohne Abgabe von Kontrolle ändert, um effizienter auf der virtuellen Maschine zu arbeiten,
    wobei der gemeinsame Kommunikationsbereich vom Betriebssystem dazu verwendet wird, zusätzliche Information an das Host-Betriebssystem zu senden, was dem Host-Betriebssystem erlaubt, effizientere Terminierungsentscheidungen für Ausführungstränge zu treffen,
    wobei die zusätzliche Information solche Information ist, die die Priorität eines Ausführungsstrangs oder die erwartete Laufzeit eines Ausführungsstrangs betrifft,
    und wobei eine synthetische Anweisung eine Anweisung ist, die für die x86-Architektur unzulässig ist, aber verständlich für die virtuelle Maschine.
  5. Das System von Anspruch 4, das weiterhin mindestens ein Untersystem umfasst und mindestens eine synthetische Anweisung verwendet, die Ausführungsprioritäten für das Host-Betriebssystem enthält.
  6. Das System von Anspruch 4, das weiterhin mindestens ein Untersystem umfasst, mit dem die effizienteren Terminierungsentscheidungen von mindestens einem Steuerungsprogramm (172) im Host-Betriebssystem getroffen werden, um effektiver mindestens ein Prozessorbetriebsmittel einzusetzen.
  7. Ein computerlesbares Medium mit computerlesbaren Anweisungen für ein Betriebssystem, durch Reduktion von Ausführungsmehraufwand die Effizienz zu erhöhen, wenn es auf einer virtuellen Maschine arbeitet,
    wobei die computerlesbaren Anweisungen

    Instruktionen einschließen, durch Ausführung einer synthetischen Anweisung zu bestimmen (144; 182), ob das Betriebssystem auf einer virtuellen Maschine (108; 110) arbeitet oder direkt auf einem x86-Prozessor, wobei das Betriebssystem im ersten Fall seine Ausführung ändert (150), um effizienter auf der genannten virtuellen Maschine zu arbeiten, oder das Betriebssystem im zweiten Fall so effizient wie für eine zugehörige Standard-Hardwareumgebung möglich arbeitet,
    und weiterhin Instruktionen, mit denen das genannte Element des besagten Betriebssystems seine Ausführung dadurch zum effizienteren Arbeiten auf der virtuellen Maschine ändert, dass mindestens ein gemeinsamer Kommunikationsbereich (162; 164) zwischen dem Betriebssystem (132; 134) und einem Host-Betriebssystem (104) verwendet wird, um Information zu übertragen ohne Kontrolle abzugeben;
    wobei der gemeinsame Kommunikationsbereich vom Betriebssystem dazu verwendet wird, zusätzliche Information an das Host-Betriebssystem zu senden, was dem Host-Betriebssystem erlaubt, effizientere Terminierungsentscheidungen für Ausführungsstränge zu treffen,
    wobei die zusätzliche Information solche Information ist, die die Priorität eines Ausführungsstrangs oder die erwartete Laufzeit eines Ausführungsstrangs betrifft,
    und wobei eine synthetische Anweisung eine Anweisung ist, die für die x86-Architektur unzulässig ist, aber verständlich für die virtuelle Maschine.
  8. Die computerlesbaren Anweisungen von Anspruch 7, die zusätzlich die Verwendung mindestens einer synthetischen Anweisung umfassen, die Ausführungsprioritäten für das Host-Betriebssystem enthält.
  9. Die computerlesbaren Anweisungen von Anspruch 7, die zusätzlich Instruktionen umfassen, durch die die effizienteren Terminierungsentscheidungen von mindestens einem Steuerungsprogramm (172) im Host-Betriebssystem getroffen werden, um effektiver mindestens ein Prozessorbetriebsmittel einzusetzen.
EP05105586A 2004-06-30 2005-06-23 Vorrichtungen und Verfahren zum Ausführen eines Betriebssystems in einer virtuellen Maschine Umgebung Not-in-force EP1628214B1 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10/882,979 US20060005190A1 (en) 2004-06-30 2004-06-30 Systems and methods for implementing an operating system in a virtual machine environment

Publications (3)

Publication Number Publication Date
EP1628214A2 EP1628214A2 (de) 2006-02-22
EP1628214A3 EP1628214A3 (de) 2007-10-24
EP1628214B1 true EP1628214B1 (de) 2010-06-23

Family

ID=35457286

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05105586A Not-in-force EP1628214B1 (de) 2004-06-30 2005-06-23 Vorrichtungen und Verfahren zum Ausführen eines Betriebssystems in einer virtuellen Maschine Umgebung

Country Status (7)

Country Link
US (1) US20060005190A1 (de)
EP (1) EP1628214B1 (de)
JP (1) JP5005191B2 (de)
KR (1) KR20060046260A (de)
CN (1) CN100474240C (de)
AT (1) ATE472135T1 (de)
DE (1) DE602005021940D1 (de)

Families Citing this family (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7849327B2 (en) * 2005-01-19 2010-12-07 Leung Hin L Technique to virtualize processor input/output resources
US7363463B2 (en) * 2005-05-13 2008-04-22 Microsoft Corporation Method and system for caching address translations from multiple address spaces in virtual machines
US20060277546A1 (en) * 2005-06-02 2006-12-07 Rothman Michael A Detecting virtualization
US8909946B2 (en) 2005-11-15 2014-12-09 Microsoft Corporation Efficient power management of a system with virtual machines
US7434003B2 (en) * 2005-11-15 2008-10-07 Microsoft Corporation Efficient operating system operation on a hypervisor
EP1814028A1 (de) * 2006-01-27 2007-08-01 Siemens Aktiengesellschaft Verfahren zum Implementieren von Applikationen in unabhängigen Partitionen mit optimierten Betriebsystemen
US20070271560A1 (en) * 2006-05-18 2007-11-22 Microsoft Corporation Deploying virtual machine to host based on workload characterizations
US7725305B2 (en) * 2006-06-08 2010-05-25 Microsoft Corporation Partial virtualization on computing device
US8024727B2 (en) * 2006-06-15 2011-09-20 Microsoft Corporation Enhancing or replacing host operating system functionality by leveraging guest operating system functionality
US20070294707A1 (en) * 2006-06-15 2007-12-20 Microsoft Corporation Enhancing or replacing host operating system functionality by leveraging guest operating system functionality
US8447936B2 (en) * 2006-06-30 2013-05-21 Microsoft Corporation Module state management in a virtual machine environment
US8214828B2 (en) * 2006-06-30 2012-07-03 Microsoft Corporation Module state management in a virtual machine environment
US20080104586A1 (en) * 2006-10-27 2008-05-01 Microsoft Corporation Allowing Virtual Machine to Discover Virtual Status Thereof
US8694712B2 (en) * 2006-12-05 2014-04-08 Microsoft Corporation Reduction of operational costs of virtual TLBs
US8261284B2 (en) * 2007-09-13 2012-09-04 Microsoft Corporation Fast context switching using virtual cpus
WO2009039375A2 (en) * 2007-09-20 2009-03-26 C & S Operations, Inc. Computer system
US9116734B1 (en) * 2011-01-14 2015-08-25 Dispersive Networks Inc. Dispersive storage area networks
CN101493781B (zh) * 2008-01-24 2012-02-15 中国长城计算机深圳股份有限公司 一种虚拟机系统及其启动方法
US8539499B1 (en) * 2008-02-18 2013-09-17 Parallels IP Holdings GmbH Symmetric multiprocessing with virtual CPU and VSMP technology
US8291426B2 (en) * 2008-06-02 2012-10-16 Microsoft Corporation Memory allocators corresponding to processor resources
US9262194B2 (en) * 2008-06-10 2016-02-16 Apple Inc. Virtual machine communications
US20090319740A1 (en) * 2008-06-18 2009-12-24 Fujitsu Limited Virtual computer system, information processing device providing virtual computer system, and program thereof
US20100251250A1 (en) * 2009-03-30 2010-09-30 Microsoft Corporation Lock-free scheduler with priority support
JP5469940B2 (ja) 2009-07-13 2014-04-16 株式会社日立製作所 計算機システム、仮想計算機モニタ及び仮想計算機モニタのスケジューリング方法
JP5320440B2 (ja) * 2010-06-29 2013-10-23 サムソン エスディーエス カンパニー リミテッド クライアントハイパーバイザー基盤の端末装置及びその動作方法
JP5648544B2 (ja) 2011-03-15 2015-01-07 富士通株式会社 スケジューリングプログラム、および情報処理装置
CN102799480B (zh) * 2012-06-21 2015-06-17 华为技术有限公司 虚拟化系统中关闭中断的方法和装置
JP5941868B2 (ja) * 2013-04-18 2016-06-29 株式会社日立製作所 仮想計算機システムおよび仮想計算機におけるｉ／ｏ実施方法
JP2015210688A (ja) * 2014-04-28 2015-11-24 株式会社日立製作所 サーバ仮想化システム
US10235809B2 (en) * 2016-06-30 2019-03-19 Microsoft Technology Licensing, Llc Reality to virtual reality portal for dual presence of devices
US11054894B2 (en) 2017-05-05 2021-07-06 Microsoft Technology Licensing, Llc Integrated mixed-input system
CN109032029B (zh) * 2018-08-14 2020-12-08 北京东土科技股份有限公司 工业服务器对外通信方法、系统、装置及工业服务器
KR102327587B1 (ko) * 2020-02-14 2021-11-17 엔에이치엔 주식회사 모바일 게임 매크로 사용자 감시 방법 및 그 시스템

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1059582A2 (de) * 1999-06-03 2000-12-13 Matsushita Electric Industrial Co., Ltd. System für virtuelle Maschine

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4456954A (en) * 1981-06-15 1984-06-26 International Business Machines Corporation Virtual machine system with guest architecture emulation using hardware TLB's for plural level address translations
JPH0731609B2 (ja) * 1985-09-18 1995-04-10 日本電気株式会社 Ｖｍモード変更装置
JPS62125438A (ja) * 1985-11-27 1987-06-06 Hitachi Ltd 仮想入出力装置
JPH04213733A (ja) * 1990-12-12 1992-08-04 Nec Corp 仮想プロセッサ方式
US5548783A (en) * 1993-10-28 1996-08-20 Dell Usa, L.P. Composite drive controller including composite disk driver for supporting composite drive accesses and a pass-through driver for supporting accesses to stand-alone SCSI peripherals
US5604887A (en) * 1994-01-21 1997-02-18 Microsoft Corporation Method and system using dedicated location to share information between real and protected mode device drivers
JPH09114683A (ja) * 1995-10-16 1997-05-02 Hitachi Ltd 計算機システムの制御方法
US5790664A (en) * 1996-02-26 1998-08-04 Network Engineering Software, Inc. Automated system for management of licensed software
US5940613A (en) * 1996-05-01 1999-08-17 Sun Microsystems, Inc. Method for creating a single binary virtual device driver for a windowing operating system
JPH10232788A (ja) * 1996-12-17 1998-09-02 Fujitsu Ltd 信号処理装置及びソフトウェア
US6075938A (en) * 1997-06-10 2000-06-13 The Board Of Trustees Of The Leland Stanford Junior University Virtual machine monitors for scalable multiprocessors
US6056786A (en) * 1997-07-11 2000-05-02 International Business Machines Corp. Technique for monitoring for license compliance for client-server software
US6086628A (en) * 1998-02-17 2000-07-11 Lucent Technologies Inc. Power-related hardware-software co-synthesis of heterogeneous distributed embedded systems
US6496847B1 (en) * 1998-05-15 2002-12-17 Vmware, Inc. System and method for virtualizing computer systems
US6397242B1 (en) * 1998-05-15 2002-05-28 Vmware, Inc. Virtualization system including a virtual machine monitor for a computer with a segmented architecture
GB9825102D0 (en) * 1998-11-16 1999-01-13 Insignia Solutions Plc Computer system
US6324578B1 (en) * 1998-12-14 2001-11-27 International Business Machines Corporation Methods, systems and computer program products for management of configurable application programs on a network
US6785894B1 (en) * 1999-04-09 2004-08-31 Sun Microsystems, Inc. Virtual device driver
US6658657B1 (en) * 2000-03-31 2003-12-02 Intel Corporation Method and apparatus for reducing the overhead of virtual method invocations
US7146305B2 (en) * 2000-10-24 2006-12-05 Vcis, Inc. Analytical virtual machine
US7308717B2 (en) * 2001-02-23 2007-12-11 International Business Machines Corporation System and method for supporting digital rights management in an enhanced Java™ 2 runtime environment
US6980946B2 (en) * 2001-03-15 2005-12-27 Microsoft Corporation Method for hybrid processing of software instructions of an emulated computer system
US7272831B2 (en) * 2001-03-30 2007-09-18 Intel Corporation Method and apparatus for constructing host processor soft devices independent of the host processor operating system
US7191440B2 (en) * 2001-08-15 2007-03-13 Intel Corporation Tracking operating system process and thread execution and virtual machine execution in hardware or in a virtual machine monitor
US20030061401A1 (en) * 2001-09-25 2003-03-27 Luciani Luis E. Input device virtualization with a programmable logic device of a server
US7103529B2 (en) * 2001-09-27 2006-09-05 Intel Corporation Method for providing system integrity and legacy environment emulation
JP2003256234A (ja) * 2002-03-05 2003-09-10 Communication Research Laboratory 抗脆弱性サーバ装置及びソフトウェア
US20030187908A1 (en) * 2002-03-26 2003-10-02 Sun Microsystems, Inc. Methods and systems for customer based resource priority control
US7127548B2 (en) * 2002-04-16 2006-10-24 Intel Corporation Control register access virtualization performance improvement in the virtual-machine architecture
US7210144B2 (en) * 2002-08-02 2007-04-24 Microsoft Corporation Method for monitoring and emulating privileged instructions of programs in a virtual machine
US7313512B1 (en) * 2002-10-18 2007-12-25 Microsoft Corporation Software license enforcement mechanism for an emulated computing environment
US7181744B2 (en) * 2002-10-24 2007-02-20 International Business Machines Corporation System and method for transferring data between virtual machines or other computer entities
US20050076186A1 (en) * 2003-10-03 2005-04-07 Microsoft Corporation Systems and methods for improving the x86 architecture for processor virtualization, and software systems and methods for utilizing the improvements
US7552426B2 (en) * 2003-10-14 2009-06-23 Microsoft Corporation Systems and methods for using synthetic instructions in a virtual machine
US7558723B2 (en) * 2003-12-12 2009-07-07 Microsoft Corporation Systems and methods for bimodal device virtualization of actual and idealized hardware-based devices
US7590982B1 (en) * 2003-12-17 2009-09-15 Vmware, Inc. System and method for virtualizing processor and interrupt priorities
US7877747B2 (en) * 2004-02-20 2011-01-25 Hewlett-Packard Development Company, L.P. Flexible operating system operable as either native or as virtualized

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1059582A2 (de) * 1999-06-03 2000-12-13 Matsushita Electric Industrial Co., Ltd. System für virtuelle Maschine

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MAGENHEIMER D ET AL: "vBlades: Optimized Paravirtualization for the Itanium Processor Family", PROCEEDINGS OF THE THIRD VIRTUAL MACHINE RESEARCH AND TECHNOLOGY SYMPOSIUM, 6 May 2004 (2004-05-06), San Jose, CA, USA, pages 1 - 11 *

Also Published As

Publication number Publication date
EP1628214A2 (de) 2006-02-22
CN100474240C (zh) 2009-04-01
JP5005191B2 (ja) 2012-08-22
ATE472135T1 (de) 2010-07-15
US20060005190A1 (en) 2006-01-05
DE602005021940D1 (de) 2010-08-05
EP1628214A3 (de) 2007-10-24
JP2006018820A (ja) 2006-01-19
KR20060046260A (ko) 2006-05-17
CN1716193A (zh) 2006-01-04

Similar Documents

Publication Publication Date Title
EP1628214B1 (de) Vorrichtungen und Verfahren zum Ausführen eines Betriebssystems in einer virtuellen Maschine Umgebung
EP1622014B1 (de) Systeme und Verfahren zur Initialisierung von mehreren virtuellen Prozessoren in einer einzigen virtuellen Maschine
US7555596B2 (en) Systems and methods for attaching a virtual machine virtual hard disk to a host machine
US8972991B2 (en) Systems and methods for exposing processor topology for virtual machines
US7580826B2 (en) Systems and methods for development of emulated devices in a virtual machine environment
US9619270B2 (en) Remote-direct-memory-access-based virtual machine live migration
US10162658B2 (en) Virtual processor allocation techniques
US7689747B2 (en) Systems and methods for an augmented interrupt controller and synthetic interrupt sources
EP2485146B1 (de) System und Verfahren zur Bereitstellung von Hardware-Virtualisierungen in einer virtuellen Maschinenumgebung
US20060005186A1 (en) Systems and methods for stack-jumping between a virtual machine and a host environment
US20120054740A1 (en) Techniques For Selectively Enabling Or Disabling Virtual Devices In Virtual Environments
US8539499B1 (en) Symmetric multiprocessing with virtual CPU and VSMP technology
US20180157519A1 (en) Consolidation of idle virtual machines
JP2006252565A (ja) 仮想マシン環境におけるマルチレベルインターセプト処理のためのシステムおよび方法
US20230127141A1 (en) Microservice scheduling
RU2543962C2 (ru) Аппаратно-вычилистельный комплекс виртуализации и управления ресурсами в среде облачных вычислений
Lin et al. Improving GPOS real-time responsiveness using vCPU migration in an embedded multicore virtualization platform

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR LV MK YU

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR LV MK YU

17P Request for examination filed

Effective date: 20071116

17Q First examination report despatched

Effective date: 20080201

AKX Designation fees paid

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 602005021940

Country of ref document: DE

Date of ref document: 20100805

Kind code of ref document: P

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20100623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

LTIE Lt: invalidation of european patent or patent extension

Effective date: 20100623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100924

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100630

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20101023

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20101025

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100623

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100630

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100630

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20110324

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602005021940

Country of ref document: DE

Effective date: 20110323

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20101224

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100923

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20101004

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602005021940

Country of ref document: DE

Representative=s name: GRUENECKER, KINKELDEY, STOCKMAIR & SCHWANHAEUS, DE

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20150115 AND 20150121

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602005021940

Country of ref document: DE

Representative=s name: GRUENECKER PATENT- UND RECHTSANWAELTE PARTG MB, DE

Effective date: 20150126

Ref country code: DE

Ref legal event code: R081

Ref document number: 602005021940

Country of ref document: DE

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, REDMOND, US

Free format text: FORMER OWNER: MICROSOFT CORP., REDMOND, WASH., US

Effective date: 20150126

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, US

Effective date: 20150724

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20160614

Year of fee payment: 12

Ref country code: GB

Payment date: 20160622

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20170511

Year of fee payment: 13

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602005021940

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20170623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180103

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170623

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180630