CN115801750A - Virtual machine communication method and device - Google Patents
Virtual machine communication method and device Download PDFInfo
- Publication number
- CN115801750A CN115801750A CN202211292486.1A CN202211292486A CN115801750A CN 115801750 A CN115801750 A CN 115801750A CN 202211292486 A CN202211292486 A CN 202211292486A CN 115801750 A CN115801750 A CN 115801750A
- Authority
- CN
- China
- Prior art keywords
- virtual
- virtual machine
- port
- bound
- virtual port
- 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.)
- Pending
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The application relates to the field of communication and provides a virtual machine communication method and device. The method comprises the following steps: loading a specific drive on a computing node and generating a plurality of VF virtual ports; determining a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with a virtual machine in the VF virtual ports; starting an ROCE function of the bound VF virtual port, and selecting a specific ROCE protocol; loading the particular driver in the virtual machine and configuring the particular ROCE protocol. The virtual machine communication method and device provided by the embodiment of the application can reduce the data movement and data copying expenses, and meet the requirements of high-performance calculation, big data analysis and other I/O high-concurrency and low-delay applications.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a virtual machine communication method and apparatus.
Background
At present, in an OpenStack cloud network, virtual machines communicate with each other based on a Transmission Control Protocol/Internet Protocol TCP/IP (TCP/IP) Protocol, but the TCP/IP Protocol sends a message through a kernel, and the communication mode has high overhead of data movement and data replication, and an existing TCP/IP architecture cannot meet application requirements in the face of high-performance computing, high-data analysis and other Input/Output I/O (I/O) high-concurrency and low-delay applications.
Disclosure of Invention
The embodiment of the application provides a virtual machine communication method and device, and aims to solve the technical problems that when virtual machines are communicated through a TCP/IP protocol, the data movement and data copying expenses are high, and the I/O high-concurrency and low-delay application requirements such as high-performance calculation and big data analysis cannot be met.
In a first aspect, an embodiment of the present application provides a virtual machine communication method, including:
loading a specific drive on a computing node and generating a plurality of VF virtual ports;
determining a bound VF virtual port; the bound VF virtual port is a VF virtual port which is bound with a virtual machine in the VF virtual ports;
starting an ROCE function of the VF virtual port which is bound, and selecting a specific ROCE protocol;
loading the particular driver in the virtual machine and configuring the particular ROCE protocol.
In one embodiment, the generating the plurality of VF virtual ports comprises:
starting an SRIOV function of a physical network card of the computing node to generate a plurality of VF virtual ports; the physical network card is matched with the specific driver.
In one embodiment, the determining the bound VF virtual port includes:
creating a direct connection virtual port and a virtual machine, and determining a bound VF virtual port according to the binding condition of the direct connection virtual port and the virtual machine.
In one embodiment, the creating a direct connection virtual port and a virtual machine includes:
creating a direct connection virtual port, starting the RDMA function of the direct connection virtual port, and selecting the specific ROCE protocol;
and creating a virtual machine, and binding a virtual network card of the virtual machine with the directly-connected virtual port.
In an embodiment, the determining a bound VF virtual port according to the binding between the direct connection virtual port and the virtual machine includes:
determining that the VF virtual port which has a mapping relation with the directly-connected virtual port is a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with the virtual network card of the virtual machine in the VF virtual ports.
In one embodiment, said loading said particular driver in said virtual machine and configuring said particular rock protocol comprises:
loading the specific drive in the virtual machine to generate an IB interface;
and binding the IB interface with a virtual network card of the virtual machine, and configuring the specific ROCE protocol for the IB interface.
In one embodiment, after the binding the virtual network card of the virtual machine with the direct connection virtual port, the method includes:
and sending a message of updating the direct connection virtual port to the computing node.
In a second aspect, an embodiment of the present application provides a virtual machine communication apparatus, including:
the VF virtual port generating module is used for loading a specific drive on a computing node and generating a plurality of VF virtual ports;
a VF virtual port determining module, configured to determine a bound VF virtual port; the bound VF virtual port is a VF virtual port which is bound with a virtual machine in the VF virtual ports;
the VF virtual port configuration module is used for starting the ROCE function of the bound VF virtual port and selecting a specific ROCE protocol;
and the virtual machine configuration module is used for loading the specific drive in the virtual machine and configuring the specific ROCE protocol.
In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor and a memory storing a computer program, where the processor implements the steps of the virtual machine communication method according to the first aspect when executing the program.
In a fourth aspect, the present application provides a computer program product, which includes a computer program, and when being executed by a processor, the computer program implements the steps of the virtual machine communication method according to the first aspect.
The Virtual machine communication method and apparatus provided in the embodiment of the present application load a specific driver on a compute node, generate a plurality of Virtual Function VF (Virtual Function, VF) Virtual ports, determine a VF Virtual port of the VF Virtual ports that has been bound to a Virtual machine, open a remote direct data access ROCE (RDMA Over switched Ethernet, rock) Function of the VF Virtual port that has been bound based on a Converged Ethernet, select a specific ROCE protocol, load the specific driver in the Virtual machine, and configure the specific ROCE protocol. The same ROCE protocol version is set in the VF virtual port at the bottom layer of the virtual machine and the virtual machine, so that Remote Direct data Access (RDMA) communication can be carried out between all the virtual machines configured with the same ROCE protocol version, because the RDMA communication directly transmits data into a storage area of the computer through a network, the data is quickly moved into a Remote system Memory from one system without causing any influence on an operating system, the use of the processing function of the computer is reduced, the expenses of data movement and data copying are reduced, and the requirements of high-performance computing, large data analysis and other I/O high-concurrency and low-delay applications are met.
Drawings
In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a virtual machine communication method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a virtual machine communication method provided by an embodiment of the present application;
fig. 3 is a second flowchart of a virtual machine communication method according to an embodiment of the present application;
fig. 4 is a third flowchart of a virtual machine communication method according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a virtual machine communication device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
To make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. 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 application.
Fig. 1 is a schematic flowchart of a virtual machine communication method provided in an embodiment of the present application;
FIG. 2 is a schematic diagram of a virtual machine communication method provided by an embodiment of the present application;
referring to fig. 1-2, an embodiment of the present application provides a virtual machine communication method, which may include:
101. loading a specific drive on a computing node and generating a plurality of VF virtual ports;
102. determining a bound VF virtual port;
the bound VF virtual port is a VF virtual port bound with a virtual machine in the VF virtual ports;
103. starting an ROCE function of the VF virtual port which is bound, and selecting a specific ROCE protocol;
104. the particular driver is loaded in the virtual machine and the particular ROCE protocol is configured.
In step 103, only the rock function of the VF virtual port that has been bound is started, and the rock protocol version is configured, without affecting the rock configuration and RDMA communication of other VF virtual ports.
In step 104, the specific driver loaded in the virtual machine is the same as the specific driver loaded in the compute node in step 101, and the specific rock protocol configured in the virtual machine is the same as the specific rock protocol selected in the VF virtual port in step 103.
The ROCE is a type of RDMA, which is generated to solve the delay of server-side data processing in network transmission, and can directly access memory data through a network interface without the intervention of an operating system kernel, thereby allowing high-throughput and low-delay network communication, and being particularly suitable for being used in a massively parallel computer cluster. ROCE is an RDMA over Ethernet technology that enables high-speed, ultra-low latency, extremely low CPU usage RDMA technology to be deployed over the currently most widely used Ethernet networks.
The ROCE protocol comprises two versions, namely ROCEv1 and ROCEv2, the ROCEv1 only supports RDMA communication of virtual machines between the same networks, the ROCEv2 version protocol supports RDMA communication of the same network or across networks, and the virtual machines between different protocols cannot carry out RDMA communication but can carry out TCP/IP communication.
In the virtual machine communication method provided in this embodiment, a specific drive is loaded on a computing node, a plurality of VF virtual ports are generated, a VF virtual port that has been bound to a virtual machine among the VF virtual ports is determined, an ROCE function of the VF virtual port that has been bound is started, a specific ROCE protocol is selected, and finally, the specific drive is loaded in the virtual machine, and the specific ROCE protocol is configured. In the embodiment, the same ROCE protocol version is set in the VF virtual port at the bottom layer of the virtual machine and the virtual machine, so that RDMA communication can be performed between all the virtual machines configured with the same ROCE protocol version, because the RDMA communication directly transfers data into a storage area of a computer through a network, the data is quickly moved from one system to a remote system memory without causing any influence on an operating system, and the use of the processing function of the computer is reduced, thereby reducing the expenses of data movement and data copying, and meeting the requirements of high-performance computing, large data analysis and other I/O high-concurrency and low-delay applications.
In one embodiment, generating the plurality of VF virtual ports may include:
starting an SRIOV function of a physical network card of a computing node to generate a plurality of VF virtual ports; the physical network card is adapted to a specific drive.
Single Root I/O Virtualization (SRIOV) is a hardware-based Virtualization solution that can improve performance and scalability. The SR-IOV standard allows for efficient sharing of a fast peripheral component interconnect device between virtual machines, and it is implemented in hardware, thus achieving I/O performance comparable to native performance.
On a computing node, a bottom layer adopts a physical network card supporting an SRIOV function and an ROCE protocol, a specific drive matched with the physical network card is loaded, the SRIOV function is started, the physical network card can virtualize a plurality of light VF virtual ports, and each VF virtual port can be configured with a respective ROCE protocol version, namely, different ROCE protocol versions of each virtual machine are supported. Meanwhile, a specific drive which is the same as that of the computing node is loaded in the virtual machine, and a specific ROCE protocol which is the same as that of a VF virtual port corresponding to communication is configured, so that RDMA communication data in the virtual machine can be forwarded through a service network card of the computing node.
In addition, the same computing node supports the creation of virtual machines of different ROCE protocol types, when the virtual machine is migrated to other nodes, the virtual machine is bound with a corresponding VF virtual port, the same ROCE protocol as the virtual machine is configured for the VF virtual port, and the stability and the migratability of RDMA communication between the virtual machines are ensured. Stable RDMA communication between virtual machines can be supported.
In this embodiment, by starting the SRIOV function of the physical network card of the computing node, in cooperation with a specific driver, multiple VF virtual ports can be generated, which facilitates the relevant configuration of the VF virtual ports.
Fig. 3 is a second flowchart of a virtual machine communication method according to an embodiment of the present disclosure; referring to fig. 3, in one embodiment, determining the bound VF virtual port may include:
301. creating a direct connection virtual port, starting the RDMA function of the direct connection virtual port, and selecting a specific ROCE protocol;
302. creating a virtual machine, and binding a virtual network card of the virtual machine with the directly-connected virtual port;
303. and determining that the VF virtual port with the mapping relation with the direct connection virtual port is a bound VF virtual port.
The bound VF virtual port is a VF virtual port that has been bound to a virtual network card of a virtual machine among the VF virtual ports.
In step 301, an application program interface of a neutron-server component in an OpenStack cloud network may be invoked to create a direct connection virtual port.
OpenStack is an open-source cloud computing management platform project and is a combination of a series of software open-source projects, neutron plays a role in providing network service for a virtual machine instance in an OpenStack cluster, and neutron-server is one of the core components of neutron and is responsible for directly receiving an external request and then scheduling a corresponding plug-in at a back end for processing.
It should be noted that only after the RDMA function directly connected to the virtual port is selected to be started, a specific rock protocol may be selected, that is, the version of the rock protocol is selected, and the RDMA communication of the virtual machine can only be realized by the rock protocol.
In step 302, an application program interface of a neutron-server component in an OpenStack cloud network may be invoked to create a virtual machine.
In step 303, since the direct connection virtual port and the VF virtual port have a mapping relationship, after the virtual network card of the virtual machine is bound to the direct connection virtual port in step 302, it can be determined that the VF virtual port mapped to the bound direct connection virtual port is already bound to the virtual network card of the virtual machine, that is, the bound VF virtual port.
In this embodiment, by creating a direct connection virtual port and a virtual machine, and determining a bonded VF virtual port according to the binding condition between the direct connection virtual port and the virtual machine, virtual machines and VF virtual ports that need to perform RDMA communication can be in one-to-one correspondence.
Fig. 4 is a third schematic flowchart of a virtual machine communication method according to an embodiment of the present application; referring to fig. 4, in one embodiment, loading a particular driver in a virtual machine and configuring a particular rock protocol may include:
401. loading a specific drive in a virtual machine to generate an IB interface;
402. and binding the IB interface with the virtual network card of the virtual machine, and configuring a specific ROCE protocol for the IB interface.
In step 401, the specific driver loaded in the virtual machine is the same as the specific driver loaded in the compute node, and after the specific driver is loaded, the IB interface mlx5_0 corresponding to the virtual network card of the virtual machine is automatically generated. The IB interface is an interface supporting RDMA communication, and mlx5_0 is the name of the IB interface.
The interconnect structure IB (InfiniBand, IB) is a unified interconnect structure, and can handle both storage I/O and network I/O, as well as inter-process communication. It can interconnect disk arrays, storage Area networks SAN (SAN), local Area networks LAN (LAN), servers and cluster servers, or connect to external networks such as Wide Area networks WAN (WAN), virtual Private networks VPN (VPN), and the internet.
In step 402, a specific rock mode that is the same as the VF virtual port is configured for the mlx5_0 interface, so as to ensure the consistency of the communication protocol on the link.
In this embodiment, by generating a binding between the IB interface and the virtual network adapter of the virtual machine, and configuring a specific rock protocol for the interface, the rock protocol configured for the virtual network adapter in the virtual machine is the same as the rock protocol version of the VF virtual port in the bottom layer, and RDMA communication is ensured between virtual machines configured with the same rock protocol.
In one embodiment, after binding the virtual network card of the virtual machine with the direct connection virtual port, the method may include:
and sending a message of updating the direct connection virtual port to the computing node.
The direct connection virtual port update message may be sent to the neutron-sriov-agent of the compute node through a port plugin in the neutron-server component.
The port plug-in is mainly responsible for managing a virtual machine port, RDMA state and ROCE version information of the port can be added in the port plug-in, data are stored in a mysql database, neutron-sriov-agent is an agent and is generally deployed on a computing node, and various network functions are achieved by processing requests from the plug-in.
A corresponding VF virtual port management module VF-manager can be added in the neutron-sriov-agent to manage the VF virtual port, and the attribute and version of the ROCE of the VF virtual port are configured.
When the neutron-sriov-agent receives the message for updating the directly connected virtual port, the Vf-manager module can be called to start the ROCE function of the virtual port of the bound VF, and a specific ROCE protocol consistent with the directly connected virtual port is selected.
According to the embodiment, the ROCE function of the VF virtual port which is bound is started according to the message updated by the directly-connected virtual port, a specific ROCE protocol is selected, and the time point of starting the ROCE function can be controlled accurately.
The following describes a virtual machine communication device provided in an embodiment of the present application, and the virtual machine communication device described below and the virtual machine communication method described above may be referred to correspondingly.
Fig. 5 is a schematic structural diagram of a virtual machine communication device according to an embodiment of the present application. Referring to fig. 5, an embodiment of the present application provides a virtual machine communication apparatus, which may include:
a VF virtual port generating module 501, configured to load a specific driver on a computing node and generate multiple VF virtual ports;
a VF virtual port determining module 502, configured to determine a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with a virtual machine in the VF virtual ports;
a VF virtual port configuration module 503, configured to start an ROCE function of the VF virtual port that has been bound, and select a specific ROCE protocol;
a virtual machine configuration module 504, configured to load the specific driver in the virtual machine and configure the specific rock protocol.
The virtual machine communication apparatus provided in this embodiment loads a specific driver on a compute node, generates a plurality of VF virtual ports, determines a VF virtual port that has been bound to a virtual machine among the VF virtual ports, starts an ROCE function of the VF virtual port that has been bound, selects a specific ROCE protocol, finally loads the specific driver in the virtual machine, and configures the specific ROCE protocol. In the embodiment, the same ROCE protocol version is set in the VF virtual port at the bottom layer of the virtual machine and the virtual machine, so that RDMA communication can be performed between all the virtual machines configured with the same ROCE protocol version, because the RDMA communication directly transfers data into a storage area of a computer through a network, the data is quickly moved from one system to a remote system memory without causing any influence on an operating system, and the use of the processing function of the computer is reduced, thereby reducing the expenses of data movement and data copying, and meeting the requirements of high-performance computing, large data analysis and other I/O high-concurrency and low-delay applications.
In an embodiment, the VF virtual port generating module 501 is specifically configured to:
starting an SRIOV function of a physical network card of the computing node to generate a plurality of VF virtual ports; and the physical network card is matched with the specific driver.
In an embodiment, the VF virtual port determining module 502 is specifically configured to:
and creating a direct connection virtual port and a virtual machine, and determining a bound VF virtual port according to the binding condition of the direct connection virtual port and the virtual machine.
In an embodiment, the VF virtual port determining module 502 is specifically configured to:
creating a direct connection virtual port, starting the RDMA function of the direct connection virtual port, and selecting the specific ROCE protocol;
and creating a virtual machine, and binding a virtual network card of the virtual machine with the directly-connected virtual port.
In an embodiment, the VF virtual port determining module 502 is specifically configured to:
determining that the VF virtual port which has a mapping relation with the directly-connected virtual port is a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with the virtual network card of the virtual machine in the VF virtual ports.
In one embodiment, the virtual machine configuration module 504 is specifically configured to:
loading the specific drive in the virtual machine to generate an IB interface;
and binding the IB interface with a virtual network card of the virtual machine, and configuring the specific ROCE protocol for the IB interface.
In one embodiment, the system further comprises a message sending module (not shown in the figure) configured to:
and sending a message of updating the direct connection virtual port to the computing node.
Fig. 6 illustrates a schematic physical structure diagram of an electronic device, and as shown in fig. 6, the electronic device may include: a processor (processor) 610, a Communication Interface (Communication Interface) 620, a memory (memory) 630 and a Communication bus 640, wherein the processor 610, the Communication Interface 620 and the memory 630 complete Communication with each other through the Communication bus 640. The processor 610 may invoke computer programs in the memory 630 to perform the steps of the virtual machine communication method, including, for example:
loading a specific driver at a computing node and generating a plurality of VF virtual ports;
determining a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with a virtual machine in the VF virtual ports;
starting an ROCE function of the bound VF virtual port, and selecting a specific ROCE protocol;
loading the particular driver in the virtual machine and configuring the particular ROCE protocol.
In addition, the logic instructions in the memory 630 may be implemented in the form of software functional units and stored in a computer readable storage medium when the logic instructions are sold or used as independent products. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 application. 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.
In another aspect, the present application further provides a computer program product, where the computer program product includes a computer program, where the computer program may be stored on a non-transitory computer readable storage medium, and when the computer program is executed by a processor, a computer is capable of executing the steps of the virtual machine communication method provided in the foregoing embodiments, for example, the steps include:
loading a specific driver at a computing node and generating a plurality of VF virtual ports;
determining a bound VF virtual port; the bound VF virtual port is a VF virtual port which is bound with a virtual machine in the VF virtual ports;
starting an ROCE function of the bound VF virtual port, and selecting a specific ROCE protocol;
loading the particular driver in the virtual machine and configuring the particular ROCE protocol.
On the other hand, embodiments of the present application further provide a processor-readable storage medium, where the processor-readable storage medium stores a computer program, where the computer program is configured to enable a processor to execute the steps of the method provided in each of the foregoing embodiments, for example, including:
loading a specific drive on a computing node and generating a plurality of VF virtual ports;
determining a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with a virtual machine in the VF virtual ports;
starting an ROCE function of the VF virtual port which is bound, and selecting a specific ROCE protocol;
loading the particular driver in the virtual machine and configuring the particular ROCE protocol.
The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid State Disks (SSDs)), etc.
The above-described embodiments of the apparatus are merely illustrative, and 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 position, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. A virtual machine communication method, comprising:
loading a specific drive on a computing node and generating a plurality of VF virtual ports;
determining a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with a virtual machine in the VF virtual ports;
starting an ROCE function of the VF virtual port which is bound, and selecting a specific ROCE protocol;
loading the particular driver in the virtual machine and configuring the particular ROCE protocol.
2. The virtual machine communication method according to claim 1, wherein the generating the VF virtual ports comprises:
starting an SRIOV function of a physical network card of the computing node to generate a plurality of VF virtual ports; the physical network card is matched with the specific driver.
3. The virtual machine communication method according to claim 1, wherein the determining the bound VF virtual port comprises:
and creating a direct connection virtual port and a virtual machine, and determining a bound VF virtual port according to the binding condition of the direct connection virtual port and the virtual machine.
4. The virtual machine communication method according to claim 3, wherein the creating of the direct connection virtual port and the virtual machine comprises:
creating a direct connection virtual port, starting the RDMA function of the direct connection virtual port, and selecting the specific ROCE protocol;
and creating a virtual machine, and binding a virtual network card of the virtual machine with the direct connection virtual port.
5. The virtual machine communication method according to claim 4, wherein the determining, according to the binding condition between the directly connected virtual port and the virtual machine, a bound VF virtual port includes:
determining that the VF virtual port which has a mapping relation with the directly-connected virtual port is a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with the virtual network card of the virtual machine in the VF virtual ports.
6. The virtual machine communication method according to claim 1, wherein the loading the specific driver in the virtual machine and configuring the specific ROCE protocol comprises:
loading the specific drive in the virtual machine to generate an IB interface;
and binding the IB interface with a virtual network card of the virtual machine, and configuring the specific ROCE protocol for the IB interface.
7. The virtual machine communication method according to claim 4, wherein after the binding of the virtual network card of the virtual machine and the direct connection virtual port, the method comprises:
and sending a message of updating the direct connection virtual port to the computing node.
8. A virtual machine communication apparatus, comprising:
the VF virtual port generating module is used for loading a specific drive on a computing node and generating a plurality of VF virtual ports;
a VF virtual port determining module, configured to determine a bound VF virtual port; the bound VF virtual port is a VF virtual port bound with a virtual machine in the VF virtual ports;
the VF virtual port configuration module is used for starting the ROCE function of the bound VF virtual port and selecting a specific ROCE protocol;
and the virtual machine configuration module is used for loading the specific drive in the virtual machine and configuring the specific ROCE protocol.
9. An electronic device comprising a processor and a memory storing a computer program, wherein the steps of the virtual machine communication method according to any one of claims 1 to 7 are implemented when the processor executes the computer program.
10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, carries out the steps of the virtual machine communication method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211292486.1A CN115801750A (en) | 2022-10-20 | 2022-10-20 | Virtual machine communication method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211292486.1A CN115801750A (en) | 2022-10-20 | 2022-10-20 | Virtual machine communication method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115801750A true CN115801750A (en) | 2023-03-14 |
Family
ID=85433415
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211292486.1A Pending CN115801750A (en) | 2022-10-20 | 2022-10-20 | Virtual machine communication method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115801750A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116614459A (en) * | 2023-07-18 | 2023-08-18 | 中移(苏州)软件技术有限公司 | Link aggregation group management method and device based on Ethernet RDMA protocol |
| CN117499205A (en) * | 2023-12-28 | 2024-02-02 | 苏州元脑智能科技有限公司 | Method, device, equipment and medium for binding disaster recovery of storage system port |
-
2022
- 2022-10-20 CN CN202211292486.1A patent/CN115801750A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116614459A (en) * | 2023-07-18 | 2023-08-18 | 中移(苏州)软件技术有限公司 | Link aggregation group management method and device based on Ethernet RDMA protocol |
| CN116614459B (en) * | 2023-07-18 | 2023-10-13 | 中移(苏州)软件技术有限公司 | Link aggregation group management method and device based on Ethernet RDMA protocol |
| CN117499205A (en) * | 2023-12-28 | 2024-02-02 | 苏州元脑智能科技有限公司 | Method, device, equipment and medium for binding disaster recovery of storage system port |
| CN117499205B (en) * | 2023-12-28 | 2024-03-29 | 苏州元脑智能科技有限公司 | Method, device, equipment and medium for binding disaster recovery of storage system port |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10374885B2 (en) | Reconfigurable server including a reconfigurable adapter device | |
| Vaquero et al. | Dynamically scaling applications in the cloud | |
| CN115801750A (en) | Virtual machine communication method and device | |
| US10212045B2 (en) | Method and system for testing and analyzing management servers | |
| US10225142B2 (en) | Method and system for communication between a management-server and remote host systems | |
| US11681585B2 (en) | Data migration for a shared database | |
| US20220166666A1 (en) | Data plane operation in a packet processing device | |
| CN115858102A (en) | Method for deploying virtual machine supporting virtualization hardware acceleration | |
| US11055108B2 (en) | Network booting in a peer-to-peer environment using dynamic magnet links | |
| CN115858103B (en) | Method, device and medium for virtual machine hot migration of open stack architecture | |
| EP4109251A1 (en) | Vnf instantiation method and device | |
| CN109327332A (en) | ISCSI GateWay high availability implementation method based on LIO under a kind of Ceph cloud storage | |
| US11513830B2 (en) | Introspection into workloads running within virtual machines | |
| CN108139937A (en) | More I/O virtualization systems | |
| WO2023121768A1 (en) | Switch for managing service meshes | |
| CN117519908B (en) | Virtual machine thermomigration method, computer equipment and medium | |
| US20170279676A1 (en) | Topology-based virtual switching model with pluggable flow management protocols | |
| CN114579250B (en) | Method, device and storage medium for constructing virtual cluster | |
| CN115470303B (en) | Database access method, device, system, equipment and readable storage medium | |
| US10469374B2 (en) | Multiple provider framework for virtual switch data planes and data plane migration | |
| US9626444B2 (en) | Continuously blocking query result data for a remote query | |
| EP3073372A1 (en) | Performing code load operations on managed components in a system | |
| WO2024114645A1 (en) | Instantiation method for virtualization network function (vnf), and apparatus | |
| US12086141B1 (en) | Coordination of services using PartiQL queries | |
| US20220083540A1 (en) | Efficient bulk loading multiple rows or partitions for a single target table |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |