Implementation method of localized operating system VOI desktop

Abstract

The invention provides an implementation method of a localized operating system VOI desktop, which is implemented by customizing Linux system startup logic in combination with an OverlayFS technology and a virtual disk technology. The method comprises the steps that an operating system mirror image is manufactured, an operating system is installed in a virtual disk, a kernel mirror image is modified, and kernel mounting root partition logic is redefined; deploying a virtual desktop, managing a mirror image file on a server side, distributing the mirror image file to a terminal and creating an independent desktop file; and when the desktop is started, the kernel system is guided through the guide program, the OverlayFS is mounted in the kernel system by using the virtual disk according to a predefined rule, and the root partition is switched. According to the invention, a high-performance virtual desktop environment is realized, multi-system coexistence and rapid switching are supported, the hardware compatibility is good, the system performance loss is less than 3% through testing, and the storage space is saved by more than 60%.

Description

Technical Field

[0001] The present invention relates to the technical field of operating system virtualization, and in particular to a method for implementing a localized operating system VOI desktop based on OverlayFS technology. Background Art

[0002] With the development of information technology, virtualized desktop technology has been widely used in enterprise office environments. Currently, virtualized desktops in domestic operating systems (Linux kernel) are mainly implemented based on Docker container technology or virtual machines (IDV desktops).

[0003] Existing Docker-based virtual desktops have the following problems:

[0004] 1. Insufficient isolation:

[0005] All containers share some runtime libraries and the host OS kernel.

[0006] Network isolation is only achieved through namespace, which is less secure.

[0007] User data isolation relies on Docker's storage driver, which is not reliable enough.

[0008] Measured data shows that under high load conditions, resource contention between containers is severe, and performance fluctuations can reach more than 30%.

[0009] 2. Deployment restrictions:

[0010] It is impossible to deploy and switch simultaneously with Windows desktop or other domestic operating systems with different kernel versions

[0011] All containers must use the same kernel version.

[0012] After testing, different versions of domestic operating systems (such as UOS and Kylin) cannot run in parallel on the same physical machine.

[0013] System updates require rebuilding the entire container, making the upgrade process time-consuming and error-prone. However, virtual desktops based on virtual machines (IDV desktops) have the following issues:

[0014] 1. High hardware requirements:

[0015] CPU requirements: Must support hardware virtualization (IntelVT-x / AMD-V)

[0016] Memory requirements: Each virtual machine requires at least 4GB of dedicated memory

[0017] Graphics card requirements: Need to support virtualization pass-through technology

[0018] In actual deployment, the terminal configuration must be more than 50% higher than that of an ordinary PC. 2. Large performance loss:

[0019] CPU virtualization overhead: 15-20% performance loss

[0020] Memory virtualization overhead: consumes an additional 20-30% of physical memory

[0021] I / O operation latency: 30-40% higher than that of physical machines

[0022] Graphics performance degradation: 25-35% frame rate reduction

[0023] The existing technical solutions generally have the following common problems:

[0024] 1. Difficulty maintaining high performance while ensuring isolation

[0025] 2. Unable to achieve flexible switching between different versions of operating systems

[0026] 3. High system update and maintenance costs

[0027] 4. Terminal deployment requirements are stringent

[0028] Therefore, a new technical solution is needed to solve the above problems and realize a domestic operating system virtual desktop environment that is safe, reliable, high-performance and flexible to deploy. Summary of the Invention

[0029] The purpose of the present invention is to provide a method for implementing a domestic operating system VOI desktop, aiming to solve technical problems existing in the prior art such as insufficient isolation, deployment restrictions, high hardware requirements and large performance loss.

[0030] Technical Solution

[0031] To achieve the above objectives, the present invention provides the following technical solutions:

[0032] A method for implementing a domestic operating system VOI desktop includes the following steps:

[0033] 1. Create an operating system image:

[0034] Mount a virtual disk on the terminal and install the operating system to the virtual disk, wherein the virtual disk may be in a VHD or qcow2 format, but is not limited to the format;

[0035] Enter the operating system to modify the kernel image (initrd.img) and redefine the kernel mounting root partition logic;

