CN106325859B - Method and server for installing driver - Google Patents

Method and server for installing driver Download PDF

Info

Publication number
CN106325859B
CN106325859B CN201610670063.7A CN201610670063A CN106325859B CN 106325859 B CN106325859 B CN 106325859B CN 201610670063 A CN201610670063 A CN 201610670063A CN 106325859 B CN106325859 B CN 106325859B
Authority
CN
China
Prior art keywords
virtual machine
host
machine
package
driver
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
Application number
CN201610670063.7A
Other languages
Chinese (zh)
Other versions
CN106325859A (en
Inventor
张亚林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
XFusion Digital Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201610670063.7A priority Critical patent/CN106325859B/en
Publication of CN106325859A publication Critical patent/CN106325859A/en
Application granted granted Critical
Publication of CN106325859B publication Critical patent/CN106325859B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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
    • 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/45545—Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox

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)
  • Stored Programmes (AREA)

Abstract

The invention discloses a method for installing a driver and a server, wherein the method is applied to the server, a host machine and at least one virtual machine are operated in the server, and the method comprises the following steps: the host machine acquires a plurality of drive packages; the host machine selects a drive package of the host machine and a drive package of the at least one virtual machine from the plurality of drive packages, wherein the drive package of the host machine and the drive package of the at least one virtual machine are compatible; the host machine installs a driver package of the host machine on the host machine; the host machine stores the driver package of the at least one virtual machine on the host machine, and the driver package of the at least one virtual machine is used for controlling the at least one virtual machine to install the driver package of the at least one virtual machine by the host machine. The method for installing the driver and the server can simultaneously upgrade the drivers of the host machine and the virtual machine, thereby ensuring that the drivers of the host machine and the virtual machine are compatible.

Description

