Drive installation method, apparatus, and cloud service system

Abstract

Embodiments of the present application disclose a drive installation method, device and cloud service system. A specific embodiment of the method comprises: in response to detecting that a trust certificate of a to-be-installed drive is not stored in a to-be-installed system, obtaining the trust certificate of the to-be-installed drive; importing the trust certificate into the to-be-installed system; and executing an installation command of the to-be-installed drive corresponding to the trust certificate. The embodiment can be applied to the field of cloud computing, and by pre-importing the trust certificate, the occurrence of a trust warning during Windows drive installation is prevented, so that the drive can be automatically installed through the installation command. As a necessary step for making a Windows image, the automatic installation of the Windows drive provides a prerequisite for the automation of the entire Windows image making process.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a driver installation method, apparatus, and cloud service system. Background Technology

[0002] Currently, Windows image driver installation is generally solved using the following two methods:

[0003] Manual method: Create a virtual machine from a Windows image, manually install the drivers, and then regenerate the image.

[0004] Offline automated installation can be achieved using the DISM (Deployment Image Servicing and Management) tool: Windows systems have the DISM image deployment tool, which can be used to call the relevant Windows API (Application Programming Interface) to add drivers to the driver store. When the image is booted, Plug and Play (PnP) will run, associating the drivers in the store with the corresponding devices on the computer.

[0005] Automated Windows driver installation refers to the process of automatically installing Windows drivers while the Windows system is running. This is achieved by analyzing the operating mechanism and installation process of Windows drivers and utilizing Windows class libraries, system tools, and some APIs. In cloud computing virtualization environments, creating Windows virtual machines requires installing the corresponding virtio driver. Because Windows images are constantly iterated, virtio driver versions are also continuously updated, necessitating frequent updates and reinstallations of Windows drivers. Summary of the Invention

[0006] This application provides a driver installation method, apparatus, and cloud service system.

[0007] In a first aspect, embodiments of this application provide a driver installation method, wherein the method includes: in response to detecting that the system to be installed does not store a trust certificate for the driver to be installed, obtaining a trust certificate for the driver to be installed; importing the trust certificate into the system to be installed; and executing an installation command for the driver to be installed corresponding to the trust certificate.

[0008] In some embodiments, the system to be installed is any one of the following: a Windows system or a Windows virtual machine.

[0009] In some embodiments, this application further includes: mounting the system to be installed after the driver is installed as an image file, so that the client can read and write access to the system to be installed.

[0010] In some embodiments, importing the trust certificate into the system to be installed includes: obtaining the trust certificate from the system with the driver to be installed already installed; and sending a storage instruction to the system to be installed so that the trust certificate is stored in a pre-configured trusted issuer storage area in the system to be installed.

[0011] Secondly, embodiments of this application provide a cloud service system, including a host machine and a virtual machine hosted on the host machine; the host machine, in response to determining that the virtual machine does not store a trust certificate for the driver to be installed, obtains the trust certificate for the driver to be installed, imports the trust certificate into the virtual machine, and executes the installation command for the driver to be installed corresponding to the trust certificate.

[0012] In some embodiments, importing the trust certificate into the virtual machine includes: obtaining the trust certificate from a system with the driver to be installed; and sending a storage instruction to the virtual machine to store the trust certificate in a pre-configured trusted issuer storage area within the virtual machine.

[0013] In some embodiments, the host machine mounts the virtual machine with the driver installed as an image file, enabling clients to read and write access to the virtual machine.

[0014] Thirdly, embodiments of this application provide a driver installation apparatus, wherein the apparatus includes: a certificate acquisition unit configured to acquire a trust certificate for the driver to be installed in response to detecting that no trust certificate for the driver to be installed is stored in the system to be installed; a certificate import unit configured to import the trust certificate into the system to be installed; and a driver installation unit configured to execute an installation command for the driver to be installed corresponding to the trust certificate.

[0015] In some embodiments, the system to be installed is any one of the following: a Windows system or a Windows virtual machine.

[0016] In some embodiments, the above apparatus further includes: a mounting unit configured to mount the system to be installed after the driver is installed as an image file, so that the client can read and write access to the system to be installed.

[0017] In some embodiments, the certificate import unit is further configured to: obtain a trust certificate from a system with the driver to be installed already installed; and send a storage instruction to the system to be installed so that the trust certificate is stored in a pre-configured trusted issuer storage area in the system to be installed.

[0018] Fourthly, embodiments of this application provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, it implements the method as described in any of the implementations of the first aspect.

[0019] Fifthly, embodiments of this application provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any implementation of the first aspect.

[0020] The driver installation method and apparatus provided in this application, in response to detecting that the system to be installed does not store a trust certificate for the driver to be installed, obtains the trust certificate for the driver to be installed; imports the trust certificate into the system to be installed; and executes the installation command for the driver to be installed corresponding to the trust certificate. By pre-importing the trust certificate, the occurrence of trust warnings during Windows driver installation is prevented, thus allowing drivers to be installed automatically via installation commands. This application overcomes the current limitation that unattended installation of Windows drivers can only be performed on the Windows platform, realizing unattended driver installation and configuration of Windows images on the Linux platform. As a necessary step in creating a Windows image, the automated installation of Windows drivers provides a prerequisite for automating the entire Windows image creation process. Moreover, driver installation can be performed while the Windows virtual machine is running, without the need to shut down the machine. Thus, driver installation and image configuration can be performed simultaneously, making unattended, customized configuration of Windows images on the Linux platform possible, effectively reducing the workload of image creation. Attached Figure Description

[0021] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0022] Figure 1 This is an exemplary system architecture diagram in which one embodiment of this application can be applied;

[0023] Figure 2 This is a flowchart of one embodiment of the driver installation method according to this application;

[0024] Figure 3 This is a schematic diagram illustrating an application scenario of the driver installation method according to this embodiment;

[0025] Figure 4 This is a flowchart of yet another embodiment of the driver installation method according to this application;

[0026] Figure 5This is a structural diagram of an embodiment of the cloud service system according to this application;

[0027] Figure 6 This is a structural diagram of one embodiment of the drive mounting device according to this application;

[0028] Figure 7 This is a schematic diagram of the structure of a computer system suitable for implementing the computer devices of the embodiments of this application. Detailed Implementation

[0029] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0030] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0031] In a typical configuration of this application, the terminal device and server device include one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0032] Computer-readable media include both permanent and non-permanent, removable and non-removable media, which can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media do not include non-transitory computer-readable media, such as modulated data signals and carrier waves.

[0033] Figure 1 An exemplary architecture 100 is shown that the driver installation method and apparatus of this application can be applied.

[0034] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0035] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to download the system and drivers to be installed. Terminal devices 101, 102, and 103 can have Windows or a Windows virtual machine installed.

[0036] Terminal devices 101, 102, and 103 can be hardware or software that supports network connectivity to provide various network services. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices that support the installation of Windows systems or Windows virtual machines, including but not limited to tablets, laptops, and desktop computers. When terminal devices 101, 102, and 103 are software, they can be installed in the aforementioned electronic devices. They can be implemented as, for example, multiple software programs or software modules used to provide Windows system or Windows virtual machine installation services, or as a single software program or software module. No specific limitations are imposed here.

[0037] Server 105 can be a server that provides various services, such as a database server that provides relevant installation data to terminal devices 101, 102, and 103. The database server can receive data query or download commands from the terminal devices and provide the corresponding data to the terminal devices, such as installation files related to the Windows system or Windows virtual machine.

[0038] It should be noted that a server can be either hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the server is software, it can be implemented as multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.

[0039] It should be understood that Figure 1 The number of terminal devices and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices and servers can be used.

[0040] Continue to refer to Figure 2The diagram illustrates a flow 200 of an embodiment of a driver installation method according to this application, the driver installation method comprising the following steps:

[0041] Step 201: In response to the detection that the system to be installed does not store a trust certificate for the driver to be installed, obtain the trust certificate for the driver to be installed.

[0042] In this embodiment, the system to be installed can be either a Windows system or a Windows virtual machine. Windows refers to the Microsoft Windows operating system, the most common computer operating system, characterized by good human-computer interaction, support for numerous applications, and strong hardware compatibility. A Windows virtual machine (VM) is a complete computer virtual system simulated by software, possessing full hardware system functionality and running in a completely isolated environment. The virtual system generates a completely new virtual image of the existing operating system, possessing the same functions as a real Windows system. After entering the virtual system, all operations are performed within this new, independent virtual system. Software can be installed and run independently, data can be saved, and it has its own independent desktop without affecting the real system. Furthermore, it is a type of operating system that allows flexible switching between the existing system and the virtual image.

