Method and system for repairing virtual simulation blue screen of disk mirror image, terminal and medium
By creating a KVM virtual machine and using the power-on self-start program in the Windows PE boot tool disk, the problem of blue screen failure in disk mirror virtual simulation is solved, and forensics efficiency and accuracy is improved. It is suitable for a variety of operating systems and hardware platforms. It supports Development of domestic technology.
Patent Information
- Application Number
- CN202411228654.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-03
- Publication Date
- 2024-11-26
AI Technical Summary
In computer forensics, blue screen failures are often caused during disk mirror virtual simulation due to incompatibility of hard drives or inconsistent hardware environment and system configuration, especially in operating system versions before Win10. The lack of effective repair methods leads to forensic efficiency and accuracy. Sexual limitation.
By obtaining the forensic disk image file of the target operating system, creating a KVM virtual machine, and using a pre-made Windows PE boot tool disk, combined with the power-on self-start program in the ISO image file, repairing the blue screen failure during virtual simulation. The specific steps include mounting disk image files, statically parsing disk partition tables, generating virtual machine configuration files, converting image file formats, setting boot file paths, injecting IDE drivers and modifying disk interface types to suit different operating system versions.
It realizes cross-platform virtual machine compatibility and flexibility, effectively solves the problem of booting blue screen in the operating system before Windows 10, improves the efficiency and accuracy of electronic evidence for evidence collection, and ensures the integrity and security of the evidence collection process. Support the popularization of domestic operating systems and CPU chips.
Smart Images

