DE102015209125A1 - Method and apparatus for operating a guest through a hypervisor - Google Patents

Abstract

A method (10) for operating a guest system by a hypervisor (12), characterized by the following features: - a startup (14) of the hypervisor (12), - a mandatory hardware initialization (16) by the hypervisor (12) before a startup (18 ) of the guest system and - an optional hardware initialization (20) by the hypervisor (12) after startup (18).

Description

The present invention relates to a method for operating a guest system through a hypervisor. The present invention also relates to a corresponding device, a corresponding computer program and a corresponding storage medium.

State of the art

A class of systems of practical computer science, which serves as an abstracting layer between actually existing hardware and other systems to be installed, is known to those skilled in the art as hypervisors (virtual machine monitor, VMM). Generic hypervisors make it possible to define a virtual environment with hardware resources such as processor, memory, disk space and peripherals, which serves as the basis for the installation of guest systems, regardless of the actual hardware.

Hypervisors of the prior art allow the simultaneous operation of multiple guest systems on a common hardware. In this case, the hypervisor manages the resource allocation for individual guest systems. It distributes the hardware resources such that each resource is available on demand for each guest operating system.

DE 102012205301 A1 discloses a computer architecture for controlling electronic data processing in a vehicle having a computing device for performing electronic data processing, at least two virtual machines, wherein a first of the virtual machines comprises a first operating system and a second of the virtual machines comprises a second operating system, and a virtualization layer , which is designed so that the first and second operating systems can be operated in parallel on the computing device, wherein the second operating system optionally meets a higher security requirement than the first operating system.

Disclosure of the invention

The invention provides a method for operating a guest system by a hypervisor, a corresponding device, a corresponding computer program and a corresponding storage medium according to the independent claims.

An advantage of this solution lies in the fact that the hypervisor performs only the essentials of initialization tasks, such as central processing unit (CPU) and memory management. The proposed approach thus reduces the additional startup time caused by the hypervisor, which is a critical quality criterion, especially in automotive engineering. The remaining initialization steps are performed step by step in cooperation with the guest system.

The measures listed in the dependent claims advantageous refinements and improvements of the independent claim basic idea are possible.

Brief description of the drawings

Embodiments of the invention are illustrated in the drawings and explained in more detail in the following description. It shows:

1 the system behavior of a hypervisor according to a first embodiment.

2 schematically a control device according to a second embodiment.

Embodiments of the invention

1 illustrates the fast and flexible startup behavior of a hypervisor 12 according to an embodiment of the invention. Here is a list of hardware devices and their device properties 24 . 26 provided that can be set up at a later date. This list is usually system-specific.

In the configuration 22 of the hypervisor 12 The user specifies which of these device properties 24 . 26 Subject of mandatory hardware initialization 16 should be. It also indicates which device properties 24 . 26 on request 28 a guest of optional hardware initialization 20 should be subjected. For each device property 26 In doing so, certain guest systems can be demanded 28 their optional hardware initialization 20 entitle.

The hypervisor 12 is now using a code generation 30 including the configuration 22 built.

Each time you turn on the power 32 of the system takes place after starting 34 the hardware booting up 14 of the hypervisor. This then takes before commissioning 18 the guest systems the obligatory hardware initialization 16 in front.

After commissioning 18 Of the guest systems, these may be the hardware device properties 24 use that they need. If a guest intends to install an uninitialized hardware device property 26 To use it, it requires their optional hardware initialization 20 through the hypervisor 12 at. It does this by setting up a dedicated request 28 to the hypervisor service application programming interface (VSA). If the request 28 in the configuration 22 was approved, the hypervisor takes 12 the optional hardware initialization 20 in front. After that, the guest system may have the hardware device property 26 use as needed. An unauthorized request 28 while calling for a reasonable error response from the hypervisor 12 out.

A typical configuration involving optional hardware initialization 20 is appropriate, is when a peripheral device such as a common CAN controller is shared between guest systems. Here it is expedient that the hypervisor 12 virtualize the peripheral appropriately. For this purpose, the hypervisor operates 12 its own driver, which is the device of an optional hardware initialization 20 and provides the guest systems with a programming interface to access the device.

This method 10 For example, in software or hardware or in a hybrid of software and hardware, for example, in a control unit 20 be implemented as the schematic representation of 2 clarified.

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited patent literature

• DE 102012205301 A1 [0004]

Claims (10)

Procedure ( 10 ) for operating a guest through a hypervisor ( 12 ), characterized by the following steps: - a startup ( 14 ) of the hypervisor ( 12 ), - a mandatory hardware initialization ( 16 ) through the hypervisor ( 12 ) before commissioning ( 18 ) of the guest system and - an optional hardware initialisation ( 20 ) through the hypervisor ( 12 ) after commissioning ( 18 ). Procedure ( 10 ) according to claim 1, characterized in that the hardware initializations ( 16 . 20 ) depending on a configuration ( 22 ) of the hypervisor ( 12 ) respectively. Procedure ( 10 ) according to claim 2, characterized by the following features: - the configuration ( 22 ) determines at least one mandatory device property ( 24 ) and - the obligatory hardware initialization ( 16 ) concerns the compulsory equipment characteristic ( 24 ). Procedure ( 10 ) according to claim 2 or 3, characterized by the following features: - the configuration ( 22 ) determines at least one optional device property ( 26 ) and - the optional hardware initialization ( 20 ) concerns the optional device characteristic ( 26 ). Procedure ( 10 ) according to claim 4, characterized in that the optional hardware initialisation ( 20 ) on a request ( 28 ) by the guest system. Procedure ( 10 ) according to claim 5, characterized by the following features: - the guest system is one of several guest systems and - the configuration ( 22 ) authorizes the guest system to the request ( 28 ). Procedure ( 10 ) according to one of claims 1 to 6, characterized by the following features: - the configuration ( 22 ) is a code generation ( 30 ) and - code generation ( 30 ) returns the hypervisor ( 12 ). Computer program, which is set up the procedure ( 10 ) according to one of claims 1 to 7. Machine-readable storage medium on which the computer program according to claim 8 is stored. Contraption ( 20 ), which is set up, the procedure ( 10 ) according to one of claims 1 to 7.

Images