[0043] In this embodiment, a Windows driver is any software component that observes or participates in the communication between the operating system and the device. The driver understands how to communicate with the device hardware to obtain data. After obtaining data from the device, the driver returns the data to the operating system, which then returns the data to the application. Generally, Windows drivers include the following categories: device function drivers, device filter drivers, software drivers, file system filter drivers, and file system drivers.

[0044] In this embodiment, the trust certificate refers to the trust certificate generated by the Windows system during the installation of the aforementioned driver. The Windows system has driver trust management and signing functions. When installing a driver from an untrusted vendor for the first time, the Windows system will pop up a warning window indicating that it does not trust that vendor's driver. Once the user confirms trust in that vendor's driver and adds it to the trust list, the warning window will no longer pop up. To ensure that the Windows system or Windows virtual machine trusts the driver to be installed and prevents the warning window from popping up again, the execution entity in this embodiment (e.g., Figure 1 The terminal device in the process (in response to detecting that the system to be installed does not have a trust certificate for the driver to be installed stored, obtains the trust certificate for the driver to be installed.)

[0045] Step 202: Import the trust certificate into the system to be installed.

[0046] In this embodiment, the trust certificate is imported into the system to be installed so that the system to be installed stores the trust certificate, indicating that the system to be installed has trusted the driver to be installed. In this way, the system to be installed will not pop up a driver trust warning window when installing the driver.

[0047] In some optional embodiments of this example, a trust certificate can be obtained from a system that has the driver to be installed already installed. This trust certificate is generated during the installation of the driver in the system with the driver already installed. After obtaining the trust certificate, the executing entity sends a storage instruction to the system to be installed, so that the trust certificate is stored in a pre-set trusted issuer storage area in the system to be installed. The storage of the trust certificate in the pre-set trusted issuer storage area in the system to be installed indicates that the system to be installed trusts the driver to be installed.

[0048] Step 203: Execute the installation command for the driver to be installed corresponding to the trusted certificate.

[0049] In this embodiment, the installation command for the driver corresponding to the trusted certificate can be executed using the pnputil.exe tool within the PowerShell environment. PowerShell is a command-line shell and scripting environment, and pnputil.exe is a driver installation tool for Windows systems.

[0050] In this embodiment, to prevent trust warning windows for the driver to be installed from popping up in the system to be installed, a trust certificate for the driver to be installed is obtained before installation, and the trust certificate is imported into the system to be installed to gain the system's trust in the driver to be installed. This eliminates trust warnings during driver installation on Windows systems or Windows virtual machines, allowing the driver to be installed automatically via installation commands.

[0051] Continue to refer to Figure 3This illustration schematically depicts an application scenario of the driver installation method according to this embodiment. User 301 wants to create a Windows virtual machine on terminal device 302, therefore, it needs to install the corresponding driver for the Windows virtual machine on terminal device 302. Terminal device 302 detects that the Windows virtual machine does not store a trust certificate for the driver. It is known that a Windows virtual machine is installed on terminal device 303, and that the driver for the Windows virtual machine on terminal device 302 is already installed in that Windows virtual machine. Therefore, user 301 finds the trust certificate for the driver in the Windows virtual machine on terminal device 303, imports the trust certificate into the Windows virtual machine on terminal device 301, and then user 301 sends a driver installation command to terminal device 302. Terminal device 302 executes the installation command for the driver to be installed corresponding to the trust certificate to install the driver.

[0052] Continue to refer to Figure 4 The illustration shows a schematic flow 400 of another embodiment of a driver installation method according to this application, the driver installation method including the following steps:

[0053] Step 401: In response to the detection that the system to be installed does not store a trust certificate for the driver to be installed, obtain the trust certificate for the driver to be installed.

[0054] In this embodiment, step 401 is performed in a similar manner to step 201, and will not be described again here.

[0055] Step 402: Import the trust certificate into the system to be installed.

[0056] In this embodiment, step 402 is performed in a similar manner to step 202, and will not be described again here.

[0057] Step 403: Execute the installation command for the driver to be installed corresponding to the trusted certificate.

[0058] In this embodiment, step 403 is performed in a similar manner to step 203, and will not be described again here.

[0059] Step 404: Mount the system to be installed after driver installation as an image file so that the client can read and write access to the system to be installed.

[0060] In this embodiment, mirroring is a file storage format and a type of redundancy. A mirror image is when data on one disk has an exact copy on another disk. Many files can be combined into a single image file. An image file is similar to a ZIP archive; it combines a specific series of files into a single file according to a certain format for easy download and use by users, such as a test version of an operating system or game. Image files not only have the "combination" function of ZIP archives, but their most important feature is that they can be recognized by specific software and directly burned to a CD. In fact, the concept of an image file can be expanded further; it can contain more information, such as system files, boot files, and partition table information. Thus, an image file can contain all the information of a partition or even an entire hard drive.

[0061] In this embodiment, mounting refers to a process by which the operating system makes computer files and directories on a storage device (such as a hard drive, CD-ROM, or shared resource) accessible to users through the computer's file system.

[0062] In this embodiment, the system to be installed has automatically installed the driver via the installation command, and the trust warning issue of the system to be installed regarding the driver has been resolved. Thus, as a necessary step in creating a Windows image, the automated installation of Windows drivers provides the prerequisite for automating the entire Windows image creation process.

[0063] In Linux platforms, the host machine and virtual machine typically communicate via SSH (Secure Shell) or WinRM (Windows Remote Management). When installing a driver, if the Windows virtual machine does not have the necessary trust certificate for the driver, a driver trust warning window will pop up, causing the Linux image creation tool to lose control of the Windows virtual machine. However, Linux is not a graphical user interface (GUI) operating system; therefore, the host machine running Linux cannot operate via a graphical interface.

[0064] The method provided in this embodiment can automatically install the driver to be installed and resolve the information alarm problem of the driver to be installed, realizing unattended driver installation and configuration of Windows images on the Linux platform. Based on this, the system to be installed after driver installation is mounted as an image file, allowing clients to read and write access to the system to be installed, thus enabling unattended creation of Windows image files on the Linux platform. Furthermore, the automatic installation process of the driver to be installed can be executed while the Windows virtual machine is running, without the need for shutdown.

[0065] from Figure 4 It can be seen from this that, with Figure 2 Compared to the corresponding embodiments, the driver installation method process 400 in this embodiment specifically illustrates that automated installation of the driver to be installed is part of realizing unattended creation of Windows images under the Linux platform. Automated driver installation provides a prerequisite for automating the entire creation process of Windows images.

[0066] Continue to refer to Figure 5 The present invention illustrates an embodiment 500 of a cloud service system according to the present application, the cloud service system including a host machine 501 and a virtual machine 502 hosted on the host machine.

[0067] In response to determining that the virtual machine 502 does not store a trust certificate for the driver to be installed, the host machine 501 obtains the trust certificate for the driver to be installed, imports the trust certificate into the virtual machine 502, and executes the installation command for the driver to be installed corresponding to the trust certificate.

[0068] In this embodiment, the host machine obtains a trust certificate from the system with the driver to be installed; and sends a storage instruction to the virtual machine so that the trust certificate is stored in the trusted issuer storage area pre-set in the virtual machine.

[0069] In this embodiment, the virtual machine with the driver installed is mounted as an image file so that the client can read and write access to the virtual machine.

[0070] Continue to refer to Figure 6 The present invention illustrates an embodiment 600 of a driver installation apparatus according to the present application, which includes: a certificate acquisition unit 601, a certificate import unit 602, a driver installation unit 603, and a mounting unit 604.

[0071] The certificate acquisition unit 601 is configured to acquire the trust certificate of the driver to be installed in response to the detection that the trust certificate of the driver to be installed is not stored in the system to be installed; the certificate import unit 602 is configured to import the trust certificate into the system to be installed; the driver installation unit 603 is configured to execute the installation command of the driver to be installed corresponding to the trust certificate; and the mounting unit 604 is configured to mount the system to be installed after the driver is installed as an image file so that the client can read and write access to the system to be installed.

[0072] In this embodiment, the system to be installed is any one of the following: a Windows system or a Windows virtual machine. The certificate import unit 602 is further configured to obtain a trust certificate from a system with the driver to be installed already installed; and to send a storage instruction to the system to be installed, so that the trust certificate is stored in a pre-set trusted issuer storage area in the system to be installed.

[0073] The following is for reference. Figure 7 It illustrates a device suitable for implementing embodiments of this application (e.g., Figure 1 The diagram shows the structure of the computer system 700 of the devices 101, 102, 103, and 105. Figure 7 The device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0074] like Figure 7 As shown, the computer system 700 includes a processor (e.g., CPU, Central Processing Unit) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the system 700. The processor 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0075] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0076] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by processor 701, it performs the functions defined in the methods of this application.