Method and server for installing driver
Technical Field
The present invention relates to the field of information technology, and more particularly, to a method and server for installing a driver.
Background
With the rapid development of Network function Virtualization (NFV for short) technology, Single Root Virtualization (SR-IOV for short), and Virtualization for I/O (VT-D for short) technologies are increasingly widely used in solutions of Virtualization scenarios. A typical application scenario is a network card supporting SR-IOV. The SR-IOV network card means: a Physical Function (abbreviated as "PF") of the network card is used in a Host operating System (abbreviated as "Host os") corresponding to the Host, and a virtual Function (abbreviated as "VF") of the network card is used in a Guest operating System (abbreviated as "Guest os") corresponding to the virtual machine. If the technology of the SR-IOV network card is adopted, the network performance is the highest, but simultaneously, a problem is also caused: the problem of version matching exists in the drivers of the network cards in the virtual machine and the host machine.
At present, the mainstream commercial network card cannot be used for realizing the front-back compatibility of PF (power factor) network card drive and VF network card drive. In the prior art, drivers are installed on the basis of independent upgrade of a host machine or a virtual machine. When the host machine or the virtual machine is upgraded independently, the problem of incompatibility of the drive versions occurs, so that the network between the host machine and the virtual machine is not communicated, and normal communication cannot be realized.
Disclosure of Invention
The embodiment of the invention provides a method for installing a driver and a server, which can simultaneously upgrade the drivers of a host machine and a virtual machine, thereby ensuring that the drivers of the host machine and the virtual machine are compatible.
In a first aspect, a method for installing a driver is provided, where the method is applied to a server in which a host and at least one virtual machine run, and the method includes:
the host machine acquires a plurality of drive packages;
the host machine selects a drive package of the host machine and a drive package of the at least one virtual machine from the plurality of drive packages, wherein the drive package of the host machine and the drive package of the at least one virtual machine are compatible;
the host machine installs a driver package of the host machine on the host machine;
the host machine stores the driver package of the at least one virtual machine on the host machine, and the driver package of the at least one virtual machine is used for controlling the at least one virtual machine to install the driver package of the at least one virtual machine by the host machine.
In the embodiment of the present invention, the host selects the driver package of the host and the driver package of the at least one virtual machine from the plurality of driver packages, wherein the driver package of the host and the driver package of the at least one virtual machine are compatible, then installs the driver package of the host on the host, and saves the driver package of the at least one virtual machine, and the driver package of the at least one virtual machine is used for the host to control the at least one virtual machine to install the driver package of the at least one virtual machine, so that the drivers of the host and the virtual machine can be upgraded or installed at the same time, thereby ensuring that the drivers of the host and the virtual machine are compatible.
Optionally, in some possible implementations, the plurality of driver packages are compatible or incompatible, and the driver package of the host machine and the driver package of the at least one virtual machine selected by the host machine from the plurality of driver packages are compatible.
In some possible implementations, the method further includes:
after the driver package of the host machine is validated and before each of the at least one virtual machine is started, the host machine saves the driver package of the at least one virtual machine to the virtual device of each of the at least one virtual machine.
Here, after the driver package is validated and before each of the at least one virtual machine is started, the host machine saves the driver package of the at least one virtual machine into the virtual device of each of the at least one virtual machine, so that each of the at least one virtual machine can necessarily scan the driver package of the at least one virtual machine when scanning the virtual device, so that the host machine can control the at least one virtual machine to install or upgrade the driver package.
Optionally, in some possible implementations, the method further includes:
after the driver package of the host takes effect, the host receives a notification message from a user, wherein the notification message is used for indicating a first virtual machine in the at least one virtual machine to install the driver package;
and the host machine stores the drive package of the at least one virtual machine into the virtual equipment of the first virtual machine according to the notification message.
Therefore, after the driver package takes effect, the host machine may receive a notification message of a user, where the notification message is used to indicate a first virtual machine installation driver in the at least one virtual machine, and then store the driver package of the at least one virtual machine into a virtual device of the first virtual machine according to the notification message, so that the first virtual machine can find its own driver package to install or upgrade the driver.
In some possible implementations, the method further includes:
the host machine controls the at least one virtual machine to start, and the driver package of the at least one virtual machine is used for installing each virtual machine in the at least one virtual machine when the virtual machine starts.
Here, the host machine controls the at least one virtual machine to start, so that each virtual machine in the at least one virtual machine is installed or upgraded with the driver package when being started, and the host machine controls the at least one virtual machine to be installed or upgraded uniformly, thereby ensuring that the drivers of the host machine and the virtual machines are compatible.
In some possible implementations, the method further includes:
the host adds identification information to the drive package of each virtual machine in the drive packages of the at least one virtual machine, wherein the identification information is used for each virtual machine in the at least one virtual machine to select the drive package according to the identification information.
The host may add identification information to the driver package of each of the at least one virtual machine driver package, where the identification information is used for each of the at least one virtual machine to be able to select or identify a corresponding driver package. Alternatively, the identification information may be a kernel version number of the virtual machine or other information having an identification function.
In some possible implementations, the method further includes:
when each virtual machine in the at least one virtual machine is started, running a preconfigured scanning tool to scan virtual equipment of each virtual machine;
and if each virtual machine in the at least one virtual machine scans the drive package corresponding to each virtual machine in the virtual equipment of each virtual machine, installing the drive package corresponding to each virtual machine.
Here, each of the at least one virtual machine may run a preconfigured scan tool to scan the virtual devices of each virtual machine at startup. If the driver package corresponding to each virtual machine is scanned in the virtual device of each virtual machine, each virtual machine in the at least one virtual machine can install the driver package corresponding to each virtual machine, so that the drivers of the host machine and the virtual machine are compatible.
Optionally, the method further comprises:
each virtual machine in the at least one virtual machine receives trigger information from a user;
and each virtual machine in the at least one virtual machine is started according to the trigger information.
Each virtual machine in the at least one virtual machine can perform a restart or reset operation according to the trigger information, and then invoke a scanning tool to scan the virtual device of each virtual machine in the at least one virtual machine, so as to find the driver package of each virtual machine in the at least one virtual machine in the virtual device for installation.
In a second aspect, a server is provided that includes a host machine and at least one virtual machine. The server is configured to perform the method of the first aspect or any possible implementation manner of the first aspect.
In a third aspect, a computer-readable medium is provided for storing a computer program comprising instructions for performing the first aspect or the method in any possible implementation of the first aspect.
In a fourth aspect, a host is provided, where the host includes a host and at least one virtual machine, and the host is configured to perform the method of the first aspect or any possible implementation manner of the first aspect.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments of the present invention will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1A is a schematic diagram of an NFV architecture according to an embodiment of the invention.
Fig. 1B is a schematic diagram of a network card supporting a host machine and a virtual machine.
Fig. 2 is a schematic flow chart of a method of installing a driver according to an embodiment of the present invention.
Fig. 3 is a schematic flow chart of a method of installing a driver according to another embodiment of the present invention.
Fig. 4 is a schematic diagram of an example of mounting a drive according to an embodiment of the present invention.
Fig. 5 is a schematic block diagram of a server according to an embodiment of the present invention.
Fig. 6 is a schematic structural diagram of a device of a host according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The technical scheme of the invention can be applied to a virtualized scene. The Virtualization technology specifically includes Network function Virtualization (NFV for short) technology in telecommunication function Virtualization. NFV by borrowing IT virtualization technology, many types of network devices can be incorporated into industry standards, such as servers, switches, and storage, and can be deployed in data centers, network nodes, or user homes. This requires that the network functions be implemented in software and run on a series of industry standard server hardware that can be migrated, instantiated, deployed as needed at different locations on the network without the need to install new equipment. The ultimate goal of NFV is to replace those proprietary, dedicated network element devices of the communication network by x86 server, storage and switching devices based on industry standards.
For example, fig. 1A shows a schematic architecture diagram of the NFV system 100. The NFV system 100 may be used in various networks, such as implemented in a data center network, operator network, or local area network. The NFV System 100 includes an NFV Management and Orchestration System (NFV MANO)101, an NFV Infrastructure layer (NFVI) 130, a plurality of Virtual Network Functions (VNFs) 108, a plurality of Element Management (EM) 122, a Network service, a VNF and Infrastructure Description (VNF and Infrastructure Description)126, and an Operation Support Management System (Operation-Support System/Business Support System, OSS/BSS) 124. Among other things, the NFV management and orchestration system 101 includes a NFV Orchestrator (NFV editor, NFVO)102, one or more VNFMs (VNFManager, VNFM)104, and a Virtualized Infrastructure Manager (VIM) 106. NFVI 130 includes computing hardware 112, storage hardware 114, network hardware 116, Virtualization Layer (Virtualization Layer), virtual computing 110, virtual storage 118, and virtual network 120.
The NFV management and orchestration system (NFV MANO)101 is used to perform monitoring and management of VNF108 and NFVI 130. The NFVO 102 may implement network services (e.g., L2 and L3 VPN services) on the NFVI 130, and may also perform resource-related requests from one or more VNFMs 104, send configuration information to the VNFMs 104, and collect state information of the VNFs 108. Additionally, NFVO 102 may communicate with VIM 106 to enable allocation and/or reservation of resources, as well as exchange configuration and status information for virtualized hardware resources. The VNFM 104 may manage one or more VNFs 108. The VNFM 104 may perform various management functions such as instantiating, updating, querying, scaling, and/or terminating the VNF108, among others. VIM 106 may perform functions for resource management, such as managing allocation of infrastructure resources (e.g., adding resources to virtual containers) and operational functions (e.g., collecting NFVI fault information). The VNFM 104 and VIM 106 may communicate with each other for resource allocation and exchange configuration and status information for virtualized hardware resources.
The NFVI 130 includes hardware resources, software resources, or a combination of both to complete the deployment of the virtualized environment. In other words, the hardware resources and virtualization layer are used to provide virtualized resources, e.g., as virtual machines and other forms of virtual containers, for VNF 108. The hardware resources include computing hardware 112, storage hardware 114, and network hardware 116. The computing hardware 112 may be commercially available hardware and/or custom hardware to provide processing and computing resources. The storage hardware 114 may be storage capacity provided within a network or storage capacity residing within the storage hardware 114 itself (local storage located within a server). In one implementation, the resources of the computing hardware 112 and the storage hardware 114 may be pooled together. The network hardware 116 may be a switch, a router, and/or any other network device configured with switching functionality. The network hardware 116 may span multiple domains and may include multiple networks interconnected by one or more transport networks.
A virtualization layer within NFVI 130 may abstract hardware resources from the physical layer and decouple VNF108 to provide virtualized resources to VNF 108. The virtual resource layer includes virtual compute 110, virtual memory 118, and virtual network 120. Virtual compute 110 and virtual storage 118 may be provided to VNF108 in the form of virtual machines, and/or other virtual containers. For example, one or more VNFs 108 may be deployed on one Virtual Machine (Virtual Machine). The virtualization layer abstracts the network hardware 116 to form a Virtual network 120, and the Virtual network 120 may include Virtual switches (Virtual switches) that are used to provide connections between Virtual machines and other Virtual machines. In addition, the transport network in the network hardware 116 may be virtualized using a centralized control plane and a separate forwarding plane (e.g., software defined network, SDN). As shown in fig. 1A, VNFM 104 may interact with VNF108 and EM 122 to enable management of the VNF's lifecycle and exchange configuration and state information. VNF108 may be configured to virtualize at least one network function performed by one physical network device. For example, in one implementation, the VNF108 may be configured to provide functionality provided by different network elements in the IMS network, such as network functionality of a P-SCSCF, S-CSCF, or HSS. EM 122 is configured to manage one or more VNFs 108.
In the embodiment of the present invention, an operating System running virtual machine software may be referred to as a host operating System (hostperation System, hostpos), where the hostpos corresponds to a host; the operating System running in the virtual machine may be referred to as a Guest operating System (Guest os), where the Guest os corresponds to the virtual machine. One host may manage multiple virtual machines. For example, in practical applications, a user windows operating system may create a plurality of Linux systems.
For example, fig. 1B shows a schematic diagram of a network card supporting a host machine and a virtual machine. The host machine in fig. 1B may correspond to NFVI 130 in fig. 1A, and the virtual machine may correspond to VNF108 in fig. 1A. The network card may be a network card supporting single root I/O virtualization (SR-IOV for short). The SR-IOV technology is a virtualization solution based on hardware, and can improve performance and scalability. The SR-IOV standard allows for efficient sharing of a Peripheral Component Interconnect Express (PCIe) device between virtual machines, and it is implemented in hardware, achieving I/O performance comparable to native performance. The SR-IOV specification defines a new standard according to which new devices are created that allow virtual machines to be connected directly to I/O devices. As shown in fig. 1B, the Network Card or the Network adapter (Network Interface Card, NIC) includes one PF and 3 VFs, where when a host (hosts) needs to upgrade a driver, a driver package (HostDrv) is installed by using the PF in the Network Card; when the virtual machine (Guestos) needs to upgrade the driver, installing the driver package (GuestDrv) by using the VF in the network card. For example, fig. 1B shows that one host corresponds to two virtual machines.
In the embodiment of the present invention, the driver package may be understood as a file package required for installing or upgrading a driver. The driver may be referred to as "driver" for short, and for brevity, the description below uses "driver" instead of "driver".
In order to ensure that the driver versions of the host machine and the virtual machine are matched or compatible, the driver versions of the host machine and the virtual machine need to be installed or upgraded. If the drive versions of the host machine and the virtual machine are upgraded simultaneously, a plurality of products are involved, and the actual operation is very difficult. Therefore, the invention proposes a solution: the host selects a compatible driver package of the host and a driver package of at least one virtual machine, then the host installs or upgrades the driver of the host according to the driver package of the host, and the host needs to control the at least one virtual machine to install or upgrade after upgrading. In other words, the host machine has contracted the process of installing or upgrading the driver for the virtual machine and the host machine. Therefore, the compatibility of the installation or upgrade drive version of the virtual machine and the host machine can be ensured.
It should be understood that the technical solution of the present invention provides a method for solving the compatibility dependency between a host and a virtual machine, but the method is not limited to solving the problem of driver compatibility of the host and the virtual machine, and may also be applied to other reasonable scenarios, for example, the present invention is not limited to the host and the virtual machine in the NFV scenario shown in fig. 1A, and may also be applied to the host and the virtual machine in other scenarios, such as a Software Defined Network (SDN) scenario, and the like, which is not limited thereto.
FIG. 2 shows a schematic flow diagram of a method 200 of installing a driver according to an embodiment of the invention. The method of fig. 2 is applied to a server, and the method is performed by the server, where a host and at least one virtual machine are running, for example, the host may correspond to NFVI 130 in fig. 1A, and the at least one virtual machine may correspond to VNF108 in fig. 1A. As shown in fig. 2, the method 200 includes:
s210, the host machine acquires a plurality of drive packages;
alternatively, the plurality of driver packages may exist in a driver package provided by a user.
For example, the host may obtain a plurality of driver packages provided or released by the user, for example, a user-provided driver package PackageA, which includes a hostos driver package (hostdva) and a plurality of gustos driver packages (gustdva), where the gustdva includes a plurality of gustos drivers, such as gustdva 1, gustdva 2, gustdva 3 …, and the like. Alternatively, multiple driver packages provided by the user may or may not be compatible.
S220, the host machine selects a drive package of the host machine and a drive package of the at least one virtual machine from the plurality of drive packages, wherein the drive package of the host machine and the drive package of the at least one virtual machine are compatible;
specifically, the host may select or screen the acquired multiple driver packages to obtain the driver package of the host and the driver package of the at least one virtual machine. And the screened drive package of the host machine is compatible with the drive package of the at least one virtual machine.
That is, the driver packages acquired by the host may be compatible or incompatible, and the driver packages obtained after the host screening are compatible.
Optionally, after the host obtains the plurality of driver packages provided by the user, the host may filter the plurality of driver packages to obtain the compatible driver packages. For example, the host machine divides the screened drive packages into two types, where the type a is the drive package of the host machine, and the type B includes the drive packages of multiple virtual machines that need to be supported.
Optionally, the host machine marks the driver package of at least one virtual machine according to the kernel version numbers corresponding to different virtual machines.
S230, the host machine installs the driver package of the host machine on the host machine;
s240, the host machine stores the driver package of the at least one virtual machine on the host machine, where the driver package of the at least one virtual machine is used for the host machine to control the at least one virtual machine to install the driver package of the at least one virtual machine.
Specifically, the host machine obtains the driver package of the host machine and the driver package of the at least one virtual machine, and the driver package of the host machine and the driver packages of the plurality of virtual machines are compatible. And then, the host machine is installed according to the drive package of the host machine, and the drive package of the at least one virtual machine is stored, wherein the drive package of the at least one virtual machine is used for controlling the at least one virtual machine to install the drive package of the at least one virtual machine by the host machine. Here, the purpose of the host machine holding the driver package of the at least one virtual machine is to: the host machine can control the at least one virtual machine to install the drive package of the at least one virtual machine according to the drive package of the at least one virtual machine, so that the host machine and the at least one virtual machine can be upgraded or installed uniformly, and the compatibility of the drives of the host machine and the virtual machine is guaranteed. In other words, the upgrading or installation of the drivers of the host machine and the virtual machine are controlled or responsible by the host machine, and the virtual machine does not need to independently upgrade the drivers.
Optionally, when one of the at least one virtual machine (for example, the first virtual machine) needs to be upgraded, the host may insert the at least one virtual driver package into the first virtual machine that needs to be upgraded. In this way, the first virtual machine may search for the driver package of the corresponding first virtual machine in the driver package of the at least one virtual machine, so as to perform installation according to the driver package of the first virtual machine.
In the embodiment of the present invention, the host installs the driver package of the host on the host, and stores the driver package of the at least one virtual machine on the host, specifically for example: the host machine installs HostDrvA in PackageA into a drive directory of the host machine; meanwhile, the host machine saves GuestDrvA in PackageA to a certain directory of the host machine.
In the embodiment of the present invention, the host may manage the driver packages of the plurality of corresponding virtual machines thereon, and may store the driver packages of the plurality of virtual machines on the host.
It should be understood that the driver package may be published by the user or downloaded from another channel, for example, the user may provide the driver package to the host or the server where the host is located by downloading the driver package of the driver to be upgraded, so as to facilitate the upgrade operation of the driver performed by the host.
Therefore, in the method for installing a driver according to the embodiment of the present invention, a host selects a driver package of the host and a driver package of the at least one virtual machine from the plurality of driver packages, where the driver package of the host and the driver package of the at least one virtual machine are compatible, then installs the driver package of the host on the host, and saves the driver package of the at least one virtual machine, and the driver package of the at least one virtual machine is used for the host to control the at least one virtual machine to install the driver package of the at least one virtual machine, so that drivers of the host and the virtual machine can be upgraded or installed at the same time, thereby ensuring that the drivers of the host and the virtual machine are compatible.
Optionally, the host may receive an instruction sent by a user, where the instruction is used to instruct or notify the host to perform a driver upgrade operation. And then, the host machine carries out drive upgrading or installation operation according to the instruction.
Optionally, as an embodiment, as shown in fig. 3, the method 200 further includes:
s250, after the driver package of the host takes effect and before each of the at least one virtual machine is started, the host saves the driver package of the at least one virtual machine to a virtual device of each of the at least one virtual machine.
Specifically, after the driver package of the host machine is validated and before each virtual machine in the at least one virtual machine is started, the driver package of the at least one virtual machine can be actively saved or inserted into the virtual device of each virtual machine in the at least one virtual machine, so that each virtual machine in the at least one virtual machine can necessarily scan the driver package of the at least one virtual machine when scanning the virtual device. The virtual device includes a virtual optical drive or a virtual optical disc. Then, at least one virtual machine can be installed or upgraded according to the drive package of at least one virtual machine stored by the host machine. Therefore, after the host machine is installed or upgraded, the host machine and the at least one virtual machine can be ensured to be installed or upgraded uniformly, and the problems that the host machine and the at least one virtual machine cannot be upgraded uniformly and the versions are inconsistent when the host machine and the at least one virtual machine are installed or upgraded are solved.
Optionally, as an embodiment, the method 200 further includes:
the host machine controls the at least one virtual machine to start, and the driver package of the at least one virtual machine is used for installing each virtual machine in the at least one virtual machine when the virtual machine starts.
Specifically, the host can control at least one virtual machine to start, wherein the driver package of the at least one virtual machine is used for installing each virtual machine in the at least one virtual machine at the starting time. For example, in a specific implementation, a controller or a switch may be disposed on the host, and the controller or the switch is used for controlling the host to control the virtual machine to perform drive installation or upgrade following the host. Specifically, for example, when the switch is turned on, the host machine controls the at least one virtual machine to start, and goes to the virtual device of the at least one virtual machine, and inserts the driver package of the at least one virtual machine, so that each virtual machine in the at least one virtual machine installs or upgrades the driver when starting; when the switch is off, the host machine does not perform this operation.
Therefore, the host machine controls the start of the at least one virtual machine, saves the drive package of the at least one virtual machine to the at least one virtual machine, and can upgrade or install the drives of the host machine and the virtual machine at the same time, so that the drives of the host machine and the virtual machine are compatible.
Optionally, as an embodiment, the method 200 further includes:
after the driver package of the host machine is effective, the host machine receives a notification message from a user, wherein the notification message is used for indicating a first virtual machine in the at least one virtual machine to install a driver;
and the host machine stores the drive package of the at least one virtual machine into the virtual equipment of the first virtual machine according to the notification message.
In particular, the host may also receive a notification message from a user indicating that a certain virtual machine (e.g., the first virtual machine) of the at least one virtual machine needs to install or upgrade a driver. After receiving the notification message, the host machine may store the previously stored driver package of at least one virtual machine in the virtual device of the first virtual machine, so that the first virtual machine can call a suitable driver package for installation, thereby satisfying the compatibility of the driver between the host machine and the virtual machine.
Alternatively, the first virtual machine may be any user-specified virtual machine that requires the installation or upgrade of a driver. It should be understood that the "first virtual machine" is introduced here for convenience of description only and does not limit the present invention.
In the embodiment of the present invention, the notification message may be an instruction or a command issued by a user, which is not limited herein.
Optionally, as an embodiment, the method 200 further includes:
the host adds identification information to the drive package of each virtual machine in the drive packages of the at least one virtual machine, wherein the identification information is used for each virtual machine in the at least one virtual machine to select the drive package according to the identification information.
Specifically, the host may add identification information to the driver package of each of the at least one virtual machine driver package, where the identification information is used for each of the at least one virtual machine to be able to select or identify the corresponding driver package. For example, the host adds identification information to a drive package of a plurality of virtual machines to be supported in the drive GuestDrvA of at least one virtual machine: GuestDrvA Operating System (OS) version 1, GuestDrvA OS version 2, GuestDrvA OS version 3 …, etc., the identification information indicating the type of drive package and/or Operating System (OS) version number. The driver package corresponding to the first virtual machine is GuestDrvA OS version 1, the driver package corresponding to the second virtual machine is GuestDrvA OS version 2, the driver package corresponding to the third virtual machine is GuestDrvA OS version 3 …, and the like. For example, the first virtual machine may find the driver package GuestDrvA OS version 1 corresponding to the first virtual machine according to the OS version number added by the host, and install or upgrade the driver according to the GuestDrvA OS version 1.
It should be understood that the identification information may be information having an identification function, such as a kernel version number, an ID number, and the like of the virtual machine, and is not limited thereto.
It should also be understood that the host may know the kernel version number of each of the at least one virtual machine.
Therefore, in the method for installing a driver according to the embodiment of the present invention, a host selects a driver package of the host and a driver package of the at least one virtual machine from a plurality of driver packages, where the driver package of the host and the driver package of the at least one virtual machine are compatible, then installs the driver package of the host on the host, and saves the driver package of the at least one virtual machine, and the driver package of the at least one virtual machine is used for the host to control the at least one virtual machine to install the driver package of the at least one virtual machine, so that drivers of the host and the virtual machine can be upgraded or installed at the same time, thereby ensuring that the drivers of the host and the virtual machine are compatible. Further, the host adds identification information to the drive package of each virtual machine in the drive packages of the at least one virtual machine, so that each virtual machine can select the drive package according to the identification information.
Optionally, as an embodiment, the method 200 further includes:
when each virtual machine in the at least one virtual machine is started, running a preconfigured scanning tool to scan virtual equipment of each virtual machine;
and if each virtual machine in the at least one virtual machine scans the drive package corresponding to each virtual machine in the virtual equipment of each virtual machine, installing the drive package corresponding to each virtual machine.
Specifically, the host machine stores the driver package of at least one virtual machine in the virtual device of each virtual machine. When each virtual machine in the at least one virtual machine is started, running a preconfigured scanning tool to scan virtual equipment of each virtual machine; if each virtual machine in the at least one virtual machine scans the drive package corresponding to each virtual machine in the virtual equipment of each virtual machine, the drive package corresponding to each virtual machine is installed, and the drives of the host machine and the virtual machine can be upgraded or installed at the same time, so that the drives of the host machine and the virtual machine are ensured to be compatible.
In an embodiment of the present invention, in a specific implementation, each of the at least one virtual machine may deploy or pre-configure a scan tool for driver installation and validation. For example, the scan tool for driver installation and validation is a GuestDrv _ install. sh script, which is integrated in Guestos image package, following the virtual machine self-boot. Wherein, sh is the suffix name of the shell script in Linux. Then, the virtual machine (gusestos) scans the optical drive or the usb disk of the virtual device thereon according to the script gustdrv _ install.
In embodiments of the present invention, the script file of the scan tool may be in different formats, such as, but not limited to, a.cfg suffix or other extension.
It should be understood that, in the embodiment of the present invention, at least one virtual machine may be one or more, and is not particularly limited thereto. In other words, the technical solution of the present invention is still applicable when there are multiple virtual machines on the host machine.
Optionally, the method further comprises:
each virtual machine in the at least one virtual machine receives trigger information from a user;
and each virtual machine is started according to the trigger information.
Specifically, each of the at least one virtual machine may receive trigger information from a user and then start or reset according to the trigger information. Each of the at least one virtual machine may invoke a scan tool to scan the virtual devices thereon at startup or reset in order to find the appropriate driver package.
Therefore, in the method for installing a driver according to the embodiment of the present invention, a host selects a driver package of the host and a driver package of the at least one virtual machine from a plurality of driver packages, where the driver package of the host and the driver package of the at least one virtual machine are compatible, then installs the driver package of the host on the host, and saves the driver package of the at least one virtual machine, and the driver package of the at least one virtual machine is used for the host to control the at least one virtual machine to install the driver package of the at least one virtual machine, so that drivers of the host and the virtual machine can be upgraded or installed at the same time, thereby ensuring that the drivers of the host and the virtual machine are compatible.
The embodiments of the present invention will be described in detail below with reference to specific examples. Fig. 4 shows a schematic diagram of an example of mounting a drive according to an embodiment of the invention. It should be noted that the example in fig. 4 is only for helping those skilled in the art to better understand the embodiment of the present invention, and does not limit the scope of the embodiment of the present invention.
As shown in fig. 4, in this example, a user 40, a host 41, and a designated virtual machine 42 are included, and it is to be understood that the designated virtual machine 42 may be any one of at least one virtual machine (e.g., a first virtual machine) managed by the host 41. In this example, when implementing the driver upgrade of the host 40 and the specified virtual machine 42, the server may complete the driver upgrade in three stages, where the first stage is a stage prepared before the upgrade (which may include S401 and S402), the second stage is an upgrade stage of the host (which may include S403 to S405), and the third stage is an upgrade stage of the virtual machine (which may include S406 to S410), and the specific steps are as follows:
alternatively, S401, the user 40 issues a plurality of driver packages PackageA.
The plurality of driver packages include a driver package (hostdrv a) of the host 41 and a driver package (GuestDrvA) of a plurality of virtual machines, wherein the GuestDrvA includes driver packages of a plurality of virtual machines that need to be supported, such as GuestDrvA1, GuestDrvA2, GuestDrvA3 …, and the like. Wherein the plurality of driver packages may or may not be compatible.
S402, the virtual machine 42 is appointed to deploy the scanning tool.
The designated virtual machine 42 designates the virtual machine that needs the upgrade driver for the host or the user. The designated virtual machine 42 is a virtual machine of the at least one virtual machine. The designated virtual machine 42 needs to deploy the associated scan script before upgrading the driver. For example, the scan script is GuestDrv _ install. The scan script is launched following the specified virtual machine 42 for scanning the virtual devices on the specified virtual machine 42 after it is launched.
S403, the host 41 receives the new driver package and the first notification message sent by the user 40.
The host 41 receives a new driver package sent by the user 40, where the driver package includes a driver package of the host and a driver package of at least one virtual machine. Furthermore, the host 41 may further receive a first notification message sent by the user 40, where the first notification message is used to instruct the host 41 to perform a driver upgrade operation.
S404, the host 41 selects a driver package of the host and a driver package of at least one virtual machine from the plurality of driver packages.
The host 41 may select a driver package of the host and a driver package of the at least one virtual machine from a plurality of driver packages provided by a user, wherein the driver package of the host and the driver package of the at least one virtual machine are compatible.
S405, the host 41 installs the driver package of the host, and saves the driver package of the at least one virtual machine.
The host 41 starts the driver upgrade operation according to the first notification information, which is specifically represented as: the driver package (hostdrv a) of the host 41 is installed in the driver directory of the host, and the driver package (GuestDrvA) of at least one virtual machine is also installed in a certain directory of the host 41 and saved. Here, the purpose of the host 41 holding the driver package of at least one virtual machine is to: the host machine controls the specified virtual machine 42 to install the driver package, so that the host machine and the specified virtual machine 42 can be upgraded or installed uniformly, and the compatibility of the drivers of the host machine and the virtual machine is ensured.
Optionally, S406, the host 41 receives the second notification message sent by the user 40.
Host 41 may receive a second notification message sent by user 40, where the second notification message is used for user 40 to notify host 41: a given virtual machine (e.g., given virtual machine 42) requires a drive upgrade operation.
S407, the host 41 stores the driver package of at least one virtual machine on the designated virtual machine 42.
After the driver package of the host machine is validated and before each virtual machine in the at least one virtual machine is started, the host machine 41 saves or inserts the driver package GuestDrvA of the at least one virtual machine into a virtual device (such as an optical drive or a USB flash disk) of the specified virtual machine 42, so that the specified virtual machine 42 searches for its driver package in the driver package of the at least one virtual machine, thereby enabling the specified virtual machine 42 to complete the driver installation or upgrade.
Optionally, the host 41 stores the driver package of at least one virtual machine on the designated virtual machine 42 upon receiving the second notification message sent by the user 40 after the driver package of the host is validated.
Alternatively, the host 41 may control the designated virtual machine 42 to perform a reset operation.
Optionally, S408, the specified virtual machine 42 receives the trigger information sent by the user 40.
The trigger information is used to instruct the designated virtual machine 42 to perform a reset operation. The designated virtual machine 42 may also be restarted after receiving the trigger information sent by the user 40, so as to perform a scanning operation according to the scanning script after being restarted.
S409, the virtual machine 42 is designated to scan the virtual device.
The designated virtual machine 42 performs a restart or reset operation according to the trigger information. At the time of starting, the designated virtual machine 42 scans the virtual device according to the scanning tool, so as to search the drive package corresponding to the designated virtual machine in the drive package of at least one virtual machine.
S410, if the drive package of the specified virtual machine is scanned by the specified virtual machine 42, the drive package is installed.
If the specified virtual machine 42 scans the driver package corresponding to the specified virtual machine 42 on its virtual device, the driver package is installed. For example, if the specified virtual machine 42 finds a GuestDrvA1 driver suitable for itself in GuestDrvA saved on its virtual device, the GuestDrvA1 driver is installed under its driver directory and the GuestDrvA1 driver is validated, thereby completing the driver upgrade of the specified virtual machine 42.
In this example, the host machine selects a driver package of the host machine and a driver package of the at least one virtual machine that are compatible, installs the driver package of the host machine, and saves the driver package of the at least one virtual machine. And after the drive package of the host machine takes effect, the host machine stores the drive package of the at least one virtual machine into the specified virtual machine. And scanning the virtual equipment on the appointed virtual machine after the appointed virtual machine is started, and installing the drive package if the drive package of the appointed virtual machine is scanned. Therefore, the drivers of the host machine and the virtual machine after upgrading can be ensured to be compatible.
Having described the method of installing a driver in detail according to an embodiment of the present invention, a server according to an embodiment of the present invention will be described below.
Fig. 5 shows a schematic block diagram of a server 500 according to an embodiment of the invention. The host 510 in the server 500 may be the NVFI 130 in fig. 1A, and the virtual machine 520 may be the VNF108 in fig. 1A. As shown in fig. 5, the host 500 includes:
a host machine 510 and at least one virtual machine 520;
the host 510 is configured to obtain a plurality of driver packages;
the host 510 is further configured to select a driver package of the host and a driver package of the at least one virtual machine from the plurality of driver packages, wherein the driver package of the host and the driver package of the at least one virtual machine are compatible;
the host 510 is further configured to install a driver package of the host on the host 510;
the host 510 is further configured to store, on the host 510, a driver package of the at least one virtual machine, where the driver package of the at least one virtual machine is used for controlling the at least one virtual machine to install the driver package of the at least one virtual machine by the host.
According to the server provided by the embodiment of the invention, the drive package of the host machine and the drive package of the at least one virtual machine are selected from the plurality of drive packages, wherein the drive package of the host machine and the drive package of the at least one virtual machine are compatible, then the drive package of the host machine is installed on the host machine, and the drive package of the at least one virtual machine is stored, and the drive package of the at least one virtual machine is used for controlling the at least one virtual machine to install the drive package of the at least one virtual machine by the host machine, so that the drives of the host machine and the virtual machine can be upgraded or installed at the same time, and the drives of the host machine and the virtual machine are ensured to be compatible.
Optionally, as an embodiment, the host 510 is further configured to:
after the driver package of the host machine is validated and before each virtual machine in the at least one virtual machine is started, the driver package of the at least one virtual machine is saved to the virtual device of each virtual machine in the at least one virtual machine.
Optionally, as an embodiment, the host 510 is further configured to:
and controlling the at least one virtual machine to start, wherein the drive package of the at least one virtual machine is used for installing each virtual machine in the at least one virtual machine at the starting time.
Optionally, as an embodiment, the host 510 is further configured to:
and adding identification information to the drive package of each virtual machine in the drive packages of the at least one virtual machine, wherein the identification information is used for each virtual machine in the at least one virtual machine to select the drive package according to the identification information.
Optionally, as an embodiment, each virtual machine 520 in the at least one virtual machine is configured to:
running a preconfigured scanning tool during starting to scan the virtual equipment of each virtual machine;
and if the drive package corresponding to each virtual machine is scanned in the virtual equipment of each virtual machine, installing the drive package corresponding to each virtual machine.
The server 500 according to the embodiment of the present invention may execute the method 200 for installing a driver according to the embodiment of the present invention, and the above and other operations and/or functions of each module in the apparatus 500 are respectively for implementing corresponding processes of the foregoing methods, and are not described herein again for brevity.
Therefore, in the server according to the embodiment of the present invention, the host selects the driver package of the host and the driver package of the at least one virtual machine from the plurality of driver packages, where the driver package of the host and the driver package of the at least one virtual machine are compatible, then installs the driver package of the host on the host, and saves the driver package of the at least one virtual machine, and the driver package of the at least one virtual machine is used for the host to control the at least one virtual machine to install the driver package of the at least one virtual machine, so that the drivers of the host and the virtual machine can be upgraded or installed at the same time, thereby ensuring that the drivers of the host and the virtual machine are compatible.
Fig. 6 shows a structure of a host 600, or server, according to another embodiment of the present invention. The Host 600 includes a hardware layer 610, a mandatory access control device running on the hardware layer 610, and a Host 601 and at least one Virtual Machine 630 running on the mandatory access control device, wherein the mandatory access control device is a Virtual Machine Monitor (VMM) 620.
In other words, the host 600 includes a hardware layer 610, a virtual machine monitor VMM 620 running on the hardware layer 610, and a host 601 and at least one virtual machine 630 running on the VMM 620, the VMM 620 being configured to perform the method of installing drivers of the embodiments of the present invention.
The hardware layer 610 may include a processor 611, a physical memory 612, a hard disk 613, and a network interface device 614, where the processor 611 may be one or multiple processors; the network interface device 614 may be a network adapter or card for connecting to any connectable network, such as the Internet (Internet), an intranet, etc. Virtual machine 630 may include a virtual processor 631, virtual memory 632, a virtual hard disk 633, and a Guest operating System (Guest OS)635, where Guest OS 635 is an operating System running on a virtual device such as virtual processor 631, virtual memory 632, virtual hard disk 633, and the like. Also running on top of Guest OS 635 is a virtual network function 636. The virtual machine monitor VMM 620 may be used to implement the method of installing drivers described in the previous embodiments.
In the embodiment of the present invention, the host 600 may include a host 601 and at least one virtual machine 630; the host 600 shown in fig. 6 can implement the processes implemented by the server in the foregoing embodiments of the methods shown in fig. 2 to fig. 4, and details are not repeated here to avoid repetition.
It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
It should be understood that, in various embodiments of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims (10)