Figure CN119025323A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the technical field of computer forensics and relates to a method, system, terminal and medium for repairing a disk image virtual simulation blue screen. Background Art
[0002] In the field of computer forensics, the identification, collection, protection, analysis, archiving and presentation of electronic evidence in court are key steps. Electronic evidence, also known as computer evidence, is mainly stored in digital form in various storage media, such as hard disks, optical disks, RAM and USB flash drives. In order to ensure the authenticity and validity of electronic evidence, it is usually necessary to adopt strict operating specifications to perform a bit-for-bit backup of the original evidence medium to form a complete copy, and use image simulation technology to simulate the operating environment and status of the target operating system for intuitive forensic analysis.
[0003] Image simulation technology enables forensic personnel to analyze image files by combining static analysis and dynamic analysis. Although static analysis can provide certain information, it often cannot parse out all the clues that forensic personnel are concerned about. Dynamic analysis can generate a bootable virtual machine system to help forensic personnel to examine and operate the target operating system in an interactive way. This method is not only simple and intuitive, but also has obvious advantages in scenarios such as website reconstruction or database service recovery.
[0004] However, in actual operation, image emulation usually requires a complete copy or deployment of the target operating system, which requires extremely high accuracy and integrity. If any driver or file is missing, the virtual machine system may not be able to start. For example, due to incompatible hard disk drives or inconsistent hardware environment and system configuration, a blue screen problem may occur when the virtual machine is turned on. This situation is particularly common in operating system versions before Win10.
[0005] Therefore, how to provide a method, system, terminal and medium for repairing the blue screen of disk image virtual simulation is crucial for repairing the blue screen failure that occurs during virtual simulation of forensic disk image. This is a technical problem that technicians urgently need to solve. Summary of the invention
[0006] The purpose of the present application is to provide a method, system, terminal and medium for repairing a blue screen of a disk image virtual simulation, which are used to repair a blue screen failure that occurs during virtual simulation of a forensic disk image.
[0007] In a first aspect, the present application provides a method for repairing a disk image virtual simulation blue screen, comprising: obtaining a forensic disk image file of a target operating system; creating a KVM virtual machine based on the forensic disk image file; starting the KVM virtual machine using a pre-made Windows PE boot tool disk; the Windows PE boot tool disk is integrated with an ISO image file, the ISO image file including a boot program for repairing a virtual simulation blue screen; and repairing a blue screen failure of the forensic disk image during virtual simulation based on the boot program.
[0008] In an implementation of the first aspect, creating a KVM virtual machine based on the forensic disk image file includes:
[0009] Mount the forensic disk image file as a DD image file;
[0010] Static analysis of the disk partition table in the DD image file and the file system corresponding to the disk partition table to obtain analysis information; the analysis information includes the type, boot mode and instruction set of the target operating system;
[0011] Generate a configuration file of the KVM virtual machine based on the parsed information;
[0012] Convert the DD image file to a QCOW image file supported by QEMU;
[0013] The path of the ISO image file is set in the configuration file of the KVM virtual machine, and the ISO image file is set as the preferred startup item.
[0014] In an implementation of the first aspect, the method further includes:
[0015] Selecting a boot file that matches the instruction set from a preset boot file list; the boot file includes a boot loader, and the boot loader is used to load the kernel of the target operating system to guide the KVM virtual machine to start in conjunction with the ISO image file;
[0016] The path of the boot file is set in the configuration file of the KVM virtual machine.
[0017] In an implementation manner of the first aspect, the method further includes creating a virtual machine snapshot file based on the QCOW image file.
[0018] In an implementation of the first aspect, repairing a blue screen failure of the forensic disk image during virtual simulation based on the boot-up program includes:
[0019] Obtain all drive letters of the target operating system;
[0020] Traversing the drive letters, and determining the system partition by detecting a specific file under each drive letter;
[0021] Reading the registry under the system partition to obtain version information of the target operating system;
[0022] Determine whether the version of the target operating system is a version before Windows 10;
[0023] If yes, inject the IDE driver into the target operating system, and modify the disk interface type to the IDE type in the configuration file of the KVM virtual machine;
[0024] Otherwise, directly modify the disk interface type to SATA type in the configuration file of the KVM virtual machine;
[0025] Automatically shut down the KVM virtual machine;
[0026] The path of the ISO image file is removed from the configuration file of the KVM virtual machine, and the KVM virtual machine is waited to be restarted.
[0027] In an implementation of the first aspect, injecting an IDE driver into the target operating system includes:
[0028] Call RegLoadKeyA function to load Windows / System32 / System into the registry;
[0029] Register the IDE driver in the first root key of the registry; the first root key of the registry is HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\CriticalDeviceDatabase;
[0030] Register the service related to the IDE driver in the second root key of the registry; the second root key of the registry is HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Services;
[0031] Copying the IDE driver to the driver directory of the target operating system;
[0032] Call the RegUnloadKeyA function to unload the registry.
[0033] In an implementation of the first aspect, the formats of the forensic disk image file include DD, E01, QCOW, QCOW2, QCOW3, VHD, VHDX, RAW, ZVHD, XVA, and VMDK.
[0034] In a second aspect, the present application provides a disk image virtual simulation blue screen repair system, including: a disk image acquisition module, used to obtain the forensic disk image file of the target operating system; a virtual machine creation module, used to create a KVM virtual machine based on the forensic disk image file; a virtual machine startup module, used to start the KVM virtual machine using a pre-made Windows PE startup tool disk; the Windows PE startup tool disk is integrated with an ISO image file, and the ISO image file includes a boot program for repairing the virtual simulation blue screen; a blue screen repair module, used to repair the blue screen failure of the forensic disk image during virtual simulation based on the boot program.
[0035] In a third aspect, the present application provides a terminal, comprising: a processor and a memory; the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory, so that the terminal executes any of the methods described above.
[0036] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements any of the methods described above when executed by a processor.
[0037] As described above, the disk image virtual simulation blue screen repair method, system, terminal and medium described in the present application have the following beneficial effects:
[0038] (1) The forensic disk image file is converted into an operable virtual machine on the Linux operating system. This cross-platform virtualization technology improves the compatibility and flexibility of the system.
[0039] (2) It effectively solves the blue screen problem caused by the loss of hard disk drive in operating systems before Windows 10, improves the efficiency and accuracy of electronic evidence collection, and ensures the integrity and security of the evidence collection process.
[0040] (3) It provides technical support for the popularization of domestic operating systems and CPU chips, expands the application scope of this application, and promotes the development and application of domestic technologies. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] Figure 1 Shown is a schematic diagram of a hardware application scenario of an embodiment of the disk image virtual simulation blue screen repair method, system, terminal and medium described in this application.
[0042] Figure 2 Shown is a schematic structural diagram of a terminal according to an embodiment of the present application.
[0043] Figure 3Shown is a flow chart of an embodiment of a method for repairing a disk image virtual simulation blue screen described in the present application.
[0044] Figure 4 Shown is a KVM architecture diagram of an embodiment of the disk image virtual simulation blue screen repair method described in this application.
[0045] Figure 5 Shown is a structural schematic diagram of another embodiment of the disk image virtual simulation blue screen repair method described in the present application.
[0046] Figure 6 Shown is a flow chart of another embodiment of the method for repairing the disk image virtual simulation blue screen described in the present application.
[0047] Figure 7 Shown is a flow chart of another embodiment of the method for repairing the disk image virtual simulation blue screen described in the present application.
[0048] Figure 8 Shown is a flowchart of an embodiment of repairing the virtual simulation blue screen problem on the Kylin operating system by offline injection of IDE drivers as described in this application.
[0049] Fig. 9 Shown is a structural schematic diagram of an embodiment of a repair system for a disk image virtual simulation blue screen described in the present application.
[0050] Fig.10 Shown is a schematic structural diagram of another embodiment of the terminal described in the present application. DETAILED DESCRIPTION
[0051] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.
[0052] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed at will, and the component layout may also be more complicated.
[0053] In addition, in this application, descriptions such as "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in this field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.
[0054] The following embodiments of the present application provide a method, system, terminal and medium for repairing a disk image virtual simulation blue screen. Figure 1 , showing a hardware application scenario diagram of an embodiment of the disk image virtual simulation blue screen repair method, system, terminal and medium described in this application.
[0055] like Figure 1 As shown, the physical machine corresponds to the physical computer terminal, which provides the hardware environment for the virtual machine. Multiple operating systems can be installed on a computer terminal, and these operating systems can communicate with each other.
[0056] The method for repairing the disk image virtual simulation blue screen described in the present application is applicable to the cross-platform disk image virtualization field, especially for the scenario of virtualizing operating systems before Windows 10 in the Linux operating system environment.
[0057] This application realizes the conversion of forensic disk image files into an operable virtual machine on the Linux operating system, effectively solving the blue screen problem caused by the loss of hard disk drive in operating systems before Windows 10, improving the efficiency and accuracy of electronic evidence collection, ensuring the integrity and security of the evidence collection process, and also providing technical support for the popularization of domestic operating systems and CPU chips.
[0058] The operating systems prior to Windows 10 described in this application include Windows XP, Windows Vista, Windows 7, Windows 8 / 8.1, and Windows Server series.
[0059] The disk image virtual simulation blue screen repair method provided in the embodiment of the present application can be used in the following Figure 2 The terminal may include: a processor and a memory, wherein the processor may be a central processing unit, and the memory is used to store data.
[0060] It should be noted that Figure 2The terminal in the figure is only used as an example and does not limit the specific structure of the terminal.
[0061] Optionally, the terminal may further include: a communication transmission device and an input and output device.
[0062] Optionally, the memory may be used to store computer programs, such as software programs and modules of application software, and the memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0063] Optionally, the communication transmission device can be used to receive or send data via a network, which may include a wireless network provided by a communication provider of the computer terminal. The communication transmission device may include a NIC (Network Interface Controller) that can be connected to other network devices through a base station so as to communicate with the Internet.
[0064] The technical solutions in the embodiments of the present application will be described in detail below in conjunction with the drawings in the embodiments of the present application.
[0065] See also Figure 3 , showing a flow chart of an embodiment of a method for repairing a disk image virtual simulation blue screen described in the present application.
[0066] like Figure 3 As shown, this embodiment provides a method for repairing a disk image virtual simulation blue screen, including the following steps S100 to S400.
[0067] In step S100, a forensic disk image file of a target operating system is obtained.
[0068] In one embodiment of the present application, the target operating system is the operating system to be forensically collected. By analyzing the header features of the forensic disk image file, the forensic personnel can determine the exact format of the forensic disk image file of the target operating system.
[0069] The header of the forensic disk image file usually contains some important metadata information, which is used to indicate the basic properties and creation process of the file. Specifically, the header features of the forensic disk image file include a file feature signature and a file domain. The file feature signature is usually a unique string of codes or symbols, which is used to uniquely identify the forensic disk image file. The file domain includes important information about the file structure and content. By checking the file domain of the forensic disk image file, the forensic personnel can determine the hardware version of the virtual machine, the compatibility settings, and the actual size of the virtual disk.
[0070] The forensic disk image files supported by this application have various formats, including DD, E01, QCOW, QCOW2, QCOW3, VHD, VHDX, RAW, ZVHD, XVA, and VMDK. Specifically, E01 usually contains unconverted or unprocessed raw disk sector data. This format is simple and direct, and retains the structure of the original file system. ZVHD is an advanced virtual hard disk image format that provides a more complete view of the system environment, including partition tables, boot sectors, etc., and supports functions such as Windows dynamic volumes and restore points. RAW is an unformatted raw binary disk image that contains the physical layout of the disk and all data. Due to space limitations, each format will not be introduced in detail here.
[0071] In the existing digital forensics field, open source tools do not support many image formats, that is, there are still deficiencies in the diversity and scalability of image formats, which will increase the complexity and difficulty of forensics work. At the same time, this limitation also slows down the efficiency of the forensics process and may affect the integrity and accuracy of the forensics results.
[0072] This application can adapt to a variety of common image formats and has good expansion capabilities. This enables this application to better cope with various data formats encountered in the forensic scene. This extensibility not only includes support for existing formats, but also means that when new image formats appear in the future, the program can support these new formats through updates or upgrades, maintaining the lasting effectiveness and adaptability of the program.
[0073] In step S200, a KVM virtual machine is created based on the forensic disk image file.
[0074] See also Figure 4 , showing a KVM architecture schematic diagram of an embodiment of the disk image virtual simulation blue screen repair method described in this application.
[0075] KVM (Kernel-based Virtual Machine) is a lightweight virtualization solution based on the Linux kernel. This technology can create and run virtual machines on Linux systems without additional software support. KVM implements virtualization functions by modifying the Linux kernel to support virtualization technology and adding the KVM kernel module on it. The KVM kernel module provides virtual hardware devices, including processors (CPUs), memory, storage, and network interfaces, allowing operating systems and applications to run in virtual machines. Since KVM is implemented directly in the Linux kernel and avoids an additional hypervisor layer, it has high performance, can reduce system overhead and improve the operating efficiency of virtual machines.
[0076] See also Figure 5 , which is a structural schematic diagram of another embodiment of the disk image virtual simulation blue screen repair method described in this application.
[0077] like Figure 5 As shown, creating a KVM virtual machine based on the forensic disk image file includes the following steps S201 to S205.
[0078] In step S201, the forensic disk image file is mounted as a DD image file.
[0079] Disk image mounting means that in a computer operating system, a disk image file is temporarily or permanently loaded into a directory in the system through specific commands or operations, so that the system can access the contents of the image file just like accessing a physical disk.
[0080] Since the DD image file format is a widely recognized standard format, this application ensures data compatibility and interchangeability by mounting the forensic disk image file as a DD image file, so that the output data can be accepted by different digital forensics tools and platforms.
[0081] In one embodiment of the present application, a specific image mounting program can be used to mount the forensic disk image file as a DD image file. The execution steps of the specific image mounting program include: using the mount command to mount the forensic disk image file to a temporary directory; running the dd command in the mounted directory to read or operate the data in the forensic disk image file.
[0082] Existing image mounting programs usually only run on Windows platforms. This platform dependency reduces the scope of application of these programs and limits their application on other platforms such as Linux operating systems. More importantly, these programs may not be able to adapt to different CPU architectures such as x86 and ARM, which is particularly disadvantageous in diverse computing environments. The lack of cross-platform capabilities not only affects the flexibility of forensic tools, but also limits the ability of forensic personnel to conduct data investigation and analysis in different environments.
[0083] In contrast, the image mount program used in this application is compatible with mainstream operating systems such as Windows and Linux, which means that forensic personnel can use this tool in a wider range of environments, greatly improving the applicability of the tool. At the same time, the program has the ability to support mainstream CPU architectures such as x86 and arm, which also ensures the compatibility of the program on different hardware platforms, providing greater flexibility for forensic work.
[0084] In step S202, the disk partition table in the DD image file and the file system corresponding to the disk partition table are statically parsed to obtain parsing information.
[0085] In the process of statically parsing the DD image file, the disk partition table and the corresponding file system can be analyzed without starting the image, thereby obtaining rich parsing information. The advantage of static parsing is that it does not affect the original data, ensuring the non-intrusiveness of the forensic process and the originality of the data.
[0086] The parsed information includes the type, boot mode and instruction set of the target operating system. Specifically, the type of the target operating system includes Windows, Linux, macOS, etc. The boot mode of the target operating system includes a unified extensible firmware interface (UEFI) and a basic input and output system (BIOS). Different instruction sets mean different processing capabilities and performance.
[0087] In step S203, a configuration file of the KVM virtual machine is generated based on the parsed information.
[0088] In one embodiment of the present application, the configuration file of the KVM virtual machine is a descriptive file in XML format, which is used to preset various hardware and startup configurations required for the virtual machine.
[0089] Specifically, the configuration file describes information such as the number of hard disks, the size of memory, and the processing power of the CPU. This information is crucial for performance adjustment and resource allocation of the virtual machine. In addition, the configuration file also includes boot settings, such as whether a bootable ISO image file is included, and the specific process of self-starting at boot. These boot settings determine the behavior mode of the virtual machine when it starts, such as giving priority to booting from an ISO image for system installation, or booting from a specific hard disk to enter the operating system.
[0090] In step S204, the DD image file is converted into a QCOW image file supported by QEMU.
[0091] Since DD image files do not support compressed storage, the size of their backup files is consistent with the original data, which is not conducive to efficient storage and management. In addition, given the exclusive support of the QCOW format by KVM virtual machines, it is necessary to further convert the DD image file into a QCOW image file after obtaining it through mounting. As a lightweight disk image format, the use of QCOW image files can significantly reduce storage requirements and improve resource utilization.
[0092] In one embodiment of the present application, the qemu-img command can be used to implement the conversion of the DD image file to the QCOW image file. Specifically, by adjusting the compression ratio, setting encryption, and embedding metadata, a series of operations can be performed to ensure that the generated QCOW image file can meet the requirements of the KVM virtual machine and retain all necessary forensic information.
[0093] In step S205, the path of the ISO image file is set in the configuration file of the KVM virtual machine, and the ISO image file is set as a preferred startup item.
[0094] In one embodiment of the present application, the path of the ISO image file can be specified by modifying the startup-related tag attribute in the XML configuration file of the KVM virtual machine, and it can be set as the preferred startup item. By this method, when the KVM virtual machine is started, it can be ensured that the operating system is first loaded and attempted to be installed or restored from the set ISO image file.
[0095] In one embodiment of the present application, the disk image virtual simulation blue screen repair method provided in this embodiment also includes the following steps S206 to S207.
[0096] In step S206, a boot file matching the instruction set is selected from a preset boot file list.
[0097] Specifically, the boot file includes a boot loader, and the boot loader is used to load the kernel of the target operating system to guide the KVM virtual machine to start in coordination with the ISO image file.
[0098] In step S207, the path of the boot file is set in the configuration file of the KVM virtual machine.
[0099] It should be noted that each boot file in the boot file list is an existing resource and can be directly downloaded and used. In addition, the boot file is not necessary in all cases; its necessity depends on different application scenarios, and some scenarios may not require a boot file.
[0100] In the prior art, creating a virtual machine usually relies on mature virtualization tools designed for Windows platforms, such as VMWare Workstation or VirtualBox. However, these tools only support simulating operating system virtual machines of the x86 architecture, and cannot meet the simulation requirements of other processor architectures (such as the arm architecture). In contrast, the KVM technology used in this application shows a wider applicability in creating virtual machines, and it can support the simulation of multiple processor architectures including x86 and arm.
[0101] In one embodiment of the present application, the method for repairing a disk image virtual simulation blue screen provided in this embodiment further includes creating a virtual machine snapshot file based on the QCOW image file.
[0102] Virtual machine snapshot technology provides users with a mechanism to create an accurate record of the system state during the operation of a virtual machine. With virtual machine snapshots, users can capture multiple states of the virtual machine's memory, disk, and configuration information. This feature is particularly suitable for scenarios that require rollback at a specific moment, because it allows users to easily restore to the previous snapshot point, thereby avoiding the risk of data loss or system damage that may be caused by actual operations.
[0103] In step S300, the KVM virtual machine is started using the pre-made Windows PE boot tool disk.
[0104] In one embodiment of the present application, the Windows PE boot tool disk is integrated with an ISO image file, and the ISO image file includes a boot-up program for repairing a virtual simulation blue screen.
[0105] Windows PE, or Windows Preinstallation Environment, is a lightweight operating system that is primarily used for system maintenance and recovery. Windows PE provides a concise framework in which users can add custom startup programs to perform specific maintenance tasks.
[0106] In the embodiment of the present application, when the KVM virtual machine encounters a blue screen problem at startup, it can be repaired with the help of a Windows PE boot tool disk integrated with an ISO image file. The ISO image file contains a startup self-starting program for repairing the virtual simulation blue screen, which can be run in a Windows PE environment.
[0107] When starting a KVM virtual machine, you can effectively solve the blue screen problem of the virtual machine by loading the Windows PE environment and running the blue screen repair program in the environment. The repair process usually includes steps such as scanning system errors, repairing damaged system files, and restoring system stability. The entire process is completed according to the instructions of the program without manual intervention, which improves the repair efficiency and success rate.
[0108] In step S400, a blue screen failure that occurs during virtual simulation of the forensic disk image is repaired based on the boot program.
[0109] See also Figure 6 , showing a flow chart of another embodiment of the method for repairing the disk image virtual simulation blue screen described in the present application.
[0110] like Figure 6 Repairing the blue screen failure of the forensic disk image during virtual simulation based on the boot-up program includes the following steps S401 to S408.
[0111] In step S401, all drive letters of the target operating system are obtained.
[0112] In step S402, the drive letters are traversed, and the system partition is determined by detecting a specific file under each drive letter.
[0113] In step S403, the registry under the system partition is read to obtain version information of the target operating system.
[0114] Specifically, the product name of the current Windows operating system is stored in the Microsoft\Windows NT\CurrentVersion\ProductName registry path. The main function of this key value is to identify the running Windows system version. By viewing this key value, you can know the full product name of the operating system, which usually contains the following information:
[0115] ProductName: indicates the product name of the operating system, such as Windows 7, Windows 8.1, and Windows 10.
[0116] Edition ID: Indicates the version and type of the operating system, such as "Professional", "Home", "Enterprise", etc.
[0117] Current Build: Indicates the build version number of the operating system.
[0118] In step S404, it is determined whether the version of the target operating system is a version before Windows 10.
[0119] In step S405, if it is a version before Windows 10, the IDE (Integrated Development Environment) driver is injected into the target operating system, and the disk interface type is modified to the IDE type in the configuration file of the KVM virtual machine; if it is not a version before Windows 10, go to step S406.
[0120] The types of hard disk interfaces that can be seen at present mainly include IDE, SATA, SCSI, SAS and FC, among which IDE is commonly known as parallel port, and SATA is commonly known as serial port. These two types of hard disks are common hard disks in personal computers and low-end servers; SCSI is the abbreviation of "small computer system dedicated interface", and SCSI hard disk is a hard disk that uses this interface; SAS is the SCSI interface of the serial port. Generally, server hard disks use these two types of interfaces. Their performance is higher than the above two hard disks, and they are more stable, but they are expensive, have small capacity, and are noisy; FC is fiber channel. Like SCIS interface, fiber channel was not originally designed and developed for hard disks. It was designed specifically for network systems, but with the demand for speed in storage systems, it was gradually applied to hard disk systems; SSD is also called electronic hard disk or solid-state electronic disk, which is a hard disk composed of a control unit and a solid-state storage unit (DRAM or FLASH chip). The interface specifications and definitions, functions and usage methods of solid-state hard disks are the same as those of ordinary hard disks, and the product appearance and size are also consistent with ordinary hard disks. The new generation of solid-state hard disks generally use SATA-2 interface. But its cost is relatively high.
[0121] In step S406, the disk interface type is directly modified to the SATA type in the configuration file of the KVM virtual machine.
[0122] In step S407, the KVM virtual machine is automatically shut down.
[0123] In step S408, the path of the ISO image file is removed from the configuration file of the KVM virtual machine, and the KVM virtual machine is waited to be restarted.
[0124] Through experimental research, it is found that Windows 10 and later versions of the operating system have a large number of hard disk interface drivers built in. These programs can automatically identify and load the corresponding hard disk interface drivers when the virtual machine system starts. If the IDE driver is lost, Windows 10 and later versions of the operating system have the ability to call the built-in IDE driver and automatically install it, thereby ensuring that the hard disk can be recognized and used normally. Therefore, in Windows 10 and later versions of the operating system, the problem of blue screen when the virtual machine is started is extremely rare, and there is no need to manually inject the hard disk driver.
[0125] See also Figure 7 , showing a flow chart of another embodiment of the method for repairing the disk image virtual simulation blue screen described in the present application.
[0126] like Figure 7 , injecting the IDE driver into the target operating system includes the following steps S409 to S412.
[0127] In step S409, the RegLoadKeyA function is called to load Windows / System32 / System into the registry.
[0128] In step S410, the IDE driver is registered in the first root key of the registry. The first root key of the registry is HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\CriticalDeviceDatabase.
[0129] In step S411, the service related to the IDE driver is registered in the second root key of the registry. The second root key of the registry is HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Services.
[0130] In step S412, the IDE driver is copied to the driver directory of the target operating system.
[0131] In step S413, the RegUnloadKeyA function is called to unload the registry.
[0132] The registry is essentially a database system that stores all system and application initialization information. The database contains configuration files of various hardware devices, interrelated application and document files, window display mode, network connection parameters, and important network settings related to computer security. The design of the registry optimizes management convenience, improves security, and is suitable for network operations. Table 1 lists the root key information of the registry.
[0133] Table 1. Registry root key information
[0134] Root key abbreviation Root key full name Storage Content HKCR HKEY_CLASSES_ROOT File types and associated applications HKCU HKEY_USERS Setting information of the current system user HKLM HKEY_LOCAL_MACHINE System hardware and software configuration HKU HKEY_CURRENT_USER Settings information for all users HKCC HKEY_CURRENT_CONFIG Current system hardware configuration information
[0135] In one embodiment of the present application, the IDE driver is injected in an offline manner.
[0136] IDE drivers usually refer to certain components in the integrated development environment, which are responsible for managing and controlling external hardware devices, especially supporting simulators, debuggers, or specific hardware platforms during software development. IDE drivers can automatically set paths, configure communication protocols, etc., allowing developers to program and test more conveniently. They usually interact with the IDE core through APIs, providing a unified interface to operate hardware-related functions. Some common IDE drivers include USB debugging drivers, JTAG debugging drivers, etc., which are all designed to improve development efficiency.
[0137] The services related to the IDE driver include system services such as atapi, IntelIde and PCIIde.
[0138] In one embodiment of the present application, the driver directory of the target operating system is Windows / System32 / drivers, which is where the Windows operating system specifically stores device drivers. These drivers are the bridge between the hardware device and the operating system, responsible for managing and controlling various hardware components inside the computer, such as sound cards, network cards, graphics cards, printers, etc.
[0139] During the process of injecting a hard drive, the conventional method is to mount the QCOW disk with read and write permissions, usually using the qemu-nbd tool and the ntfs-3g driver. However, actual operational experience shows that the ntfs-3g driver does not show stable reliability when processing read and write operations of the NTFS file system, which may cause the risk of data loss or damage.
[0140] In order to overcome this defect, the present application uses the Windows PE boot tool disk to start the operating system and uses the native NTFS driver of the Windows operating system to perform read and write operations on the NTFS file system. This method significantly improves the stability and reliability of the operation, thereby reducing the risk of data loss or damage.
[0141] The following will take the forensic disk image file win7.zvhd as an example to explain in detail how to fix the blue screen problem encountered during disk image virtual simulation by offline injection of IDE driver on Kylin operating system. The Kylin operating system used in this embodiment is developed based on the Linux kernel.
[0142] See also Figure 8 , showing a flowchart of an embodiment of repairing the virtual simulation blue screen problem on the Kylin operating system by offline injection of IDE driver as described in this application.
[0143] like Figure 8 First, by analyzing the header features of the forensic disk image file win7.zvhd, it can be confirmed that the forensic disk image file uses the ZVHD format. Then, a specific image mounter is used to mount the forensic disk image file win7.zvhd as a DD image file. By statically analyzing the partition table and file system information of the DD image file, it is found that the forensic disk image file win7.zvhd is an image file of the Windows 7 operating system booted by BIOS, and the image file includes a system partition and a data partition. Both partitions are NTFS file systems and support x86 architecture CPUs. Based on these parsed information, an XML format configuration file required for creating a KVM virtual machine is generated and named Win7.xml. The qemu-img command is used to convert the DD image file win7.dd into a QCOW image file, and different boot files are selected according to different instruction sets. Then, a virtual machine snapshot is made based on the QCOW image file. In the configuration file Win7.xml, specify the path of the ISO image file Boot.iso and set it as the preferred startup item, where Boot.iso includes the startup program fix.exe for repairing the virtual simulation blue screen. After preparing the configuration file Win7.xml and the QCOW image file, use the virtual machine management command virsh to start the KVM virtual machine. During the startup process of the KVM virtual machine, the startup program fix.exe will traverse all drive letters to locate the system partition, and by reading the registry Microsof t\\Windows NT\\CurrentVersion\\ProductName, it is learned that the operating system is located in the C drive and the version information of the operating system is Windows 7. Since Windows 7 is a version before Windows 10, it is necessary to inject the IDE driver into the system and change the hard disk interface type to IDE type in the configuration file Win7.xml. After the startup program fix.exe function is completed, the operation of automatically shutting down the KVM virtual machine is executed. Finally, remove the path of the Boot.iso file from the configuration file Win7.xml, and then restart the KVM virtual machine to complete the blue screen repair.
[0144] It should be noted that the protection scope of the disk image virtual simulation blue screen repair method described in the embodiment of the present application is not limited to the execution order of the steps listed in this embodiment. All solutions implemented by adding, reducing or replacing steps in the prior art based on the principles of the present application are included in the protection scope of the present application.
[0145] In addition, the technical solution of the present application is also applicable to injecting other types of driver files into a virtual machine to achieve a wider range of application purposes. For example, by injecting a network card driver, the network function can be expanded without changing the disk interface type. Due to space limitations, all possible application scenarios are not listed one by one here.
[0146] See also Fig. 9 , showing a structural schematic diagram of an embodiment of a disk image virtual simulation blue screen repair system described in the present application.
[0147] like Fig. 9 As shown, this embodiment provides a disk image virtual simulation blue screen repair system, including a disk image acquisition module, a virtual machine creation module, a virtual machine startup module and a blue screen repair module.
[0148] The disk image acquisition module is used to obtain the forensic disk image file of the target operating system.
[0149] The virtual machine creation module is used to create a KVM virtual machine based on the forensic disk image file.
[0150] The virtual machine startup module is used to start the KVM virtual machine using a pre-made Windows PE startup tool disk; the Windows PE startup tool disk is integrated with an ISO image file, and the ISO image file includes a startup program for repairing a virtual simulation blue screen.
[0151] The blue screen repair module is used to repair the blue screen failure of the forensic disk image during virtual simulation based on the boot program.
[0152] It should be noted that the disk image virtual simulation blue screen repair system provided in the embodiment of the present application can implement the disk image virtual simulation blue screen repair method described in the present application, but the implementation device of the disk image virtual simulation blue screen repair method described in the present application includes but is not limited to the structure of the disk image virtual simulation blue screen repair system listed in the present embodiment. All structural deformations and replacements of the prior art made according to the principles of the present application are included in the protection scope of the present application.
[0153] See also Fig.10 , which is a schematic diagram of the structure of another embodiment of the terminal described in the present application.
[0154] like Fig.10 As shown, this embodiment provides a terminal, including: a processor and a memory.
[0155] The memory is used to store computer programs.
[0156] The processor is used to execute the computer program stored in the memory so that the terminal executes any one of the above-mentioned methods for repairing the disk image virtual simulation blue screen.
[0157] In the several embodiments provided in the present application, it should be understood that the disclosed system, device or method can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules / units is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or units can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules or units, which can be electrical, mechanical or other forms.
[0158] The modules / units described as separate components may or may not be physically separated, and the components displayed as modules / units may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules / units may be selected according to actual needs to achieve the purpose of the embodiments of the present application. For example, the functional modules / units in the various embodiments of the present application may be integrated into one processing module, or each module / unit may exist physically separately, or two or more modules / units may be integrated into one module / unit.
[0159] Those of ordinary skill in the art should further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0160] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by the processor, the method for repairing the virtual simulation blue screen of the disk image described in any of the above items is implemented. A person of ordinary skill in the art can understand that all or part of the steps in the method for implementing the above embodiment can be completed by instructing the processor through a program, and the program can be stored in a computer-readable storage medium, and the storage medium is a non-transitory medium, such as a random access memory, a read-only memory, a flash memory, a hard disk, a solid-state hard disk, a magnetic tape, a floppy disk, an optical disc, and any combination thereof. The above storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state disk (SSD)), etc.
[0161] The present application embodiment may also provide a computer program product, the computer program product including one or more computer instructions. When the computer instructions are loaded and executed on a computing device, the process or function described in the embodiment of the present application is generated in whole or in part. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer or data center.
[0162] When the computer program product is executed by a computer, the computer executes the method described in the above method embodiment. The computer program product may be a software installation package, and when the above method is required, the computer program product may be downloaded and executed on a computer.
[0163] The descriptions of the processes or structures corresponding to the above-mentioned figures have different emphases. For parts that are not described in detail in a certain process or structure, please refer to the relevant descriptions of other processes or structures.
[0164] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.
Claims
1. A method for repairing a disk image virtual simulation blue screen, characterized in that: include: Get the forensic disk image file of the target operating system; Creating a KVM virtual machine based on the forensic disk image file; Using a pre-made Windows PE boot tool disk to start the KVM virtual machine; the Windows PE boot tool disk is integrated with an ISO image file, and the ISO image file includes a boot-up self-starting program for repairing a virtual simulation blue screen; Based on the boot-up program, the blue screen failure of the forensic disk image during virtual simulation is repaired.
2. The method according to claim 1, characterized in that Creating a KVM virtual machine based on the forensic disk image file includes: Mount the forensic disk image file as a DD image file; Static analysis of the disk partition table in the DD image file and the file system corresponding to the disk partition table to obtain analysis information; the analysis information includes the type, boot mode and instruction set of the target operating system; Generate a configuration file of the KVM virtual machine based on the parsed information; Convert the DD image file to a QCOW image file supported by QEMU; The path of the ISO image file is set in the configuration file of the KVM virtual machine, and the ISO image file is set as the preferred startup item.
3. The method according to claim 2, characterized in that Also includes: Selecting a boot file that matches the instruction set from a preset boot file list; The boot file includes a boot loader, and the boot loader is used to load the kernel of the target operating system to guide the KVM virtual machine to start in conjunction with the ISO image file; The path of the boot file is set in the configuration file of the KVM virtual machine.
4. The method according to claim 2, characterized in that: The method also includes creating a virtual machine snapshot file based on the QCOW image file.
5. The method according to claim 1, characterized in that Repairing the blue screen failure of the forensic disk image during virtual simulation based on the boot-up program includes: Obtain all drive letters of the target operating system; Traversing the drive letters, and determining the system partition by detecting a specific file under each drive letter; Reading the registry under the system partition to obtain version information of the target operating system; Determine whether the version of the target operating system is a version before Windows 10; If yes, inject the IDE driver into the target operating system, and modify the disk interface type to the IDE type in the configuration file of the KVM virtual machine; Otherwise, directly modify the disk interface type to SATA type in the configuration file of the KVM virtual machine; Automatically shut down the KVM virtual machine; The path of the ISO image file is removed from the configuration file of the KVM virtual machine, and the KVM virtual machine is waited to be restarted.
6. The method according to claim 5, characterized in that Injecting an IDE driver into the target operating system includes: Call RegLoadKeyA function to load Windows / System32 / System into the registry; Register the IDE driver in the first root key of the registry; the first root key of the registry is HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\CriticalDeviceDatabase; Register the service related to the IDE driver in the second root key of the registry; the second root key of the registry is HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Services; Copying the IDE driver to the driver directory of the target operating system; Call the RegUnloadKeyA function to unload the registry.
7. The method according to claim 1, characterized in that The formats of the forensic disk image files include DD, E01, QCOW, QCOW2, QCOW3, VHD, VHDX, RAW, ZVHD, XVA, and VMDK.
8. A disk image virtual simulation blue screen repair system, characterized in that: include: The disk image acquisition module is used to obtain the forensic disk image file of the target operating system; A virtual machine creation module, used to create a KVM virtual machine based on the forensic disk image file; A virtual machine startup module, used to start the KVM virtual machine using a pre-made Windows PE startup tool disk; the Windows PE startup tool disk is integrated with an ISO image file, and the ISO image file includes a startup program for repairing a virtual simulation blue screen; The blue screen repair module is used to repair the blue screen failure of the forensic disk image during virtual simulation based on the boot program.
9. A terminal, characterized in that: include: Processor and memory; The memory is used to store computer programs; The processor is used to execute the computer program stored in the memory, so that the terminal executes the disk image virtual simulation blue screen repair method according to any one of claims 1 to 8.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method for repairing the disk image virtual simulation blue screen described in any one of claims 1 to 8 is implemented.