[0077] It should be noted that the computer-readable medium of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0078] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0079] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0080] The units described in the embodiments of this application can be implemented in software or hardware. The described units can also be located in a processor; for example, it can be described as: a processor including a certificate acquisition unit, a certificate import unit, a driver installation unit, and a mounting unit. The names of these units do not necessarily limit the unit itself; for example, the certificate acquisition unit can also be described as "in response to detecting that the system to be installed does not store a trust certificate for the driver to be installed, acquiring the trust certificate for the driver to be installed."

[0081] In another aspect, this application also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the computer device to: in response to detecting that a trust certificate for the driver to be installed is not stored in the system to be installed, obtain a trust certificate for the driver to be installed; import the trust certificate into the system to be installed; and execute the installation command for the driver to be installed corresponding to the trust certificate.

[0082] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method of driving installation, wherein, The method comprises: in response to detecting that a trust certificate of a to-be-installed driver is not stored in a to-be-installed system, acquiring the trust certificate of the to-be-installed driver from a system in which the to-be-installed driver is installed, wherein the trust certificate is generated based on a confirmation operation received for a trust warning window of the to-be-installed driver when the system in which the to-be-installed driver is installed installs the to-be-installed driver; sending a storage instruction to the to-be-installed system to store the trust certificate in a pre-set trusted issuer storage area in the to-be-installed system, so that the to-be-installed system no longer pops up the trust warning window for the to-be-installed driver when installing the to-be-installed driver, to prevent a mirror making tool of a Linux operating system in a host machine from losing control over a Windows operating system in a virtual machine as the to-be-installed system; executing an installation command of the to-be-installed driver corresponding to the trust certificate by a pnputil.exe tool in a powershell environment; mounting the to-be-installed system after installing the driver as a mirror file to realize automation of a mirror making process.