[0036] like Figure 1As shown in the file system mapping diagram, configure the OverlayFS mapping rules to map the Lower layer to the operating system image file, the Upper layer to the desktop file, and the merged layer to the physical disk desktop file.

[0037] The Work layer is mapped to the system temporary folder and serves as the temporary workspace of OverlayFS to process file modification operations and ensure data consistency.

[0038] 2. Deploy domestic virtual desktops, such as Figure 2 The desktop deployment diagram is as follows:

[0039] Manage image files on the server side, including layered image files and image incremental modification files;

[0040] Distribute the image file to the terminal and create an independent desktop file on the terminal;

[0041] Maintain the correspondence between desktop files and images;

[0042] Configure the grub startup item for each desktop, specifying the corresponding kernel file, image virtual disk file, and desktop virtual disk file.

[0043] 3. Start the desktop, such as Figure 3 The system startup steps are shown in the flowchart:

[0044] When the terminal system starts, select the desktop system configured in the grub menu;

[0045] Boot the desktop system through the boot program and pass the startup parameters to the kernel system;

[0046] Start the desktop kernel temporary file system;

[0047] Use the specified virtual disk to mount OverlayFS according to predefined rules;

[0048] Switch the root partition to OverlayFS and start the desktop system in OverlayFS.

[0049] Beneficial effects

[0050] The present invention has the following beneficial effects:

[0051] 1. Provides better isolation:

[0052] The OverlayFS technology achieves file system-level isolation, avoiding the isolation issues in traditional Docker solutions.

[0053] Each desktop environment has its own independent Upper layer storage space, with 100% data isolation.

[0054] Supports independent user space, and the processes of different desktop environments are completely isolated. After testing, even under high load conditions, the performance fluctuation of each desktop environment does not exceed 5%.

[0055] 2. Support multi-system deployment:

[0056] Different types of operating system desktops can be deployed simultaneously, and flexible switching is supported.

[0057] Change

[0058] Supports coexistence of different versions of domestic operating systems such as UOS and Kylin. There is no extra consumption in system switching time, and the user experience is close to the native system restart.

[0059] Switch

[0060] Supports co-existence of up to 10 different operating system versions. 3. Reduced hardware requirements:

[0061] Compared with the IDV solution, the terminal hardware requirements are reduced by more than 50%

[0062] Minimum system requirements:

[0063] CPU: Supports AMD64 architecture and ARM64 architecture, without hardware virtualization support

[0064] Memory: consistent with native operating system requirements

[0065] Storage: 10GB for the base system, with 2-3GB of incremental storage for each desktop environment

[0066] The adaptability range has been expanded, and it can be deployed on more than 90% of existing terminal devices. 4. Improved performance:

[0067] Directly utilize local hardware resources to avoid performance loss caused by virtualization

[0068] Compared with physical machine performance:

[0069] CPU performance loss: less than 3%

[0070] Memory access latency: Increase by no more than 3%

[0071] Disk I / O performance: close to native speed (more than 90%)

[0072] Graphics performance: over 98% of native performance

[0073] System startup time is shortened by more than 60% compared with the IDV solution

[0074] 5. Simplify management and maintenance:

[0075] Through the layered file system technology, unified management and rapid update of system images are achieved

[0076] Update efficiency improvement:

[0077] System update time reduced by 80%

[0078] Incremental update package size reduced by 70%

[0079] The rollback operation time does not exceed 5 seconds

[0080] Batch deployment efficiency:

[0081] Deployment time for 100 terminals is less than 30 minutes

[0082] The number of concurrent updates supported has been increased to over 500 devices.

[0083] Network bandwidth usage reduced by 65%

[0084] 6. Save storage space:

[0085] Using tiered storage technology, multiple desktops share the basic system layer

[0086] Storage space saving:

[0087] Save 60-70% storage space compared to traditional solutions

[0088] The total storage usage of the 10 desktop environments does not exceed 50GB, and the average size of the incremental update package is less than 100MB.

[0089] 7. Improved security:

[0090] Based on read-only system image, it prevents system files from being tampered with. Desktop environments are completely isolated to avoid cross infection.

[0091] Supports regular automatic restoration function to ensure system security BRIEF DESCRIPTION OF THE DRAWINGS

[0092] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0093] Figure 1 This is a file system mapping diagram of the present invention, showing the layered file system architecture based on OverlayFS.

[0094] 101 represents the Lower layer, which is used to map the operating system base image file and is a read-only layer;

[0095] 102 represents the Upper layer, which is used to map desktop personalized files and is a writable layer that stores user modifications.

[0096] 103 represents the Merged layer, which provides a unified file system view and combines the contents of the Lower and Upper layers for display to the user.

[0097] 104 represents the Work layer, which serves as the temporary workspace of OverlayFS and is used to process file modification operations and ensure data consistency.

[0098] 105 indicates a virtual disk file, which can be in VHD or qcow2 format;

[0099] 106 indicates a layered image file, which supports multi-level mapping relationships:

[0100] 106-1 represents the basic operating system layer

[0101] 106-2 indicates the application layer

[0102] 106-3 indicates the patch update layer

[0103] Figure 2 This is a schematic diagram of the desktop deployment of the present invention, showing the complete deployment architecture from server to terminal.

[0104] 201 represents the server-side image management center, which is used to centrally manage multiple system images and update packages;

[0105] 202 represents the image distribution channel, which supports on-demand distribution and incremental updates;

[0106] 203 represents a terminal device used to run a multi-system desktop environment;

[0107] 204 represents the local image storage (Lower layer), which stores multiple read-only system base images;

[0108] 205 represents a desktop configuration database, which maintains multiple sets of desktop configurations and their corresponding images and data relationships;

[0109] 206 indicates grub multi-boot configuration, which supports fast switching between multiple systems;

[0110] 207 represents the desktop file (Upper layer), which independently stores user data and modified content for each system, including personal configuration and application data.

[0111] This deployment architecture enables:

[0112] 1. Centralized management and distribution of multiple system images

[0113] 2. Separate storage of system image and user data

[0114] 3. Independent configuration of multiple desktop environments

[0115] 4. Flexible system switching mechanism

[0116] Figure 3 This is a flow chart of the system startup steps of the present invention.

[0117] 301 indicates the initial stage of system startup;

[0118] 302 indicates the grub boot phase;

[0119] 303 indicates the kernel loading stage;

[0120] 304 indicates the temporary file system startup phase;

[0121] 305 indicates the OverlayFS mounting stage;

[0122] 306 indicates the root file system switching stage;

[0123] 307 indicates the desktop system startup phase.

[0124] The above figures clearly illustrate the implementation process of the technical solution of the present invention, including the file system organization structure, deployment architecture, and the complete system startup process. The various components and steps in the figures work together to achieve an efficient and flexible domestic operating system VOI desktop solution. DETAILED DESCRIPTION

[0125] The specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0126] Example 1: Basic implementation

[0127] A specific implementation of the present invention includes the following specific steps:

[0128] 1. Operating system image creation

[0129] 1.1 Image Preparation

[0130] Create a virtual disk file in VHD format. The size is set according to actual needs, with a typical value of 20GB.

[0131] Install a domestic operating system (such as Tongxin UOS or Kylin KOS) into the virtual disk;

[0132] Complete basic environment configuration, including driver installation and necessary system optimization.

[0133] 1.2 Kernel Customization

[0134] Modify the initrd.img file, add OverlayFS and virtual disk support modules; configure kernel startup parameters, add the overlayfs.conf configuration file, and define the following mapping rules:

[0135] Lower layer: points to the base operating system image file path

[0136] Upper layer: points to the personal desktop data storage path

[0137] Merged layer: points to the / overlay directory as the final unified view

[0138] Work layer: points to the temporary working directory

[0139] 2. Virtual desktop deployment process, such as Figure 2 Desktop deployment diagram

[0140] 2.1 Server-side Configuration

[0141] Establish an image management center to store basic images and incremental update packages;

[0142] Implement an image version control system to support image rollback and updates;

[0143] Configure image distribution strategies to support on-demand distribution and incremental updates.

[0144] 2.2 Terminal Deployment

[0145] Create a dedicated partition on the terminal's local hard disk to store image files;

[0146] Create a desktop configuration database to record the following information:

[0147] Desktop ID, corresponding image version, personal data storage location, startup configuration parameters