1. A method for installing a driver, wherein the method is applied to a server in which a host machine and at least one virtual machine are operated, and the method comprises the following steps:
the host machine acquires a plurality of drive packages;
the host machine selects a driver package of the host machine and a driver package of the at least one virtual machine from the plurality of driver packages, wherein the driver package of the host machine and the driver package of the at least one virtual machine are compatible;
the host machine installs a drive package of the host machine on the host machine;
the host machine stores the driver package of the at least one virtual machine on the host machine, and the driver package of the at least one virtual machine is used for controlling the at least one virtual machine to install the driver package of the at least one virtual machine by the host machine.
2. The method of claim 1, further comprising:
after the driver package of the host machine is validated and before each of the at least one virtual machine is started, the host machine saves the driver package of the at least one virtual machine to the virtual device of each of the at least one virtual machine.
3. The method of claim 2, further comprising:
the host machine controls the at least one virtual machine to start, and the driver package of the at least one virtual machine is used for installing each virtual machine in the at least one virtual machine when starting.
4. The method according to any one of claims 1 to 3, further comprising:
and the host adds identification information to the drive package of each virtual machine in the drive packages of the at least one virtual machine, wherein the identification information is used for each virtual machine in the at least one virtual machine to select the drive package according to the identification information.
5. A method according to claim 2 or 3, characterized in that the method further comprises:
when each virtual machine in the at least one virtual machine is started, running a preconfigured scanning tool to scan virtual equipment of each virtual machine;
and if each virtual machine in the at least one virtual machine scans the drive package corresponding to each virtual machine in the virtual equipment of each virtual machine, installing the drive package corresponding to each virtual machine.
6. A server, comprising:
a host machine and at least one virtual machine;
the host machine is used for acquiring a plurality of drive packages;
the host machine is further used for selecting a drive package of the host machine and a drive package of the at least one virtual machine from the plurality of drive packages, wherein the drive package of the host machine and the drive package of the at least one virtual machine are compatible;
the host machine is also used for installing a drive package of the host machine on the host machine;
the host machine is further configured to store a driver package of the at least one virtual machine on the host machine, where the driver package of the at least one virtual machine is used for the host machine to control the at least one virtual machine to install the driver package of the at least one virtual machine.
7. The server of claim 6, wherein the host is further configured to:
after the driver package of the host machine is validated and before each virtual machine in the at least one virtual machine is started, the driver package of the at least one virtual machine is saved into a virtual device of each virtual machine in the at least one virtual machine.
8. The server of claim 7, wherein the host is further configured to:
and controlling the at least one virtual machine to start, wherein the drive package of the at least one virtual machine is used for installing each virtual machine in the at least one virtual machine when starting.
9. The server according to any one of claims 6 to 8, wherein the host is further configured to:
and adding identification information to the drive package of each virtual machine in the drive packages of the at least one virtual machine, wherein the identification information is used for each virtual machine in the at least one virtual machine to select the drive package according to the identification information.
10. The server according to claim 7 or 8, wherein each of the at least one virtual machine is configured to:
running a preconfigured scanning tool during starting to scan the virtual equipment of each virtual machine;
and if the drive package corresponding to each virtual machine is scanned in the virtual equipment of each virtual machine, installing the drive package corresponding to each virtual machine.
CN201610670063.7A 2016-08-12 2016-08-12 Method and server for installing driver Active CN106325859B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610670063.7A CN106325859B (en) 2016-08-12 2016-08-12 Method and server for installing driver

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610670063.7A CN106325859B (en) 2016-08-12 2016-08-12 Method and server for installing driver