2. The method of claim 1, wherein the to-be-installed system is any one of a Windows system and a Windows virtual machine.

3. A cloud service system comprising a host machine and a virtual machine hosted on the host machine; the host machine, in response to determining that a trust certificate of a to-be-installed driver is not stored in the virtual machine, acquires the trust certificate of the to-be-installed driver from a system in which the to-be-installed driver is installed, sends a storage instruction to a to-be-installed system to store the trust certificate in a pre-set trusted issuer storage area in the virtual machine, so that the to-be-installed system no longer pops up a trust warning window for the to-be-installed driver when installing the to-be-installed driver, to prevent a mirror making tool of a Linux operating system in a host machine from losing control over a Windows operating system in a virtual machine as the to-be-installed system, and executes an installation command of the to-be-installed driver corresponding to the trust certificate by a pnputil.exe tool in a powershell environment; mounting the to-be-installed system after installing the driver as a mirror file to realize automation of a mirror making process; wherein the trust certificate is generated based on a confirmation operation received for a trust warning window of the to-be-installed driver when the system in which the to-be-installed driver is installed installs the to-be-installed driver.

4. A drive mounting device wherein, The apparatus comprises: a certificate acquisition unit configured to, in response to detecting that a trust certificate of a to-be-installed driver is not stored in a to-be-installed system, acquire the trust certificate of the to-be-installed driver from a system in which the to-be-installed driver is installed, wherein the trust certificate is generated based on a confirmation operation received for a trust warning window of the to-be-installed driver when the system in which the to-be-installed driver is installed installs the to-be-installed driver; The certificate importing unit is configured to send a storage instruction to the to-be-installed system to store the trust certificate into a pre-set trusted issuer storage area of the to-be-installed system, so that the to-be-installed system no longer pops up a trust warning window for the to-be-installed driver when installing the to-be-installed driver, to prevent the image making tool of the Linux operating system in the host computer from losing control over the Windows operating system in the virtual machine as the to-be-installed system; The driver installing unit is configured to execute an installation command of the to-be-installed driver corresponding to the trust certificate through a pnputil.exe tool in a powershell environment; The mounting unit is configured to mount the to-be-installed system after installing the driver as an image file to realize automation of an image file making process.

5. The apparatus of claim 4, wherein The to-be-installed system is any one of the following: a Windows system, a Windows virtual machine.

6. A computer readable medium having stored thereon a computer program, wherein, The program, when executed by a processor, implements the method of any one of claims 1-2.

7. An electronic device, comprising: one or more processors; a memory device having one or more programs stored thereon, when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any one of claims 1-2.

Images