[0148] Generate a separate grub boot configuration for each desktop, including:

[0149] Kernel Path

[0150] initrd.img path

[0151] Root file system parameters

[0152] OverlayFS Configuration Parameters

[0153] 3. Desktop startup process, such as Figure 3 The system startup steps are shown in the flowchart

[0154] 3.1 Pre-boot stage BIOS / UEFI boots to the grub menu;

[0155] The user selects the desktop environment to be started;

[0156] grub loads the specified kernel and initrd.img.

[0157] 3.2 System startup phase

[0158] Mount the temporary root file system;

[0159] Mount necessary devices and file systems;

[0160] Check and mount the OverlayFS layers:

[0161] Mount the Lower layer system image in read-only mode

[0162] Mount Upper layer personal data in read-write mode

[0163] Create a Work directory for OverlayFS operations to perform root file system switching (pivot_root / switch_root);

[0164] Start system services and desktop environment.

[0165] Example 2: Multi-layer mirroring support, such as Figure 1 The file system mapping diagram shows that this embodiment adds support for multi-layer mirroring based on the basic implementation method: 1. The lower layer supports multi-level configuration, which can include the following in order from bottom to top:

[0166] Basic operating system layer (L0)

[0167] Common Application Layer (L1)

[0168] Department customization layer (L2)

[0169] Security Patch Layer (L3)

[0170] 2. The image hierarchy is defined through the configuration file:

[0171] [overlay]

[0172] lower_dirs= / path / to / L0: / path / to / L1: / path / to / L2: / path / to / L3upper_dir= / path / to / personal

[0173] merged_dir= / overlay

[0174] work_dir= / overlay-work

[0175] Example 3: Incremental update mechanism

[0176] This embodiment implements the incremental update mechanism of the system:

[0177] 1. Update package production

[0178] Create a difference file based on the base image

[0179] Generate an update description file containing version information and dependencies

[0180] 2. Update deployment

[0181] Server distribution incremental update package

[0182] Terminal merge update content

[0183] Automatically update grub configuration

[0184] 3. Update rollback

[0185] Save update history

[0186] Support quick rollback to previous version

[0187] Although the preferred embodiments of the present disclosure have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present disclosure.

[0188] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.

Claims

1. A method for implementing a VOI desktop in a localized operating system, characterized in that: The following steps are involved: Create an operating system image: Mounting a virtual disk on a terminal and installing an operating system into the virtual disk; Modify the kernel image, redefine the kernel mounting root partition logic, and configure OverlayFS mapping rules; Map the Lower layer to the operating system image file, the Upper layer to the desktop file, and the Merged layer to the physical disk desktop folder; Deploy virtual desktops: Manage image files on the server side, including layered image files and image incremental modification files; Distribute the image file to the terminal and create an independent desktop file on the terminal; Maintain the correspondence between desktop files and images; Configure startup items for each desktop; Launch the desktop: Start the desktop system through the boot program; Start the desktop kernel temporary file system; Use virtual disks to mount OverlayFS according to predefined rules; Switch the root partition to OverlayFS and start the desktop system.

2. The implementation method according to claim 1, characterized in that: The virtual disk adopts a virtual disk format that supports read-write separation.

3. The implementation method according to claim 1, characterized in that: The Lower Layers support multi-level mapping, including: Base operating system layer; Application layer; Patch update layer.

4. The implementation method according to claim 1, characterized in that: In the steps of deploying virtual desktops: Supports simultaneous deployment of multiple different operating system desktop images on the same terminal device; Each desktop system has an independent Upper layer storage space for storing user data and modified content.

5. The implementation method according to claim 1, characterized in that: The OverlayFS mounting and root partition switching in the desktop startup step include: Load the OverlayFS module in the kernel temporary file system; Mount each layer of file system according to predefined mapping rules; Prepare a new root file system environment; Perform root file system switching operations; Release temporary file system resources.

6. The implementation method according to claim 1, characterized in that: The server-side image management includes: Base image version control; Incremental update package management; Distribute policy configuration on demand.

7. The implementation method according to claim 1, characterized in that: It also includes multi-system switching steps: Save the current system operation status; Load the mapping configuration of the target system; Performs a fast switching operation.

Images