Boot Configuration Data Structure for Guest OS Initialization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face challenges in loading programs during system boot using stored configuration data, as BIOS is independent of operating systems and lacks access to logical block addresses of non-operating system programs, leading to difficulties in determining the reliable location of dynamic configuration data, especially for guest operating systems that may lack file system resource access.
Innovation Solution
A method and apparatus that utilize a computer system with a predetermined file system of a host operating system to store and provide configuration data to guest operating systems, involving a table of contents, non-volatile solid state memory, and a bootstrap loader to initialize and copy data into the guest operating system's memory, ensuring separation of configuration data and reducing single points of failure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If BIOS is used as an independent booting mechanism, then BIOS can be utilized in a single location as the starting point, but the logical block addresses of non-operating system programs are known only to the operating system and not to the BIOS, restricting the loading of programs from disk during boot
Solution Approach 1:
The patent introduces a configuration data structure as an intermediary mechanism that bridges BIOS and operating system programs. This configuration data structure stores logical block address information and enables BIOS to access and load programs from disk during boot, resolving the limitation where BIOS could not know the LBA addresses of non-operating system programs.
2Ease of operation
If configuration data is stored with the application program or centrally stored, then configuration data can be accessed, but a single point of failure possibility exists where registry conflicts may cause setting information and configuration data for every program in the environment
Solution Approach 1:
The patent segments configuration data into separate structures that are independently stored and managed. Each program's configuration data is stored in its own dedicated configuration data structure, isolating it from other programs' configuration data. This segmentation eliminates the single point of failure risk where registry conflicts could affect all programs simultaneously.
3Ease of manufacture
If configuration data is stored using a file system on HDD, then configuration data can be stored, but guest operating environments often lack the file system resource access or resource itself
Solution Approach 1:
The patent introduces a configuration data structure as an intermediary that operates independently of the file system. This configuration data structure can be accessed by guest operating systems without requiring them to have file system resource access or a traditional file system installed, enabling configuration storage and retrieval across diverse guest OS environments.
4Reliability
If bootstrap application programs are moved to non-volatile BIOS memory, then programs can be stored permanently, but the applications cannot be booted from disk due to their size and the need to load them prior to initiating a system boot
Solution Approach 1:
The patent segments the bootstrap application programs into smaller components that can be stored in non-volatile BIOS memory while maintaining the ability to boot from disk. The configuration data structure stores references to these segmented programs, allowing the system to load only the necessary portions from disk during boot, resolving the conflict between permanent storage and booting capability.
Data Source
AI summary
A system and method for loading programs during a system boot using stored configuration data in a predetermined file system from a prior session and providing the stored configuration data to a guest operating system capable of communication with a host operating system, during start-up, within a computing environment having a hypervisor, in a predetermined manner.