Virtual Storage Partition Mapping for Multi-Boot Guest OSes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional operating system architectures limit virtual server instances to a single boot disk, which is incompatible with cloud computing environments, especially for non-standard operating systems like z/OS that require multiple disk images for booting, and hypervisors struggle to scale with this volume of unique boot virtual storage disks.
Innovation Solution
A hypervisor-based architecture that organizes a storage pool of virtual storage blocks into multiple virtual storage partition tables, assigns device addresses, and presents them to the guest operating system, allowing multiple disk images to be managed as a single virtual storage device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single boot disk is used in conventional operating system architecture, then device complexity is reduced, but adaptability to cloud computing environments and non-standard operating systems deteriorates
Solution Approach 1:
The patent segments the storage device into multiple virtual storage partitions, each with its own partition table and device address. This allows a single physical storage device to present multiple logical boot disks to different operating systems, resolving the contradiction between adaptability and complexity by organizing storage into manageable segments rather than requiring separate physical devices for each OS
Solution Approach 2:
The patent creates a universal storage device that can serve multiple functions simultaneously - it can boot different operating systems (conventional OSes, z/OS, cloud computing OSes) using the same physical storage infrastructure. The hypervisor layer provides multi-functionality by presenting different virtual storage partitions to different guest OSes, eliminating the need for separate boot disks for each OS type
2Adaptability or versatility
If multiple disk images are presented to guest operating systems, then adaptability to non-standard operating systems like z/OS is improved, but device complexity and hypervisor scaling requirements worsen
Solution Approach 1:
The hypervisor acts as an intermediary layer between the physical storage device and the guest operating systems. It manages the complexity of multiple disk images by presenting them through standardized virtual storage partitions with device addresses. This mediator approach allows support for non-standard OSes like z/OS without increasing the complexity at the guest OS level, as the hypervisor handles the complex partition management centrally
3Adaptability or versatility
If a one-to-one mapping between hypervisor storage disks and guest OS disks is used, then ease of operation is improved, but adaptability to multiple boot disks deteriorates
Solution Approach 1:
The patent introduces a new dimension of abstraction by mapping physical storage blocks to virtual storage partitions through partition tables, rather than directly mapping physical disks to guest OS disks. This dimensional change allows multiple boot disks to be presented to a single virtual machine while maintaining ease of operation through standardized device address mapping, resolving the contradiction between adaptability and operational simplicity
Data Source
AI summary
An architecture for demultiplexing volumes in a storage device includes a virtual machine. A guest operating system is in the virtual machine. The architecture further includes a storage pool of virtual storage blocks and a hypervisor. The hypervisor is configured to organize the storge pool of virtual storage blocks into a plurality of virtual storage partition tables. Device addresses are assigned to the plurality of virtual storage partition tables. The plurality of virtual storage partition tables and the devices addresses are organized into a virtual storage device. The device addresses are presented to the guest operating system in the virtual machine.