Publications (2)

Publication Number Publication Date
CN106325859A CN106325859A (en) 2017-01-11
CN106325859B true CN106325859B (en) 2020-01-21

Family

ID=57740612

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610670063.7A Active CN106325859B (en) 2016-08-12 2016-08-12 Method and server for installing driver

Country Status (1)

Country Link
CN (1) CN106325859B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108108177B (en) * 2018-01-02 2020-10-27 联想(北京)有限公司 Firmware upgrading method of physical host, physical host and virtual machine
CN110048875B (en) * 2018-01-17 2021-01-01 华为技术有限公司 Method and equipment for upgrading drive
CN109101247B (en) * 2018-07-25 2022-02-11 新华三信息技术有限公司 Method and device for installing driver and server
CN109271172B (en) * 2018-09-17 2022-02-11 杭州安恒信息技术股份有限公司 Host performance expansion method and device of sweep cluster

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101689116A (en) * 2007-08-15 2010-03-31 索尼爱立信移动通讯股份有限公司 System and method for updating device drivers
CN102880482A (en) * 2012-08-06 2013-01-16 厦门市美亚柏科信息股份有限公司 System and technical method of automatically updating software in host batch control virtual machine
CN103533027A (en) * 2013-09-22 2014-01-22 瑞斯康达科技发展股份有限公司 Distributed equipment and software version compatibility maintenance method and system
CN103677858A (en) * 2012-08-30 2014-03-26 中兴通讯股份有限公司 Method, system and device for managing virtual machine software in cloud environment
CN103902338A (en) * 2014-03-21 2014-07-02 珠海市君天电子科技有限公司 Drive loading method, drive processing method, client side, server and system
US8990809B1 (en) * 2014-06-23 2015-03-24 Flexera Software Llc Creating a virtual appliance using existing installation manifest
CN104572147A (en) * 2013-10-18 2015-04-29 宇宙互联有限公司 Cloud startup system, virtual machine with cloud startup system and startup method of virtual machine
CN104967664A (en) * 2015-05-13 2015-10-07 西安三星电子研究有限公司 Automatic cloud deploying system and method

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101689116A (en) * 2007-08-15 2010-03-31 索尼爱立信移动通讯股份有限公司 System and method for updating device drivers
CN102880482A (en) * 2012-08-06 2013-01-16 厦门市美亚柏科信息股份有限公司 System and technical method of automatically updating software in host batch control virtual machine
CN103677858A (en) * 2012-08-30 2014-03-26 中兴通讯股份有限公司 Method, system and device for managing virtual machine software in cloud environment
CN103533027A (en) * 2013-09-22 2014-01-22 瑞斯康达科技发展股份有限公司 Distributed equipment and software version compatibility maintenance method and system
CN104572147A (en) * 2013-10-18 2015-04-29 宇宙互联有限公司 Cloud startup system, virtual machine with cloud startup system and startup method of virtual machine
CN103902338A (en) * 2014-03-21 2014-07-02 珠海市君天电子科技有限公司 Drive loading method, drive processing method, client side, server and system
US8990809B1 (en) * 2014-06-23 2015-03-24 Flexera Software Llc Creating a virtual appliance using existing installation manifest
CN104967664A (en) * 2015-05-13 2015-10-07 西安三星电子研究有限公司 Automatic cloud deploying system and method

Also Published As

Publication number Publication date
CN106325859A (en) 2017-01-11

Similar Documents

Publication Publication Date Title
US20220019474A1 (en) Methods and apparatus to manage workload domains in virtual server racks
EP3317762B1 (en) Methods and apparatus for software lifecycle management of a virtual computing environment
US10838747B2 (en) Virtual appliances
US10044795B2 (en) Methods and apparatus for rack deployments for virtual computing environments
EP3284213B1 (en) Managing virtual network functions
EP3353651B1 (en) In-service upgrade of kernel loadable modules
US10372464B2 (en) Provisioning the hyper-converged infrastructure bare metal systems from the top of the rack switch
CN101989212B (en) Method and device for providing virtual machine management program for starting blade server
CN103677807B (en) Customizing program logic for booting a system
US8762986B2 (en) Advanced packaging and deployment of virtual appliances
US20170085419A1 (en) System and method for deploying an application
US10951471B2 (en) Mechanism for hardware configuration and software deployment
CN106325859B (en) Method and server for installing driver
WO2015084638A1 (en) Methods and apparatus to automatically configure monitoring of a virtual machine
US20150039875A1 (en) Deployment of Software Images with Distinct Configuration Logic
US11528186B2 (en) Automated initialization of bare metal servers
US20200073648A1 (en) Managing an upgrade of a virtualization infrastructure component
US11997170B2 (en) Automated migration of monolithic applications to container platforms
CN108234174B (en) Management method and device of virtual network function
CN113419813A (en) Method and device for deploying bare engine management service based on container platform
WO2017004269A1 (en) Methods and apparatus for software lifecycle management of a virtual computing environment
US11425203B2 (en) Commissioning a virtualized network function
CN111008043A (en) Server starting method of cloud platform and terminal
US9690614B1 (en) Methods, systems, and computer readable mediums for orchestrating the automated installation of an application in a virtual environment
CN115004151A (en) System and method for updating add-on card firmware and collecting hardware information on any server or bare metal server installed with any OS

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20211222

Address after: 450046 Floor 9, building 1, Zhengshang Boya Plaza, Longzihu wisdom Island, Zhengdong New Area, Zhengzhou City, Henan Province

Patentee after: xFusion Digital Technologies Co., Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd.

TR01 Transfer of patent right