CN113485755B - Device driver verification method, device and storage medium - Google Patents
Device driver verification method, device and storage medium Download PDFInfo
- Publication number
- CN113485755B CN113485755B CN202110740868.5A CN202110740868A CN113485755B CN 113485755 B CN113485755 B CN 113485755B CN 202110740868 A CN202110740868 A CN 202110740868A CN 113485755 B CN113485755 B CN 113485755B
- Authority
- CN
- China
- Prior art keywords
- driver
- test
- operating system
- target
- drivers
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a device driver verification method, a device, equipment and a storage medium. The method comprises the following steps: mapping the hardware equipment of the target host into a virtual machine, and starting an operating system corresponding to the source host on the virtual machine; searching a plurality of drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment; running environment test is carried out on a plurality of drivers in an operating system, and when the test is passed, the tested drivers are moved to a temporary folder; and selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver installed. By mapping the hardware equipment of the target computer into the virtual machine, starting an operating system to be migrated or restored on the virtual machine, and carrying out matching and testing of a driving program on the mapped hardware equipment on the operating system, the migrated or restored operating system can be ensured to normally use the hardware equipment of the target host.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a device driver verification method, apparatus, device, and storage medium.
Background
When operating system migration or operating system restoration is performed, if the hardware device of the target computer and the driver installed by the operating system are not precisely adapted, the migrated and restored operating system may not normally use the hardware device, and the driver needs to be reinstalled. Because a hardware device may have multiple versions of drivers, if the drivers are to be manually matched and verified one by one, the workload is huge and the efficiency is low.
The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present invention and is not intended to represent an admission that the foregoing is prior art.
Disclosure of Invention
The invention mainly aims to provide a device driver verification method, device, equipment and storage medium, and aims to solve the technical problem that a currently migrated or restored operating system cannot normally use a hardware device of a target host.
In order to achieve the above object, the present invention provides a device driver verification method, the method comprising the steps of:
mapping the hardware equipment of the target host into a virtual machine, and starting an operating system corresponding to the source host on the virtual machine;
Searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment;
running environment tests are respectively carried out on the plurality of drivers in the operating system through the virtual machine, and when test results passing through the tests are obtained, the drivers passing through the tests are moved to a temporary folder;
and selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver.
Optionally, before searching the corresponding multiple drivers under the preset driver library catalog according to the hardware identifier corresponding to the hardware device, the method further includes:
collecting drivers of all versions corresponding to all hardware devices connected on a target host, and generating a target drive library according to the drivers of all versions corresponding to all hardware devices;
copying the target drive library into a hard disk of a virtual machine;
and mapping the data in the hard disk of the virtual machine to a preset drive library directory.
Optionally, the running environment test is performed on the plurality of drivers in the operating system by the virtual machine, and when a test result of passing the test is obtained, the running environment test is performed on the driver passing the test to a temporary folder, including:
Sequentially installing the plurality of drivers in the operating system through the virtual machine;
the hardware equipment is driven by the driver to interact with the hardware equipment, so that the driver is tested according to an interaction result;
and when the test result of passing the test is obtained, unloading the drive program of passing the test in the operating system, and moving the drive program of passing the test to a temporary folder.
Optionally, the driving the hardware device by the driver, interacting with the hardware device, so as to test the driver according to an interaction result, including:
performing forbidden interaction on the hardware equipment through the driver according to the forbidden instruction to obtain a forbidden interaction result;
enabling interaction is carried out on the hardware equipment through the driver according to the enabling instruction, and enabling interaction results are obtained;
performing mode setting on the hardware equipment through the driver according to a mode setting instruction, and receiving feedback mode information to obtain a mode setting interaction result;
transmitting a data packet to the hardware equipment through the driver, and receiving a target data packet fed back by the hardware equipment to obtain a data interaction result;
And testing the driver according to the forbidden interaction result, the enabled interaction result, the mode setting interaction result and the data interaction result.
Optionally, after the driver is tested according to the disabled interaction result, the enabled interaction result, the mode setting interaction result and the data interaction result, the method further includes:
and when the forbidden interaction result is the forbidden interaction normal, the enabled interaction result is the enabled interaction normal, the mode setting interaction result is the mode setting interaction normal and the data interaction result is the data interaction normal, obtaining a test result passing the test.
Optionally, after the driver drives the hardware device and interacts with the hardware device to test the driver according to the interaction result, the method further includes:
when a test result of test failure is obtained, deleting the driver program of the test failure from the mapping data under the preset driver library;
and unloading the drive program which fails the test in the operating system.
Optionally, the selecting the target driver from the temporary folder includes:
Detecting whether the temporary folder contains a current driver corresponding to the hardware equipment or not;
when the temporary folder contains a plurality of current drivers corresponding to the hardware equipment, determining version information corresponding to the current drivers;
and selecting a target driver corresponding to the latest release version from the plurality of current drivers according to the version information.
In addition, in order to achieve the above object, the present invention also provides a device driver verification apparatus, including:
the mapping module is used for mapping the hardware equipment of the target host into the virtual machine and starting an operating system corresponding to the source host on the virtual machine;
the matching module is used for searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment;
the test module is used for respectively carrying out running environment test on the plurality of drivers in the operating system through the virtual machine, and moving the drivers passing the test to a temporary folder when the test result passing the test is obtained;
and the installation module is used for selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver.
In addition, in order to achieve the above object, the present invention also proposes a device driver verification device including: a memory, a processor, and a device driver verification program stored on the memory and executable on the processor, the device driver verification program configured to implement the steps of the device driver verification method as described above.
In addition, in order to achieve the above object, the present invention also proposes a storage medium having stored thereon a device driver verification program which, when executed by a processor, implements the steps of the device driver verification method as described above.
Mapping the hardware equipment of a target host into a virtual machine, and starting an operating system corresponding to a source host on the virtual machine; searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment; running environment tests are respectively carried out on a plurality of drivers in an operating system through a virtual machine, and when test results passing through the tests are obtained, the drivers passing through the tests are moved to a temporary folder; and selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver installed. By the method, the hardware equipment of the target computer is mapped into the virtual machine, the operating system to be migrated or restored is started on the virtual machine, and the mapping hardware equipment is subjected to matching and testing of the driving program on the operating system, so that the operating system with the target driving program is obtained, the target driving program is the driving program which passes the test and can normally use the equipment hardware of the target host, the operating system is migrated or restored according to the operating system with the target driving program, the operating system after migration or restoration can normally use the hardware equipment of the target host, the correct driving program is not required to be matched manually, and the efficiency of migrating or restoring the operating system is improved.
Drawings
FIG. 1 is a schematic diagram of a device driver verification device for a hardware runtime environment according to an embodiment of the present invention;
FIG. 2 is a flowchart of a device driver verification method according to a first embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a device mapping according to an embodiment of a device driver verification method of the present invention;
FIG. 4 is a flowchart illustrating a second embodiment of a device driver verification method according to the present invention;
FIG. 5 is a block diagram showing a first embodiment of a device driver verification apparatus according to the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to fig. 1, fig. 1 is a schematic diagram of a device driver verification device of a hardware running environment according to an embodiment of the present invention.
As shown in fig. 1, the device driver verification device may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a Wireless interface (e.g., a Wireless-Fidelity (Wi-Fi) interface). The Memory 1005 may be a high-speed random access Memory (Random Access Memory, RAM) Memory or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
Those skilled in the art will appreciate that the architecture shown in FIG. 1 does not constitute a limitation of the device driver verification device, and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
As shown in fig. 1, an operating system, a network communication module, a user interface module, and a device driver authentication program may be included in the memory 1005 as one type of storage medium.
In the device driver verification device shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the device driver verification apparatus of the present invention may be provided in the device driver verification apparatus, and the device driver verification apparatus calls the device driver verification program stored in the memory 1005 through the processor 1001 and executes the device driver verification method provided by the embodiment of the present invention.
An embodiment of the present invention provides a device driver verification method, and referring to fig. 2, fig. 2 is a flowchart of a first embodiment of the device driver verification method of the present invention.
In this embodiment, the device driver verification method includes the following steps:
step S10: mapping the hardware equipment of the target host into a virtual machine, and starting an operating system corresponding to the source host on the virtual machine.
It may be understood that the execution body of the embodiment is a device driver verification device, which may be a device such as a computer, a server, etc. that is in communication with the target host and has a virtual machine started, or may be a computer to which an operating system is migrated, and this embodiment is described by taking a computer to which an operating system is migrated as an example.
The migration of the operating system and data of one computer to another computer is called an operating system migration. The operating system includes windows, linux, etc., but may be other operating systems, and the present embodiment is not limited thereto. The computer before migration is called a source computer (source host), and the migrated computer is called a target computer (target host), and the source computer and the target computer may be physical computers or virtual computers. The present embodiment is not limited thereto.
It should be understood that the restoration of the operating system refers to restoring the operating system and data of the computer to some state before. The computer executing the backup operation is called a backup source computer (source host), and the state stored in the backup database is called a restore point, and the restore point in the backup database is restored to the target computer (target host) during the restore. The source computer and the target computer may be physical computers or virtual computers.
Referring to fig. 3, fig. 3 is a schematic diagram of a device mapping diagram of an embodiment of a device driver verification method according to the present invention, before an operating system is migrated or restored, a hardware device on a target host is mapped into a virtual machine through a network. As shown in fig. 3, in addition to virtual hardware devices (virtual hard disk 1 and virtual hard disk 2), PCI devices mapped via a network are attached to a virtual PCI bus. The PCI device mapped can be seen after the system is started by starting the operating system to be migrated or restored corresponding to the source host on the virtual machine, and the operating system of the virtual machine cannot normally use the PCI device because the operating system of the virtual machine is not provided with the drive program of the PCI device.
Step S20: searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment.
It should be noted that, the hardware identifier is a hardware ID, and step S20 includes querying the hardware ID of the hardware device, and then searching for the corresponding driver in the preset driver library directory according to the hardware ID. After the operating System detects the new hardware device, matching and searching the corresponding driver program in a preset driver library preset in the System, wherein the preset driver library catalog is the default driver library target, for example, the Windows operating System preset driver library catalog is C \Windows\System32\driver store\FileReductor.
It will be appreciated that a device driver is a program that allows the operating system and computer device to interact normally. If the operating system does not install the driver for the hardware device, the operating system cannot use the device.
Further, in order to avoid the operating system being bloated and the performance being low caused by the oversized preset driver library, before searching the corresponding plurality of drivers under the preset driver library according to the hardware identifier corresponding to the hardware device, the method further includes: collecting drivers of all versions corresponding to all hardware devices connected on a target host, and generating a target drive library according to the drivers of all versions corresponding to all hardware devices; copying the target drive library into a hard disk of a virtual machine; and mapping the data in the hard disk of the virtual machine to a preset drive library directory.
It should be noted that, the specific process of collecting all versions of drivers of all hardware devices connected to the target host in advance may be downloading, through a network, the drivers of all versions corresponding to all hardware devices in the drive store, or may be other manners, which is not limited in this embodiment. A full version of the target driver library is generated by a deployment tool (such as windows' disk. Exe) of the operating system, and the target driver library contains drivers for each version of each hardware device. When the virtual machine is created, the target drive library is copied into the virtual hard disk (such as virtual hard disk 2 in fig. 3), and after the operating system of the virtual machine is started, the data in the virtual hard disk 2 is mapped to the default drive library (under the default drive library) directory of the operating system. When the operating system of the virtual machine detects a new hardware device, a default driver library path is used for matching the drivers, and as the target driver library is a complete driver library, the drivers which can be found by the operating system may have multiple versions, and the operating system can select one of the versions of the drivers to install in the operating system according to a preset matching algorithm. Since the data in the virtual hard disk is mapped to the default drive library directory and is not a copy, the default drive library is not bloated after the operating system is migrated or restored.
In a specific implementation, there are two methods of mapping: one is to capture all file operation requests (such as enumerating files, reading files, writing files, deleting files, etc.) under a preset drive library directory through a file system filtering drive, redirect these file operation requests to the directory corresponding to the target drive library, so as to map the target drive library to the preset drive library directory, and then include the complete drive library under the preset drive directory. The other is to directly mount the target drive library to a preset drive catalog (which can be realized by a mount vol command for windows systems), and after mounting, the complete drive library can be seen under the preset drive catalog. By the two methods, data in the hard disk of the virtual machine is mapped to the preset drive library catalog, and all the pre-collected drive programs can be matched under the preset drive library catalog through the hardware identification.
Step S30: and respectively performing running environment test on the plurality of drivers in the operating system through the virtual machine, and moving the drivers passing the test to a temporary folder when the test result passing the test is obtained.
It should be understood that running environment testing refers to the installation, testing, and uninstallation of multiple drivers in an operating system. In a specific implementation, for the same hardware identifier, the target driver library may include a plurality of versions of drivers, and at this time, the plurality of versions of drivers are installed, tested and uninstalled in sequence. The method for moving the tested driver to the temporary folder comprises the following steps: and acquiring the drive program passing the test from a preset drive library catalog, and moving the drive program passing the test to a temporary folder. For example, if the test passes, the driver file is moved from Windows C: \Windows\System32\driver store\FileReposity to C: \driver_check for saving.
It should be noted that, after the operating system selects one version of the driver according to the preset matching algorithm to install the driver to the operating system and test, uninstalling the driver, notifying the operating system to match and install other versions of the driver under the default driver library catalog again, executing the test step again, if the test is passed, acquiring the passed driver from the preset driver library catalog, and moving the passed driver to the temporary folder. If the test fails, deleting the corresponding version of the driver under the preset driver library catalog until the operating system cannot be matched with other versions of device drivers under the preset driver library catalog.
Step S40: and selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver.
It can be understood that after the test is performed in step S30, all the drivers that pass the test are stored in the temporary folder, and the process of selecting the target driver from the temporary folder may be to randomly select a driver with a version from the temporary folder as the target driver, or may be to select the driver with the latest version as the target driver.
Specifically, the selecting the target driver from the temporary folder includes: detecting whether the temporary folder contains a current driver corresponding to the hardware equipment or not; when the temporary folder contains a plurality of current drivers corresponding to the hardware equipment, determining version information corresponding to the current drivers; and selecting a target driver corresponding to the latest release version from the plurality of current drivers according to the version information.
After testing all versions of drivers corresponding to a certain device, detecting the driver corresponding to the device in the temporary folder, and if the driver corresponding to the device is not available, indicating that the driver is not exactly matched; if only one driver is selected as a target driver, the target driver is installed in an operating system, and the driver is the driver which is precisely matched; if a plurality of versions of drivers exist, the driver corresponding to the latest release version is selected as a target driver and is installed in an operating system.
It should be understood that, after the step S40, the method further includes: and carrying out migration or restoration operation of the operating system on the target host according to the operating system provided with the target driver.
The method comprises the steps of mapping hardware equipment of a target host into a virtual machine, and starting an operating system corresponding to a source host on the virtual machine; searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment; running environment tests are respectively carried out on a plurality of drivers in an operating system through a virtual machine, and when test results passing through the tests are obtained, the drivers passing through the tests are moved to a temporary folder; and selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver installed. By the method, the hardware equipment of the target computer is mapped into the virtual machine, the operating system to be migrated or restored is started on the virtual machine, and the mapping hardware equipment is subjected to matching and testing of the driving program on the operating system, so that the operating system with the target driving program is obtained, the target driving program is the driving program which passes the test and can normally use the equipment hardware of the target host, the operating system is migrated or restored according to the operating system with the target driving program, the operating system after migration or restoration can normally use the hardware equipment of the target host, the correct driving program is not required to be matched manually, and the efficiency of migrating or restoring the operating system is improved.
Referring to fig. 4, fig. 4 is a flowchart illustrating a second embodiment of a device driver verification method according to the present invention.
Based on the above-mentioned first embodiment, before the step S30 of the device driver verification method of the present embodiment, the method further includes:
step S301: and sequentially installing the plurality of drivers in the operating system through the virtual machine.
It should be understood that in a specific implementation, all versions of drivers corresponding to a preset driver library directory may be first searched out through a hardware identifier corresponding to a hardware device, and a plurality of drivers may be installed, tested and uninstalled in sequence; and the method can also be used for installing, testing and uninstalling according to the hardware identifier corresponding to the hardware device from the preset driver library catalog, if the test is passed, the driver under the preset driver library catalog is moved to the temporary folder, if the test fails, the driver under the preset driver library target is deleted, that is, the drivers for testing are removed from the preset driver library catalog, and the method is used for installing, testing and uninstalling according to the hardware identifier corresponding to the hardware device from the preset driver library catalog again until other drivers corresponding to the hardware device cannot be matched under the preset driver library catalog, so that the situation of repeated test cannot exist.
Step S302: and driving the hardware equipment through the driver program, and interacting with the hardware equipment to test the driver program according to an interaction result.
The method further comprises the steps of: and configuring the driver, and executing step S302 according to the configured driver. Taking the network card device as an example, after the driver is installed successfully, the network card is configured, such as setting an IP address, a subnet mask, and the like. After the configuration is finished, the network card equipment is interacted with, and the test is carried out according to the interaction result.
Specifically, the step S302 includes: performing forbidden interaction on the hardware equipment through the driver according to the forbidden instruction to obtain a forbidden interaction result; enabling interaction is carried out on the hardware equipment through the driver according to the enabling instruction, and enabling interaction results are obtained; performing mode setting on the hardware equipment through the driver according to a mode setting instruction, and receiving feedback mode information to obtain a mode setting interaction result; transmitting a data packet to the hardware equipment through the driver, and receiving a target data packet fed back by the hardware equipment to obtain a data interaction result; and testing the driver according to the forbidden interaction result, the enabled interaction result, the mode setting interaction result and the data interaction result.
Further, after the driver is tested according to the disabled interaction result, the enabled interaction result, the mode setting interaction result and the data interaction result, the method further includes: and when the forbidden interaction result is the forbidden interaction normal, the enabled interaction result is the enabled interaction normal, the mode setting interaction result is the mode setting interaction normal and the data interaction result is the data interaction normal, obtaining a test result passing the test.
It can be understood that, taking the network card device as an example for explanation, the interactive test process is as follows: enabling and disabling the network card device; enabling the network card equipment to enter a power saving mode and then awakening to a working mode; receiving and transmitting data packets through the network card equipment, and establishing network connection; if none of these interactions is problematic, the driver may be deemed to be adaptable to the network card device. The disabling instruction, the enabling instruction, the mode setting instruction and the data interaction instruction can be set in the test program in advance, and when the test flow of the driver is triggered, the disabling instruction, the enabling instruction, the mode setting instruction and the data interaction instruction are sequentially determined through the test program, so that interaction is carried out with the hardware equipment according to the interaction instructions, and an interaction result is obtained.
Further, after the step S302, the method further includes: when a test result of test failure is obtained, deleting the driver program of the test failure from the mapping data under the preset driver library; and unloading the drive program which fails the test in the operating system.
It should be noted that, the driver with test failure is deleted from the preset driver library catalog, so as to avoid the driver with test failure from being tested for multiple times, thereby being capable of reaching the condition of ending the test of the driver, and the condition of ending the test is that the driver cannot be matched with other versions of device drivers from the preset driver library catalog.
Step S303: and when the test result of passing the test is obtained, unloading the drive program of passing the test in the operating system, and moving the drive program of passing the test to a temporary folder.
When the test is passed, determining a drive program passing the test under the preset drive library catalog, and moving the drive program from the preset drive library catalog to the temporary folder. At this time, the driver of the version which has not been tested is unloaded from the preset driver library catalog, and the operating system is notified to match with the drivers of other versions from the preset driver library catalog again, and the drivers are installed, tested and unloaded. If the test fails, deleting the driver of the version under the preset driver library catalog, unloading the driver of which the test fails under the preset driver library catalog, informing the operating system of matching the drivers of other versions under the preset driver library catalog again, and if the corresponding drivers cannot be matched under the preset driver library catalog, indicating that the drivers of all the versions are tested. At this time, the driver corresponding to the hardware device under the preset driver library is moved or deleted. After testing all versions of drivers corresponding to the hardware device, detecting the drivers in the temporary folder, selecting the latest release version of the driver as a target driver, and installing the target driver into an operating system. According to the embodiment, when the operating system provided with the target driver carries out operating system migration or restoration, the operating system presets no bloated data in the driver library catalog, so that performance reduction caused by overlarge migrated operating system is avoided.
The method comprises the steps of mapping hardware equipment of a target host into a virtual machine, and starting an operating system corresponding to a source host on the virtual machine; searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment; sequentially installing a plurality of driving programs in an operating system through a virtual machine; the hardware equipment is driven by the driver, and interaction is carried out with the hardware equipment, so that the driver is tested according to an interaction result; and when the test result of passing the test is obtained, unloading the drive program of passing the test in the operating system, moving the drive program of passing the test to a temporary folder, selecting a target drive program from the temporary folder, and installing the target drive program in the operating system to obtain the operating system with the target drive program. By the method, the hardware equipment of the target computer is mapped into the virtual machine, the operating system to be migrated or restored is started on the virtual machine, the mapping hardware equipment is subjected to driver matching on the operating system, the driver of the hardware equipment on the target computer can be normally used according to the installed driver for interactive testing, the target driver is installed in the operating system, the target driver is the driver which can normally use the equipment hardware of the target host and passes testing, the operating system is migrated or restored to the target host according to the operating system with the target driver, the migrated or restored operating system can normally use the hardware equipment of the target host without manually matching the correct driver, and the efficiency of migrating or restoring the operating system is improved.
In addition, the embodiment of the invention also provides a storage medium, wherein the storage medium is stored with a device driver verification program, and the device driver verification program realizes the steps of the device driver verification method when being executed by a processor.
Referring to fig. 5, fig. 5 is a block diagram showing the configuration of a first embodiment of the device driver verification apparatus according to the present invention.
As shown in fig. 5, a device driver verification apparatus according to an embodiment of the present invention includes:
the mapping module 10 is configured to map a hardware device of a target host to a virtual machine, and start an operating system corresponding to a source host on the virtual machine.
And the matching module 20 is configured to search a plurality of corresponding drivers under a preset driver library directory according to the hardware identifier corresponding to the hardware device.
And the test module 30 is configured to perform an operation environment test on the plurality of drivers in the operating system through the virtual machine, and when a test result passing the test is obtained, move the driver passing the test to a temporary folder.
And an installation module 40, configured to select a target driver from the temporary folder, and install the target driver in the operating system, so as to obtain an operating system in which the target driver is installed.
It should be understood that the foregoing is illustrative only and is not limiting, and that in specific applications, those skilled in the art may set the invention as desired, and the invention is not limited thereto.
The method comprises the steps of mapping hardware equipment of a target host into a virtual machine, and starting an operating system corresponding to a source host on the virtual machine; searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment; running environment tests are respectively carried out on a plurality of drivers in an operating system through a virtual machine, and when test results passing through the tests are obtained, the drivers passing through the tests are moved to a temporary folder; and selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver installed. By the method, the hardware equipment of the target computer is mapped into the virtual machine, the operating system to be migrated or restored is started on the virtual machine, and the mapping hardware equipment is subjected to matching and testing of the driving program on the operating system, so that the operating system with the target driving program is obtained, the target driving program is the driving program which passes the test and can normally use the equipment hardware of the target host, the operating system is migrated or restored according to the operating system with the target driving program, the operating system after migration or restoration can normally use the hardware equipment of the target host, the correct driving program is not required to be matched manually, and the efficiency of migrating or restoring the operating system is improved.
It should be noted that the above-described working procedure is merely illustrative, and does not limit the scope of the present invention, and in practical application, a person skilled in the art may select part or all of them according to actual needs to achieve the purpose of the embodiment, which is not limited herein.
In addition, technical details not described in detail in this embodiment may refer to the device driver verification method provided in any embodiment of the present invention, which is not described herein.
In an embodiment, the device driver verification apparatus further includes: an acquisition module;
the acquisition module is used for acquiring drivers of all versions corresponding to all hardware devices connected to the target host, generating a target drive library according to the drivers of all versions corresponding to all hardware devices, copying the target drive library into a virtual machine hard disk, and mapping data in the virtual machine hard disk to a preset drive library directory.
In an embodiment, the test module 30 is further configured to sequentially install the plurality of drivers in the operating system through the virtual machine, drive the hardware device through the drivers, interact with the hardware device to test the drivers according to the interaction result, unload the drivers passing the test in the operating system when the test result passing the test is obtained, and move the drivers passing the test to the temporary folder.
In an embodiment, the test module 30 is further configured to perform, according to a disable instruction, disable interaction on the hardware device through the driver, obtain a disable interaction result, perform, according to an enable instruction, enable interaction on the hardware device through the driver, obtain an enable interaction result, perform, according to a mode setting instruction, mode setting on the hardware device through the driver, receive feedback mode information, obtain a mode setting interaction result, send a data packet to the hardware device through the driver, receive a target data packet fed back by the hardware device, obtain a data interaction result, and test the driver according to the disable interaction result, the enable interaction result, the mode setting interaction result, and the data interaction result.
In an embodiment, the test module 30 is further configured to obtain a test result that the test passes when the disabled interaction result is disabled interaction normal, the enabled interaction result is enabled interaction normal, the mode setting interaction result is mode setting interaction normal, and the data interaction result is data interaction normal.
In an embodiment, the test module 30 is further configured to delete the driver with test failure from the mapping data under the preset driver library when the test result with test failure is obtained, and uninstall the driver with test failure in the operating system.
In an embodiment, the installation module 40 is further configured to detect whether the temporary folder includes a current driver corresponding to the hardware device, determine version information corresponding to the current drivers when the temporary folder includes a plurality of current drivers corresponding to the hardware device, and select, according to the version information, a target driver corresponding to a latest release version from the current drivers.
Furthermore, it should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. Read Only Memory)/RAM, magnetic disk, optical disk) and including several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (10)
1. A device driver verification method, the device driver verification method comprising:
mapping the hardware equipment of the target host into a virtual machine, and starting an operating system corresponding to the source host on the virtual machine;
searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment;
running environment tests are respectively carried out on the plurality of drivers in the operating system through the virtual machine, and when test results passing through the tests are obtained, the drivers passing through the tests are moved to a temporary folder;
and selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver.
2. The device driver verification method according to claim 1, wherein before searching for a corresponding plurality of drivers under a preset driver library directory according to the hardware identifier corresponding to the hardware device, the method further comprises:
collecting drivers of all versions corresponding to all hardware devices connected on a target host, and generating a target drive library according to the drivers of all versions corresponding to all hardware devices;
Copying the target drive library into a hard disk of a virtual machine;
and mapping the data in the hard disk of the virtual machine to a preset drive library directory.
3. The device driver verification method according to claim 1, wherein the running environment test is performed on the plurality of drivers in the operating system by the virtual machine, and when a test result of passing the test is obtained, moving the driver passing the test to a temporary folder includes:
sequentially installing the plurality of drivers in the operating system through the virtual machine;
the hardware equipment is driven by the driver to interact with the hardware equipment, so that the driver is tested according to an interaction result;
and when the test result of passing the test is obtained, unloading the drive program of passing the test in the operating system, and moving the drive program of passing the test to a temporary folder.
4. The device driver verification method of claim 3, wherein the driving the hardware device by the driver interacts with the hardware device to test the driver according to an interaction result, comprising:
Performing forbidden interaction on the hardware equipment through the driver according to the forbidden instruction to obtain a forbidden interaction result;
enabling interaction is carried out on the hardware equipment through the driver according to the enabling instruction, and enabling interaction results are obtained;
performing mode setting on the hardware equipment through the driver according to a mode setting instruction, and receiving feedback mode information to obtain a mode setting interaction result;
transmitting a data packet to the hardware equipment through the driver, and receiving a target data packet fed back by the hardware equipment to obtain a data interaction result;
and testing the driver according to the forbidden interaction result, the enabled interaction result, the mode setting interaction result and the data interaction result.
5. The device driver verification method of claim 4, wherein after the driver is tested according to the disable interaction result, the enable interaction result, the mode setting interaction result, and the data interaction result, the method further comprises:
and when the forbidden interaction result is the forbidden interaction normal, the enabled interaction result is the enabled interaction normal, the mode setting interaction result is the mode setting interaction normal and the data interaction result is the data interaction normal, obtaining a test result passing the test.
6. The device driver verification method of claim 3, wherein after the driver drives the hardware device and interacts with the hardware device to test the driver according to an interaction result, the method further comprises:
when a test result of test failure is obtained, deleting the driver program of the test failure from the mapping data under the preset driver library;
and unloading the drive program which fails the test in the operating system.
7. The device driver verification method according to any one of claims 1 to 6, wherein the selecting a target driver from the temporary folder includes:
detecting whether the temporary folder contains a current driver corresponding to the hardware equipment or not;
when the temporary folder contains a plurality of current drivers corresponding to the hardware equipment, determining version information corresponding to the current drivers;
and selecting a target driver corresponding to the latest release version from the plurality of current drivers according to the version information.
8. A device driver verification apparatus, characterized in that the device driver verification apparatus comprises:
The mapping module is used for mapping the hardware equipment of the target host into the virtual machine and starting an operating system corresponding to the source host on the virtual machine;
the matching module is used for searching a plurality of corresponding drivers under a preset driver library catalog according to the hardware identifier corresponding to the hardware equipment;
the test module is used for respectively carrying out running environment test on the plurality of drivers in the operating system through the virtual machine, and moving the drivers passing the test to a temporary folder when the test result passing the test is obtained;
and the installation module is used for selecting a target driver from the temporary folder, and installing the target driver in the operating system to obtain the operating system with the target driver.
9. A device driver verification device, the device comprising: a memory, a processor, and a device driver verification program stored on the memory and executable on the processor, the device driver verification program configured to implement the device driver verification method of any one of claims 1 to 7.
10. A storage medium having stored thereon a device driver verification program which when executed by a processor implements the device driver verification method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110740868.5A CN113485755B (en) | 2021-06-30 | 2021-06-30 | Device driver verification method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110740868.5A CN113485755B (en) | 2021-06-30 | 2021-06-30 | Device driver verification method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113485755A CN113485755A (en) | 2021-10-08 |
| CN113485755B true CN113485755B (en) | 2023-08-18 |
Family
ID=77937231
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110740868.5A Active CN113485755B (en) | 2021-06-30 | 2021-06-30 | Device driver verification method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113485755B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114676069B (en) * | 2022-05-30 | 2022-08-30 | 深圳市科力锐科技有限公司 | Kernel file testing method, device, equipment and storage medium |
| CN114691440B (en) * | 2022-06-01 | 2022-09-02 | 广州市高奈特网络科技有限公司 | Data extraction method and device of equipment, computer equipment and storage medium |
Citations (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101101562A (en) * | 2007-07-10 | 2008-01-09 | 北京大学 | Dummy machine external storage on-line migration method |
| CN101834860A (en) * | 2010-04-22 | 2010-09-15 | 北京交通大学 | Method for remote dynamic verification on integrality of client software |
| CN102609638A (en) * | 2011-12-22 | 2012-07-25 | 中国航天科工集团第二研究院七〇六所 | Xen virtual machine framework based on UEFI (unified extensible firmware interface) runtime service and implementation method thereof |
| CN103246534A (en) * | 2013-04-12 | 2013-08-14 | 深信服网络科技（深圳）有限公司 | Method and device for migrating operating system |
| CN103441900A (en) * | 2013-08-27 | 2013-12-11 | 上海新炬网络技术有限公司 | Centralization cross-platform automated testing system and control method thereof |
| CN104699615A (en) * | 2012-03-31 | 2015-06-10 | 北京奇虎科技有限公司 | System failure processing method and device |
| CN104715183A (en) * | 2013-12-13 | 2015-06-17 | ***通信集团公司 | Trusted verifying method and equipment used in running process of virtual machine |
| CN104732145A (en) * | 2015-03-31 | 2015-06-24 | 北京奇虎科技有限公司 | Parasitic course detection method and device in virtual machine |
| CN104834576A (en) * | 2015-04-30 | 2015-08-12 | 捷鼎国际股份有限公司 | Computer system for testing hardware device based on virtual machine and method thereof |
| US9135038B1 (en) * | 2010-05-28 | 2015-09-15 | Bromium, Inc. | Mapping free memory pages maintained by a guest operating system to a shared zero page within a machine frame |
| CN105592492A (en) * | 2015-12-18 | 2016-05-18 | 重庆邮电大学 | Platform and method for testing high-layer protocol stack consistency |
| CN106775928A (en) * | 2016-11-25 | 2017-05-31 | 国家电网公司 | A kind of virtual machine Autonomic Migration Framework system and method between isomery cloud platform |
| CN107220171A (en) * | 2016-03-22 | 2017-09-29 | 阿里巴巴集团控股有限公司 | The method of testing and device of a kind of virtual machine |
| US9792131B1 (en) * | 2010-05-28 | 2017-10-17 | Bromium, Inc. | Preparing a virtual machine for template creation |
| CN107463427A (en) * | 2017-06-29 | 2017-12-12 | 北京北信源软件股份有限公司 | The acquisition methods and device of a kind of VME operating system type and version |
| CN107656844A (en) * | 2017-09-14 | 2018-02-02 | 深圳市华云中盛科技有限公司 | The method and its system of virtual machine internal monitoring are realized based on virtualization serial ports passage |
| CN107992381A (en) * | 2017-12-11 | 2018-05-04 | 深圳市科力锐科技有限公司 | System reducing method, device, system, backup and reduction server and storage medium |
| CN108268307A (en) * | 2018-01-07 | 2018-07-10 | 长沙曙通信息科技有限公司 | A kind of Table top virtualizes live migration of virtual machine implementation method |
| CN110048875A (en) * | 2018-01-17 | 2019-07-23 | 华为技术有限公司 | A kind of method and apparatus of upgrading driving |
| CN110537171A (en) * | 2017-04-21 | 2019-12-03 | 雷蛇(亚太)私人有限公司 | Test equipment and method for being tested device driver software |
| CN111090439A (en) * | 2019-12-13 | 2020-05-01 | 苏州浪潮智能科技有限公司 | Mirror image generation method, device and equipment for Linux system of bare metal server |
| CN111176978A (en) * | 2018-11-09 | 2020-05-19 | 通用电气航空***有限公司 | Tool verification system and method for verifying rejected parts |
| CN112100050A (en) * | 2019-06-17 | 2020-12-18 | 百度（美国）有限责任公司 | Vulnerability-driven hybrid test system for application program |
| CN112433822A (en) * | 2020-12-07 | 2021-03-02 | 北京远为软件有限公司 | Method for realizing cross-domain network terminal virtual machine based on separation of three rights |
| CN112463631A (en) * | 2020-12-11 | 2021-03-09 | 苏州浪潮智能科技有限公司 | Chip driver testing method, device and equipment and readable storage medium |
| CN112764981A (en) * | 2021-01-22 | 2021-05-07 | 山东云海国创云计算装备产业创新中心有限公司 | Cooperative test system and method |
| CN112799785A (en) * | 2021-02-01 | 2021-05-14 | 糖纸伞科技有限公司 | Virtual machine cluster migration method, device, equipment and medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9286088B2 (en) * | 2009-03-09 | 2016-03-15 | Microsoft Technology Licensing, Llc | User interface for interaction with virtual machine |
-
2021
- 2021-06-30 CN CN202110740868.5A patent/CN113485755B/en active Active
Patent Citations (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101101562A (en) * | 2007-07-10 | 2008-01-09 | 北京大学 | Dummy machine external storage on-line migration method |
| CN101834860A (en) * | 2010-04-22 | 2010-09-15 | 北京交通大学 | Method for remote dynamic verification on integrality of client software |
| US9135038B1 (en) * | 2010-05-28 | 2015-09-15 | Bromium, Inc. | Mapping free memory pages maintained by a guest operating system to a shared zero page within a machine frame |
| US9792131B1 (en) * | 2010-05-28 | 2017-10-17 | Bromium, Inc. | Preparing a virtual machine for template creation |
| CN102609638A (en) * | 2011-12-22 | 2012-07-25 | 中国航天科工集团第二研究院七〇六所 | Xen virtual machine framework based on UEFI (unified extensible firmware interface) runtime service and implementation method thereof |
| CN104699615A (en) * | 2012-03-31 | 2015-06-10 | 北京奇虎科技有限公司 | System failure processing method and device |
| CN103246534A (en) * | 2013-04-12 | 2013-08-14 | 深信服网络科技（深圳）有限公司 | Method and device for migrating operating system |
| CN103441900A (en) * | 2013-08-27 | 2013-12-11 | 上海新炬网络技术有限公司 | Centralization cross-platform automated testing system and control method thereof |
| CN104715183A (en) * | 2013-12-13 | 2015-06-17 | ***通信集团公司 | Trusted verifying method and equipment used in running process of virtual machine |
| CN104732145A (en) * | 2015-03-31 | 2015-06-24 | 北京奇虎科技有限公司 | Parasitic course detection method and device in virtual machine |
| CN104834576A (en) * | 2015-04-30 | 2015-08-12 | 捷鼎国际股份有限公司 | Computer system for testing hardware device based on virtual machine and method thereof |
| CN105592492A (en) * | 2015-12-18 | 2016-05-18 | 重庆邮电大学 | Platform and method for testing high-layer protocol stack consistency |
| CN107220171A (en) * | 2016-03-22 | 2017-09-29 | 阿里巴巴集团控股有限公司 | The method of testing and device of a kind of virtual machine |
| CN106775928A (en) * | 2016-11-25 | 2017-05-31 | 国家电网公司 | A kind of virtual machine Autonomic Migration Framework system and method between isomery cloud platform |
| CN110537171A (en) * | 2017-04-21 | 2019-12-03 | 雷蛇(亚太)私人有限公司 | Test equipment and method for being tested device driver software |
| CN107463427A (en) * | 2017-06-29 | 2017-12-12 | 北京北信源软件股份有限公司 | The acquisition methods and device of a kind of VME operating system type and version |
| CN107656844A (en) * | 2017-09-14 | 2018-02-02 | 深圳市华云中盛科技有限公司 | The method and its system of virtual machine internal monitoring are realized based on virtualization serial ports passage |
| CN107992381A (en) * | 2017-12-11 | 2018-05-04 | 深圳市科力锐科技有限公司 | System reducing method, device, system, backup and reduction server and storage medium |
| CN108268307A (en) * | 2018-01-07 | 2018-07-10 | 长沙曙通信息科技有限公司 | A kind of Table top virtualizes live migration of virtual machine implementation method |
| CN110048875A (en) * | 2018-01-17 | 2019-07-23 | 华为技术有限公司 | A kind of method and apparatus of upgrading driving |
| CN111176978A (en) * | 2018-11-09 | 2020-05-19 | 通用电气航空***有限公司 | Tool verification system and method for verifying rejected parts |
| CN112100050A (en) * | 2019-06-17 | 2020-12-18 | 百度（美国）有限责任公司 | Vulnerability-driven hybrid test system for application program |
| CN111090439A (en) * | 2019-12-13 | 2020-05-01 | 苏州浪潮智能科技有限公司 | Mirror image generation method, device and equipment for Linux system of bare metal server |
| CN112433822A (en) * | 2020-12-07 | 2021-03-02 | 北京远为软件有限公司 | Method for realizing cross-domain network terminal virtual machine based on separation of three rights |
| CN112463631A (en) * | 2020-12-11 | 2021-03-09 | 苏州浪潮智能科技有限公司 | Chip driver testing method, device and equipment and readable storage medium |
| CN112764981A (en) * | 2021-01-22 | 2021-05-07 | 山东云海国创云计算装备产业创新中心有限公司 | Cooperative test system and method |
| CN112799785A (en) * | 2021-02-01 | 2021-05-14 | 糖纸伞科技有限公司 | Virtual machine cluster migration method, device, equipment and medium |
Non-Patent Citations (1)
| Title |
|---|
| 设备驱动非内核化通信架构的研究与实现;谭茁;翟高寿;;信息网络安全(第11期);第57-65页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113485755A (en) | 2021-10-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102736978B (en) | A kind of method and device detecting the installment state of application program | |
| CN107870968B (en) | Performing real-time updates to a file system volume | |
| CN113485755B (en) | Device driver verification method, device and storage medium | |
| US9081639B2 (en) | System and method for remotely re-imaging a computer system | |
| KR101636870B1 (en) | Method and apparatus for generating minimal boot image | |
| US20170286234A1 (en) | System and method for live virtual incremental restoring of data from cloud storage | |
| CN112612417B (en) | Data migration method, device, equipment and storage medium | |
| CN106843947B (en) | Method and device for processing code defects | |
| US7818557B2 (en) | Method for re-imaging a computer system | |
| CN110780942A (en) | System starting method and device, node equipment and computer readable storage medium | |
| CN113157347A (en) | Automatic probe deployment method, electronic device and storage medium | |
| US8949588B1 (en) | Mobile telephone as bootstrap device | |
| CN111399862A (en) | Batch installation method and device of Windows missing driver and computer equipment | |
| CN111090546A (en) | Method, device and equipment for restarting operating system and readable storage medium | |
| CN112579361B (en) | Backup data reconstruction method, device, equipment and storage medium | |
| CN112416379B (en) | Application program installation method and device, computing equipment and readable storage medium | |
| CN110941516B (en) | Operating system restoration method, device, equipment and storage medium | |
| CN113032183A (en) | System management method, device, computer equipment and storage medium | |
| CN116185571B (en) | Data migration method, device, storage medium and apparatus | |
| CN112579359A (en) | Business system reconstruction method, device, equipment and storage medium | |
| CN106933604B (en) | System upgrading method and device | |
| CN112882871B (en) | Host conflict detection method, device, equipment and storage medium | |
| US20230032581A1 (en) | Method and Apparatus for Processing Virtual Machine Component | |
| CN111090458B (en) | Gray release system and application release method based on gray release system | |
| CN113190244A (en) | Method and device for upgrading wireless module, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |