WO2019001398A1 - 虚拟网卡接口的状态控制和报文传输 - Google Patents

虚拟网卡接口的状态控制和报文传输 Download PDF

Info

Publication number
WO2019001398A1
WO2019001398A1 PCT/CN2018/092731 CN2018092731W WO2019001398A1 WO 2019001398 A1 WO2019001398 A1 WO 2019001398A1 CN 2018092731 W CN2018092731 W CN 2018092731W WO 2019001398 A1 WO2019001398 A1 WO 2019001398A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
network card
virtual
card interface
state
Prior art date
Application number
PCT/CN2018/092731
Other languages
English (en)
French (fr)
Inventor
孙凯
柳佳佳
Original Assignee
新华三技术有限公司
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 新华三技术有限公司 filed Critical 新华三技术有限公司
Publication of WO2019001398A1 publication Critical patent/WO2019001398A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances

Definitions

  • NFV Network Functions Virtualization
  • the hypervisor is an intermediate software layer running between the physical server and the operating system.
  • Virtualized resources can include virtualized hardware such as hard disks, CPU (Central Processing Unit), memory, and network cards, all of which are implemented by hypervisor simulation.
  • the network card resources used in the NFV implementation scheme mainly include a common virtual network card, such as a fully virtualized network card or a paravirtualized network card.
  • FIG. 1 is a schematic flowchart diagram of an interface state control method according to an embodiment of the present invention.
  • FIG. 1A, 1B, and 1C are schematic diagrams of a network architecture in which the method shown in FIG. 1 is applied.
  • FIG. 2 is a schematic structural diagram of a specific application scenario according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a packet transmission method according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of hardware of an interface state control apparatus according to an embodiment of the present invention.
  • FIG. 5 is a functional structural diagram of an interface state control logic according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of hardware of a message transmission apparatus according to an embodiment of the present invention.
  • FIG. 7 is a functional structural diagram of a message transmission control logic according to an embodiment of the present invention.
  • FIG. 1 is a schematic flowchart diagram of an interface state control method according to an embodiment of the present invention.
  • the method can be applied to a virtualization layer of an NFV-enabled host.
  • the interface state control method can include the following steps:
  • step 101 the interface response chain of the virtual machine is maintained.
  • the interface response chain includes a correspondence between a virtual network card interface belonging to the virtual machine and a physical network card interface associated with the virtual network card interface.
  • a virtual machine that uses a normal virtual NIC cannot know the status of the interface of the physical NIC.
  • the status of the virtual NIC interface of the virtual machine may be different from that of the physical NIC. Therefore, the virtual machine service cannot run normally in a specific scenario.
  • the interface response chain notifies the corresponding virtual machine of the physical network card interface state change.
  • a virtual machine 111 and a virtual machine 112 are deployed on the host 100, and the virtual machine 111 and the virtual machine 112 are associated with the physical network interface 13C through the virtual network interface 12A1 and the virtual network interface 12B1, respectively. Then the host 100 can maintain the interface response chain as shown in Table 1:
  • Virtual machine 111 Virtual network card interface 12A1 Physical NIC interface 13C
  • Virtual machine 112 Virtual network card interface 12B1 Physical NIC interface 13C
  • the foregoing maintenance interface response chain may include: determining, when the virtual machine is created, whether the virtual machine enables the physical network card interface state response function; if yes, creating an interface response corresponding to the virtual machine chain.
  • a physical network card interface state response function may be introduced for the virtual machine.
  • a corresponding interface response chain needs to be created for the virtual machine, and the physical network card interface state change notification is performed according to the interface response chain.
  • the physical network card interface status response function is disabled on the VM, you do not need to create a corresponding interface response chain for the VM or notify the physical network card interface status change.
  • the virtual machine when the virtual machine is created, it can be determined whether the virtual machine enables the physical network card interface status response function. If the physical network card interface status response function is enabled on the virtual machine, you can create an interface response chain corresponding to the virtual machine. Otherwise, you do not need to create an interface response chain corresponding to the virtual machine.
  • the value of the field is the first identifier, it indicates that the corresponding virtual machine is enabled with the physical NIC interface status response function.
  • the value of the field is the second identifier, the corresponding virtual machine is not enabled with the physical NIC interface.
  • Status response function In this way, based on the value of the field in the configuration file of the virtual machine, it can be determined whether the physical network card interface state response function is enabled on the virtual machine. Moreover, when it is determined that the virtual network machine has enabled the physical network card interface state response function, the interface response chain corresponding to the virtual machine is created.
  • the interface response chain of the virtual machine is updated, or the virtual machine is deleted when the virtual machine is deleted.
  • the corresponding relationship between the added virtual network card interface and its associated physical network card interface may be added in the interface response chain.
  • the interface response chain of the virtual machine 111 shown in Table 1 is taken as an example.
  • a virtual network card interface 12A2 is added to the virtual machine 111, and the virtual network card interface 12A2 is associated with the physical network card interface 13D.
  • the interface response chain of the updated virtual machine 111 can be as shown in Table 2:
  • the virtual machine When the virtual machine deletes the virtual NIC interface, the information corresponding to the virtual NIC interface in the interface response chain maintained by the virtual machine itself may be deleted.
  • the interface response chain corresponding to the virtual machine maintained by itself may be deleted.
  • Step 102 Control the state of the virtual network card interface associated with the physical network card interface according to the state of the physical network card interface in the interface response chain.
  • the state of the virtual NIC interface can be controlled according to the interface response chain to be consistent with the state of the corresponding physical NIC interface.
  • the state of the virtual NIC interface associated with the physical NIC interface is controlled according to the state of the physical NIC interface in the interface response chain, including: For any virtual NIC When the state of the physical NIC interface associated with the virtual NIC interface changes from the UP state to the Down state, the state of the virtual NIC interface is switched to the Down state; when the virtual NIC interface is associated with the physical NIC When the state of an interface changes from Down to Up, the state of the virtual NIC interface is switched to the UP state.
  • the state of the physical NIC interface associated with a virtual NIC interface (hereinafter referred to as the target virtual NIC interface) is changed from the UP state to the Down state.
  • the target virtual NIC interface can be switched to the Down state.
  • the target virtual NIC interface can be switched to the UP state.
  • the host 100 can switch the virtual NIC interface 12A1 and the virtual NIC interface 12B1 to Down state.
  • the state of the virtual network card interface associated with the physical network card interface is controlled according to the state of the physical network card interface in the interface response chain, including: The virtual network card interface controls the state of the virtual network card interface to be Down state when the state of the multiple physical network card interfaces associated with the virtual network card interface changes from the UP state to the Down state; when the virtual network card interface is associated with multiple physical entities When the state of at least one physical NIC interface in the NIC is changed from the Down state to the UP state, the state of the virtual NIC interface is controlled to be in the UP state.
  • the target virtual NIC interface association is determined.
  • the status of the physical NIC interface is Down, so that the state of the target virtual NIC interface can be switched to the Down state.
  • the status of the physical NIC interface of the target NIC interface is changed from the Down state to the Up state, the status of the physical NIC interface associated with the target NIC interface is UP, so that the target NIC interface can be The state is switched to the UP state.
  • the host 100-2 when the host 100-2 detects that the state of the physical NIC interface 13E1 and the physical NIC interface 13E2 changes from the UP state to the Down state, the host 100-2 can switch the state of the virtual NIC interface 12C1 to the Down state.
  • the host 100-2 When the state of the physical network card interface 13E1 and the physical network card interface 13E2 are both in the Down state, and the host 100-2 detects that the physical network interface 13E1 changes from the Down state to the UP state, the host 100-2 can switch the state of the virtual network interface 12C1. It is in the UP state.
  • the virtual network card interface can be effectively guaranteed.
  • the status of the corresponding physical NIC interface is the same.
  • FIG. 2 is a schematic diagram of a specific application scenario according to an embodiment of the present invention.
  • two virtual machines (VMs) 211 and 212 exist on a host (200).
  • the virtual network card interface 2111A1 on the virtual network card 211A1 of the VM 211 and the virtual network card interface 2121A2 on the virtual network card 212A2 of the VM 212 are connected to the physical network card interface 251A of the physical network card 250A through a Linux (an operating system) bridge 2410. .
  • the VMs 211, 212 can be connected to the upper network 260 via the physical network card 250A.
  • VM 220 there is a VM 220 on the host 200B. Moreover, the virtual network card interface 2201B on the virtual network card 220B of the VM 220 is connected to the physical network card interface 251B of the physical network card 250B through the Linux bridge 2420. As such, VM 220 can be connected to upper layer network 260 via physical network card 250B.
  • a VM 231, a VM 232, and a VM 233 are present on the host 200C.
  • the virtual network card interface 2311C1 on the virtual network card 231C1 of the VM 231 is connected to the Linux bridge 2431, and the virtual network card interface 2321C2 on the virtual network card 232C2 of the VM 232 and the virtual network card interface 2331C3 on the virtual network card 233C3 of the VM 233 are connected to the Linux bridge 2432.
  • the Linux bridge 2431 and the Linux bridge 2432 are connected to the physical network card interface 251C of the physical network card 250C through the Linux bridge 2433.
  • VMs 231, 232, 233 can be connected to upper layer network 260 via physical network card 250C.
  • a new field for indicating whether the virtual machine enables the physical network card interface status response function is added to the configuration file of the virtual machine.
  • the value of this field is the first identity value (such as 0x1), it indicates that the virtual machine enables the physical NIC interface status response function.
  • the value of this field is the second identifier value (such as 0x0), it indicates that the virtual machine does not enable the physical NIC interface status response function.
  • the network card resource used by the virtual machine is a normal virtual network card
  • the virtualization layer monitors the state of the physical network card interface.
  • the kernel notifies the physical NIC interface UP/Down event
  • the virtualization layer controls the state change of the corresponding virtual NIC interface.
  • the virtualization layers of the host 200A, the host 200B, and the host 200C respectively determine whether the physical network card interface state response function is enabled for the virtual machine of the local machine.
  • the physical status fields in the configuration files of the virtual machine 211, the virtual machine 212, the virtual machine 220, the virtual machine 231, the virtual machine 232, and the virtual machine 233 are all "0x1", that is, each virtual machine makes
  • the physical network card interface status response function can be enabled;
  • Virtual machine 211 Virtual network card interface 2111A1 Physical NIC interface 251A
  • Virtual machine 212 Virtual network card interface 2121A2 Physical NIC interface 251A
  • Virtual machine 220 Virtual network card interface 2201B Physical NIC interface 251B
  • Virtual machine 231 Virtual network card interface 2311C1 Physical NIC interface 251C Virtual machine 232 Virtual network card interface 2321C2 Physical NIC interface 251C Virtual machine 233 Virtual network card interface 2331C3 Physical NIC interface 251C
  • the host when there are multiple layers of Linux bridge nested deployment (such as host 200C), the host records the correspondence between the virtual network card interface and the physical network card interface that are connected through multiple layers of Linux bridge. .
  • the state of the physical NIC interface 250A that the virtualization layer of the host 200A receives from the kernel changes from the UP state to the Down state event.
  • the virtualization layer of the host 200A can switch the state of the virtual network card interface 2111A1 and the virtual network card interface 2121A2 to the Down state, respectively.
  • the virtualization layer of the host 200A can respectively set the state of the virtual network interface 2111A1 and the virtual network interface 2121A2. Switch to the UP state.
  • the virtualization layer of the host 200B and the host 200C may also perform the physical network card interface state change notification according to the above description, and the specific implementation thereof is not described herein.
  • FIG. 3 is a schematic flowchart diagram of a packet transmission method according to an embodiment of the present invention.
  • the packet transmission method can be applied to the NFV-enabled host. As shown in FIG. 3, the packet transmission method can include the following steps 301-304.
  • the execution body of steps 301 to 304 may be a management module of the host or the host, such as a CPU (Center Process Unit).
  • the following takes the execution subject of steps 301 to 304 as a host as an example for description.
  • the interface response chain of the virtual machine is maintained.
  • the interface response chain includes a correspondence between a virtual network card interface belonging to the virtual machine and a physical network card interface associated with the virtual network card interface.
  • Step 302 Determine a state of the target virtual network card interface according to a state of the physical network card interface corresponding to the target virtual network card interface in the interface response chain.
  • the target virtual NIC interface does not specifically refer to a fixed virtual NIC interface, but may refer to any virtual NIC interface of any virtual machine deployed on the host that will be used to transmit packets.
  • the host can query the interface response chain maintained by the host according to the target virtual NIC interface to determine the physical NIC interface associated with the target virtual NIC interface, and further, associate the virtual NIC interface according to the target virtual NIC interface.
  • the state of the physical NIC interface determines the state of the target virtual NIC interface.
  • the host can determine that the target virtual NIC interface is in the UP state; when the target virtual NIC interface is associated When the physical NIC interface is in the Down state, the host can determine that the target virtual NIC interface is in the Down state.
  • the host may determine the target virtual NIC interface when at least one physical NIC interface of the plurality of physical NIC interfaces associated with the target virtual NIC interface is in the UP state.
  • the host can determine that the target NIC interface is Down.
  • Step 303 When it is determined that the target virtual network card interface is in an UP state, the packet is transmitted through the target virtual network card interface.
  • the host when the host determines that the target virtual network card interface is in the UP state, the host may transmit the packet through the target virtual network card interface.
  • Step 304 When the target virtual network card interface is in the Down state, the packet is refused to be transmitted through the target virtual network interface.
  • the host when the host determines that the target virtual NIC interface is in the Down state, the host will refuse to transmit the packet through the target virtual NIC interface.
  • the status of the virtual NIC interface is consistent with that of the corresponding physical NIC.
  • FIG. 4 is a schematic structural diagram of hardware of an interface state control apparatus according to an embodiment of the present invention.
  • the interface state control device can include a processor 401, a machine readable storage medium 402 that stores machine executable instructions.
  • Processor 401 and machine readable storage medium 402 can communicate via system bus 403. And, by reading and executing machine executable instructions in the machine readable storage medium 402 corresponding to the interface state control logic, the processor 401 can perform the interface state control method described above.
  • the machine-readable storage medium 402 referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like.
  • a machine-readable storage medium can be a volatile memory, a non-volatile memory, or similar storage medium.
  • the machine readable storage medium may be a RAM (Radom Access Memory), a flash memory, a storage drive (such as a hard disk drive), a solid state drive, any type of storage disk (such as a compact disc, dvd, etc.) or combination.
  • the above interface state control logic may include a maintenance unit 501 and a control unit 502.
  • the maintenance unit 501 is configured to maintain an interface response chain of the virtual machine, where the interface response chain includes a correspondence between a virtual network card interface belonging to the virtual machine and a physical network card interface associated with the virtual network card interface; and the control unit 502 And controlling a state of the virtual network card interface associated with the physical network card interface according to a state of the physical network card interface in the interface response chain.
  • the maintenance unit 501 is specifically configured to determine, when the virtual machine is created, whether the virtual machine enables the physical network card interface status response function. If yes, create an interface response chain corresponding to the virtual machine.
  • the maintenance unit 501 is further configured to: when the virtual machine adds the virtual network card interface or delete the virtual network card interface, update the interface response chain corresponding to the virtual machine, and delete the interface response corresponding to the virtual machine when the virtual machine is deleted. chain.
  • control unit 502 is specifically configured to: if the physical NIC interface associated with the first virtual NIC interface is changed from the ON state to the Down state, the first NIC interface associated with the interface of the physical NIC is And controlling the first virtual network card interface to be in the Down state; and if the physical network card interface associated with the first virtual network card interface is changed from the Down state to the Up state, the first virtual network card interface is controlled to be in the UP state.
  • control unit 502 is further configured to: for the second virtual network card interface that is associated with the multiple physical network card interfaces, if the multiple physical network card interfaces associated with the second virtual network card interface are all in the Down state, control the virtual The NIC interface is in the Down state. If at least one of the physical NIC interfaces of the second virtual NIC interface is in the Up state, the second NIC interface is controlled to be in the Up state.
  • FIG. 6 is a schematic structural diagram of hardware of a message transmission apparatus according to an embodiment of the present invention.
  • the message transfer device can include a processor 601, a machine readable storage medium 602 that stores machine executable instructions.
  • Processor 601 and machine readable storage medium 602 can communicate via system bus 603. And, by reading and executing the machine executable instructions in the machine readable storage medium 602 corresponding to the message transmission control logic, the processor 601 can perform the message transmission method described above.
  • the machine-readable storage medium 602 referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like.
  • a machine-readable storage medium can be a volatile memory, a non-volatile memory, or similar storage medium.
  • the machine readable storage medium may be a RAM (Radom Access Memory), a flash memory, a storage drive, a solid state drive, any type of storage disk, or a combination thereof.
  • the above message transmission control logic may include a maintenance unit 701, a determination unit 702, and a transmission unit 703.
  • the maintenance unit 701 is configured to maintain an interface response chain of the virtual machine, where the interface response chain includes a correspondence between a virtual network card interface belonging to the virtual machine and a physical network card interface associated with the virtual network card interface, and the determining unit 702 And determining, according to the state of the physical NIC interface corresponding to the target virtual NIC interface in the interface response chain, the state of the target virtual NIC interface; the transmitting unit 703, configured to: when determining that the target virtual NIC interface is in the UP state, The packet is transmitted through the target virtual network interface, and when the target virtual network interface is determined to be in the Down state, the packet is refused to be transmitted through the target virtual network interface.

Abstract

本发明提供一种接口状态控制方法、报文传输方法及装置，可应用于使能了网络功能虚拟化的主机。根据该接口状态控制方法的一个示例，针对主机上部署的虚拟机维护接口响应链。其中，所述接口响应链包括属于该虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系。然后，主机可根据接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态，以保证虚拟网卡接口与对应的物理网卡接口状态一致。

Description

虚拟网卡接口的状态控制和报文传输
相关申请的交叉引用
本专利申请要求于2017年6月27日提交的、申请号为201710503089.7、发明名称为“一种接口状态控制方法、报文传输方法及装置”的中国专利申请的优先权，该申请的全文以引用的方式并入本文中。
背景技术
NFV(Network Functions Virtualization,网络功能虚拟化)运行在虚拟化环境中，依赖底层的hypervisor提供虚拟化资源。其中，hypervisor是一种运行在物理服务器和操作系统之间的中间软件层。虚拟化资源可包括硬盘、CPU(Center Process Unit，中央处理单元)、内存以及网卡等虚拟化硬件，均是由hypervisor模拟实现。
目前，NFV实现方案中使用的网卡资源主要包括普通虚拟网卡，例如全虚拟化网卡或半虚拟化网卡等。
附图说明
图1是本发明实施例提供的一种接口状态控制方法的流程示意图。
图1A、1B、1C为应用图1所示方法的网络架构示意图。
图2是本发明实施例提供的一种具体应用场景的架构示意图。
图3是本发明实施例提供的一种报文传输方法的流程示意图。
图4是本发明实施例提供的一种接口状态控制装置的硬件结构示意图。
图5是本发明实施例提供的一种接口状态控制逻辑的功能结构图。
图6是本发明实施例提供的一种报文传输装置的硬件结构示意图。
图7是本发明实施例提供的一种报文传输控制逻辑的功能结构图。
具体实施方式
请参见图1，图1为本发明实施例提供的一种接口状态控制方法的流程示意图。其 中，该方法可以应用于使能了NFV的主机的虚拟化层，如图1所示，该接口状态控制方法可以包括以下步骤：
在步骤101、维护虚拟机的接口响应链。其中，该接口响应链包括属于虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系。
使用普通虚拟网卡的虚拟机由于无法获知物理网卡的接口状态变化，可能会发生虚拟机的虚拟网卡接口的状态与物理网卡接口的状态不一致，从而发生特定场景下虚拟机业务无法正常运行的情况。为了使虚拟机能够感知到物理网卡的接口状态变化，可以根据各虚拟机的虚拟网卡接口与物理网卡接口的关联，维护对应的接口响应链，以便物理网卡接口的状态发生变化时，能够根据该接口响应链向对应的虚拟机通知该物理网卡接口状态变化。
举例来说，假设如图1A所示，主机100上部署有虚拟机111和虚拟机112，虚拟机111和虚拟机112分别通过虚拟网卡接口12A1和虚拟网卡接口12B1与物理网卡接口13C相联系，则主机100可以维护如表1所示的接口响应链：
表1
虚拟机111 虚拟网卡接口12A1 物理网卡接口13C
虚拟机112 虚拟网卡接口12B1 物理网卡接口13C
作为一种可选的实施方式，上述维护接口响应链，可以包括：当虚拟机被创建时，判断该虚拟机是否使能物理网卡接口状态响应功能；若是，则创建该虚拟机对应的接口响应链。
为了提高本发明实施例提供的技术方案的可控性，可以为虚拟机引入物理网卡接口状态响应功能。并且，当虚拟机使能了物理网卡接口状态响应功能时，需要为该虚拟机创建对应的接口响应链，并根据该接口响应链进行物理网卡接口状态变化通知。当虚拟机未使能物理网卡接口状态响应功能时，不需要为该虚拟机创建对应的接口响应链，也不需要进行物理网卡接口状态变化通知。
相应地，当虚拟机被创建时，可以判断该虚拟机是否使能物理网卡接口状态响应功能。若该虚拟机使能了物理网卡接口状态响应功能，则可以创建该虚拟机对应的接口响应链。否则，可以不用创建该虚拟机对应的接口响应链。
例如，可以在虚拟机的配置文件中增加一个用于指示虚拟机是否使能物理网卡接口 状态响应功能的字段。当该字段的值为第一标识值时，表明对应的虚拟机使能了物理网卡接口状态响应功能；当该字段的值为第二标识值时，表明对应的虚拟机未使能物理网卡接口状态响应功能。这样，可以根据虚拟机的配置文件中的该字段的值，确定该虚拟机是否使能了物理网卡接口状态响应功能。并且，当确定虚拟机使能了物理网卡接口状态响应功能时，创建该虚拟机对应的接口响应链。
在创建虚拟机对应的接口响应链之后，还可以包括：当该虚拟机添加虚拟网卡接口或删除虚拟网卡接口时，更新该虚拟机对应的接口响应链；或者当该虚拟机被删除时，删除该虚拟机对应的接口响应链。
当为虚拟机创建接口响应链之后，还可以根据该虚拟机的虚拟网卡接口变化(包括添加虚拟网卡接口和删除虚拟网卡接口等)或虚拟机自身的变化(如删除虚拟机等)，更新自身维护的该虚拟机对应的接口响应链。
其中，当检测到虚拟机添加虚拟网卡接口时，可以在该接口响应链中新增该添加的虚拟网卡接口与其关联的物理网卡接口之间的对应关系。举例来说，以表1所示的虚拟机111的接口响应链为例，假设如图1B所示，虚拟机111上新增虚拟网卡接口12A2，且虚拟网卡接口12A2与物理网卡接口13D关联，则更新后的虚拟机111的接口响应链可以如表2所示：
表2
Figure PCTCN2018092731-appb-000001
当检测到虚拟机删除虚拟网卡接口时，可以删除该虚拟机自身维护的接口响应链中与该虚拟网卡接口对应的信息。
当检测到该虚拟机被删除时，可以删除自身维护的该虚拟机对应的接口响应链。
步骤102、根据接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态。
在维护接口响应链之后，可以根据接口响应链将虚拟网卡接口的状态控制为与对应的物理网卡接口的状态一致。
作为一种实施方式，当一个虚拟网卡接口与单个物理网卡接口关联时，根据接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态，包括： 对于任一虚拟网卡接口，当该虚拟网卡接口关联的物理网卡接口的状态由UP(开启)状态变化为Down(关闭)状态时，将该虚拟网卡接口的状态切换为Down状态；当该虚拟网卡接口关联的物理网卡接口的状态由Down状态变化为UP状态时，将该虚拟网卡接口的状态切换为UP状态。
在该实施方式中，当一个虚拟网卡接口与一个物理网卡接口关联时，若检测到某虚拟网卡接口(下文中称为目标虚拟网卡接口)关联的物理网卡接口的状态由UP状态变化为Down状态时，可以将目标虚拟网卡接口切换为Down状态。当检测到目标虚拟网卡接口关联的物理网卡接口的状态由Down状态变化为UP状态时，可以将目标虚拟网卡接口切换为UP状态。
举例来说，以表1所示的接口响应链为例，假设主机100检测到物理网卡接口13C状态由UP状态变化为Down状态，则主机100可以将虚拟网卡接口12A1以及虚拟网卡接口12B1切换为Down状态。
作为另一种实施方式，当一个虚拟网卡接口与多个物理网卡接口关联时，根据接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态，包括：对于任一虚拟网卡接口，当该虚拟网卡接口关联的多个物理网卡接口的状态均由UP状态变化为Down状态时，控制该虚拟网卡接口的状态切换为Down状态；当该虚拟网卡接口关联的多个物理网卡中至少一个物理网卡接口的状态由Down状态切换为UP状态时，控制该虚拟网卡接口的状态切换为UP状态。
在该实施方式中，当一个虚拟网卡接口与多个物理网卡接口关联时，若目标虚拟网卡接口关联的多个物理网卡接口的状态均由UP状态变化为Down状态，则确定目标虚拟网卡接口关联的物理网卡接口状态为Down，从而可以将目标虚拟网卡接口的状态切换为Down状态。若目标虚拟网卡接口关联的多个物理网卡接口中至少一个物理网卡接口的状态由Down状态变化为UP状态，则确定目标虚拟网卡接口关联的物理网卡接口状态为UP，从而可以将目标虚拟网卡接口的状态切换为UP状态。
举例来说，假设如图1C所示，主机100-2维护的接口响应链如表3所示：
表3
Figure PCTCN2018092731-appb-000002
在该示例中，当主机100-2检测到物理网卡接口13E1和物理网卡接口13E2的状态均由UP状态变化为Down状态时，主机100-2可以将虚拟网卡接口12C1的状态切换为Down状态。
当物理网卡接口13E1和物理网卡接口13E2的状态均为Down状态，且主机100-2检测到物理网卡接口13E1由Down状态变化为UP状态时，主机100-2可以将虚拟网卡接口12C1的状态切换为UP状态。
可见，在图1所示的方法流程中，通过维护接口响应链，并根据接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态，可以有效保证虚拟网卡接口与对应的物理网卡接口状态一致。
为了使本领域技术人员更好地理解本发明实施例提供的技术方案，下面结合具体应用场景对本发明实施例提供的技术方案进行说明。
请参见图2，为本发明实施例提供的一种具体应用场景的示意图，如图2所示，在该应用场景中，主机(Host)200A上存在两个虚拟机(VM)211、212。其中，VM 211的虚拟网卡211A1上的虚拟网卡接口2111A1和VM 212的虚拟网卡212A2上的虚拟网卡接口2121A2通过Linux(一种操作系统)bridge(桥)2410与物理网卡250A的物理网卡接口251A相连。这样，VM 211、212可经由物理网卡250A连接至上层网络260。
主机200B上存在VM 220。并且，VM 220的虚拟网卡220B上的虚拟网卡接口2201B通过Linux桥2420与物理网卡250B的物理网卡接口251B相连。这样，VM 220可经由物理网卡250B连接至上层网络260。
主机200C上存在VM 231、VM 232、VM 233。其中，VM 231的虚拟网卡231C1上的虚拟网卡接口2311C1与Linux桥2431相连，VM 232的虚拟网卡232C2上的虚拟网卡接口2321C2和VM 233的虚拟网卡233C3上的虚拟网卡接口2331C3与Linux桥2432相连。并且，Linux桥2431和Linux桥2432通过Linux桥2433与物理网卡250C的物理网卡接口251C相连。这样，VM 231、232、233可经由物理网卡250C连接至上层网络260。
在该实施例中，虚拟机的配置文件中新增一个用于指示虚拟机是否使能物理网卡接口状态响应功能的字段，如physical status(物理状态)字段。当该字段的值为第一标识值(如0x1)时，表明该虚拟机使能物理网卡接口状态响应功能。当该字段的值为第二标识值(如0x0)时，表明该虚拟机未使能物理网卡接口状态响应功能。
在该实施例中，虚拟机使用的网卡资源为普通虚拟网卡，虚拟化层(hypervisor)监控物理网卡接口的状态。当内核通报物理网卡接口UP/Down事件时，由虚拟化层控制对应虚拟网卡接口的状态变化。
基于图2所示的应用场景，本发明实施例提供的接口状态控制方案实现流程如下：
首先，主机200A、主机200B和主机200C的虚拟化层分别判断本机的虚拟机是否使能了物理网卡接口状态响应功能。
在该实施例中，假设虚拟机211、虚拟机212、虚拟机220、虚拟机231、虚拟机232和虚拟机233的配置文件中的physical status字段均为“0x1”，即各虚拟机均使能了物理网卡接口状态响应功能；
接着，主机200A、主机200B和主机200C的虚拟化层分别维护如表4、表5和表6所示的接口响应链：
表4
虚拟机211 虚拟网卡接口2111A1 物理网卡接口251A
虚拟机212 虚拟网卡接口2121A2 物理网卡接口251A
表5
虚拟机220 虚拟网卡接口2201B 物理网卡接口251B
表6
虚拟机231 虚拟网卡接口2311C1 物理网卡接口251C
虚拟机232 虚拟网卡接口2321C2 物理网卡接口251C
虚拟机233 虚拟网卡接口2331C3 物理网卡接口251C
可见，在本发明实施例中，当存在多层Linux bridge嵌套部署的情况(如主机200C)时，主机记录该通过多层Linux bridge相互连接的虚拟网卡接口与物理网卡接口之间的对应关系。
假设某一时刻，主机200A的虚拟化层接收到内核通报的物理网卡接口250A的状态由UP状态变化为Down状态事件。这时，主机200A的虚拟化层可以分别将虚拟网卡 接口2111A1和虚拟网卡接口2121A2的状态切换为Down状态。后续，当主机200A的虚拟化层接收到内核通报的物理网卡接口250A的状态由Down状态变化为UP状态事件时，主机200A的虚拟化层可以分别将虚拟网卡接口2111A1和虚拟网卡接口2121A2的状态切换为UP状态。
主机200B和主机200C的虚拟化层也可以按照以上所描述的进行物理网卡接口状态变化通知，其具体实现在此不做赘述。
请参见图3，为本发明实施例提供的一种报文传输方法的流程示意图。其中，该报文传输方法可以应用于使能NFV的主机，如图3所示，该报文传输方法可以包括以下步骤301～304。
需要说明的是，步骤301～步骤304的执行主体可以为上述主机或主机中的管理模块，如CPU(Center Process Unit，中央处理单元)。为便于描述，以下以步骤301～步骤304的执行主体为主机为例进行说明。
在步骤301、维护虚拟机的接口响应链。其中，该接口响应链包括属于该虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系。
主机维护虚拟机的接口响应链的具体实现可以参见图1所示方法流程中的相关描述，在此不再赘述。
步骤302、根据接口响应链中与目标虚拟网卡接口对应的物理网卡接口的状态，确定该目标虚拟网卡接口的状态。
其中，目标虚拟网卡接口并不特指某一固定的虚拟网卡接口，而是可以指代主机上部署的任一虚拟机的将用于传输报文的任一虚拟网卡接口。
当主机通过目标虚拟网卡接口传输报文时，主机可以根据该目标虚拟网卡接口查询自身维护的接口响应链，以确定该目标虚拟网卡接口关联的物理网卡接口，进而，根据该目标虚拟网卡接口关联的物理网卡接口的状态确定该目标虚拟网卡接口的状态。
举例来说，假设目标虚拟网卡接口与单个物理网卡接口关联，则当目标虚拟网卡接口关联的物理网卡接口为UP状态时，主机可以确定该目标虚拟网卡接口为UP状态；当目标虚拟网卡接口关联的物理网卡接口为Down状态时，主机可以确定该目标虚拟网卡接口为Down状态。
又举例来说，假设目标虚拟网卡接口与多个物理网卡接口关联，则当目标虚拟网卡 接口关联的多个物理网卡接口中至少一个物理网卡接口为UP状态时，主机可以确定该目标虚拟网卡接口为UP状态；当目标虚拟网卡接口关联的多个物理网卡接口均为Down状态时，主机可以确定该目标虚拟网卡接口为Down状态。
步骤303、当确定该目标虚拟网卡接口为UP状态时，通过该目标虚拟网卡接口传输报文。
本发明实施例中，当主机确定目标虚拟网卡接口为UP状态时，主机可以通过该目标虚拟网卡接口传输报文。
步骤304、当目标虚拟网卡接口为Down状态时，拒绝通过该目标虚拟网卡接口传输报文。
本发明实施例中，当主机确定目标虚拟网卡接口为Down状态时，主机将会拒绝通过该目标虚拟网卡接口传输报文。
通过以上描述可以看出，在本发明实施例提供的技术方案中，通过维护接口响应链，并根据接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态，可以有效保证虚拟网卡接口与对应的物理网卡接口状态一致。
以上对本发明提供的方法进行了描述。下面对本发明提供的装置进行描述。
图4为本发明实施例提供的一种接口状态控制装置的硬件结构示意图。该接口状态控制装置可包括处理器401、存储有机器可执行指令的机器可读存储介质402。处理器401与机器可读存储介质402可经由系统总线403通信。并且，通过读取并执行机器可读存储介质402中与接口状态控制逻辑对应的机器可执行指令，处理器401可执行上文描述的接口状态控制方法。
本文中提到的机器可读存储介质402可以是任何电子、磁性、光学或其它物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，机器可读存储介质可以是易失存储器、非易失性存储器或者类似的存储介质。具体地，机器可读存储介质可以是RAM(Radom Access Memory，随机存取存储器)、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、dvd等)或者它们的组合。
如图5所示，从功能上划分，上述接口状态控制逻辑可以包括维护单元501和控制单元502。其中：维护单元501，用于维护虚拟机的接口响应链，所述接口响应链包括属于该虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系；控制单元502，用于根据所述接口响应链中物理网卡接口的状态控制与该物理网卡 接口关联的虚拟网卡接口的状态。
根据一示例，所述维护单元501具体用于当虚拟机被创建时，判断该虚拟机是否使能物理网卡接口状态响应功能。若是，则创建该虚拟机对应的接口响应链。
此外，所述维护单元501还用于当该虚拟机添加虚拟网卡接口或删除虚拟网卡接口时更新该虚拟机对应的接口响应链，以及当该虚拟机被删除时删除该虚拟机对应的接口响应链。
根据另一示例，所述控制单元502具体用于：对于与一个物理网卡接口关联的第一虚拟网卡接口，若该第一虚拟网卡接口关联的物理网卡接口由开启UP状态变化为关闭Down状态，则控制该第一虚拟网卡接口切换为Down状态；若该第一虚拟网卡接口关联的物理网卡接口由Down状态变化为UP状态时，则控制该第一虚拟网卡接口切换为UP状态。
此外，所述控制单元502还具体用于：对于与多个物理网卡接口关联的第二虚拟网卡接口，若该第二虚拟网卡接口关联的多个物理网卡接口均为Down状态，则控制该虚拟网卡接口为Down状态；若该第二虚拟网卡接口关联的多个物理网卡接口中至少一个物理网卡接口为UP状态时，则控制该第二虚拟网卡接口为UP状态。
图6为本发明实施例提供的一种报文传输装置的硬件结构示意图。该报文传输装置可包括处理器601、存储有机器可执行指令的机器可读存储介质602。处理器601与机器可读存储介质602可经由系统总线603通信。并且，通过读取并执行机器可读存储介质602中与报文传输控制逻辑对应的机器可执行指令，处理器601可执行上文描述的报文传输方法。
本文中提到的机器可读存储介质602可以是任何电子、磁性、光学或其它物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，机器可读存储介质可以是易失存储器、非易失性存储器或者类似的存储介质。具体地，机器可读存储介质可以是RAM(Radom Access Memory，随机存取存储器)、闪存、存储驱动器、固态硬盘、任何类型的存储盘或者它们的组合。
如图7所示，从功能上划分，上述报文传输控制逻辑可以包括维护单元701、确定单元702和传输单元703。其中：维护单元701，用于维护虚拟机的接口响应链，所述接口响应链包括属于该虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系；确定单元702，用于根据接口响应链中目标虚拟网卡接口对应的物 理网卡接口的状态，确定所述目标虚拟网卡接口的状态；传输单元703，用于当确定所述目标虚拟网卡接口为开启UP状态时，通过所述目标虚拟网卡接口传输报文，而当确定所述目标虚拟网卡接口为关闭Down状态时，拒绝通过该目标虚拟网卡接口传输报文。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上所述仅为本发明的较佳实施例而已，并不用以限制本发明，凡在本发明的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本发明保护的范围之内。

Claims (15)

  1. 一种接口状态控制方法，包括：
    使能了网络功能虚拟化的主机维护所述主机上部署的虚拟机的接口响应链，其中，所述接口响应链包括属于所述虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系；
    所述主机根据所述接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态。
  2. 根据权利要求1所述的方法，其特征在于，所述维护所述主机上部署的虚拟机的接口响应链，包括：
    当虚拟机被创建时，所述主机判断该虚拟机是否使能了物理网卡接口状态响应功能；
    若是，则所述主机创建该虚拟机对应的接口响应链。
  3. 根据权利要求2所述的方法，其特征在于，所述维护所述主机上部署的虚拟机的接口响应链，还包括以下任意一个或多个：
    当该虚拟机添加虚拟网卡接口或删除虚拟网卡接口时，所述主机更新该虚拟机对应的接口响应链；
    当该虚拟机被删除时，所述主机删除该虚拟机对应的接口响应链。
  4. 根据权利要求1所述的方法，其特征在于，所述根据所述接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态，包括：
    对于与一个物理网卡接口关联的第一虚拟网卡接口，当该第一虚拟网卡接口关联的物理网卡接口由开启状态变化为关闭状态时，所述主机控制该第一虚拟网卡接口切换为关闭状态；
    当该第一虚拟网卡接口关联的物理网卡接口由关闭状态变化为开启状态时，所述主机控制该第一虚拟网卡接口切换为开启状态。
  5. 根据权利要求1所述的方法，其特征在于，所述根据所述接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态，包括：
    对于与多个物理网卡接口关联的第二虚拟网卡接口，当该第二虚拟网卡接口关联的多个物理网卡接口均为关闭状态时，所述主机控制该第二虚拟网卡接口为关闭状态；
    当该第二虚拟网卡接口关联的至少一个物理网卡接口为开启状态时，所述主机控制该第二虚拟网卡接口为开启状态。
  6. 一种接口状态控制装置，应用于使能了网络功能虚拟化的主机，包括：
    维护单元，用于维护所述主机上部署的虚拟机的接口响应链，其中，所述接口响应链包括属于所述虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系；
    控制单元，用于根据所述接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态。
  7. 根据权利要求6所述的装置，其特征在于，所述维护单元具体用于
    当虚拟机被创建时，判断该虚拟机是否使能物理网卡接口状态响应功能；
    若是，则创建该虚拟机对应的接口响应链。
  8. 根据权利要求7所述的装置，其特征在于，所述维护单元，还用于
    当该虚拟机添加虚拟网卡接口或删除虚拟网卡接口时，更新该虚拟机对应的接口响应链；
    当该虚拟机被删除时，删除该虚拟机对应的接口响应链。
  9. 根据权利要求6所述的装置，其特征在于，所述控制单元，具体用于
    对于与一个物理网卡接口关联的第一虚拟网卡接口，当该第一虚拟网卡接口关联的物理网卡接口由开启状态变化为关闭状态时，控制该第一虚拟网卡接口切换为关闭状态；
    当该第一虚拟网卡接口关联的物理网卡接口由关闭状态变化为开启状态时，控制第一该虚拟网卡接口切换为开启状态。
  10. 根据权利要求6所述的装置，其特征在于，所述控制单元，具体用于
    对于与多个物理网卡接口关联的第二虚拟网卡接口，当该第二虚拟网卡接口关联的多个物理网卡接口均为关闭状态时，控制该第二虚拟网卡接口为关闭状态；
    当该第二虚拟网卡接口关联的至少一个物理网卡接口为开启状态时，控制该第二虚拟网卡接口为开启状态。
  11. 一种接口状态控制装置，应用于使能了网络功能虚拟化的主机，包括处理器和非暂时性机器可读存储介质，
    所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令，
    所述处理器被所述机器可执行指令促使：
    维护所述主机上部署的虚拟机的接口响应链，其中，所述接口响应链包括属于所述虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系；
    根据所述接口响应链中物理网卡接口的状态控制与该物理网卡接口关联的虚拟网卡接口的状态。
  12. 根据权利要求11所述的装置，其特征在于，所述处理器还被所述机器可执行指令促使：
    当所述虚拟机被创建时，所述主机判断该虚拟机是否使能了物理网卡接口状态响应功能；
    若是，则所述主机创建该虚拟机对应的接口响应链。
  13. 一种报文传输方法，包括：
    使能了网络功能虚拟化的主机维护所述主机上部署的虚拟机的接口响应链，其中，所述接口响应链包括属于所述虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系；
    当需要通过目标虚拟网卡接口传输报文时，所述主机根据所述接口响应链中与所述目标虚拟网卡接口对应的物理网卡接口的状态，确定所述目标虚拟网卡接口的状态；
    当确定所述目标虚拟网卡接口为开启状态时，所述主机通过所述目标虚拟网卡接口传输报文；
    当确定所述目标虚拟网卡接口为关闭状态时，所述主机拒绝通过该目标虚拟网卡接口传输报文。
  14. 一种报文传输装置，应用于使能了网络功能虚拟机化的主机，包括：
    维护单元，用于维护所述主机上部署的虚拟机的接口响应链，其中，所述接口响应链包括属于所述虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系；
    确定单元，用于当需要通过目标虚拟网卡接口传输报文时，根据所述接口响应链中与所述目标虚拟网卡接口对应的物理网卡接口的状态来确定所述目标虚拟网卡接口的状态；
    传输单元，用于当所述确定单元确定所述目标虚拟网卡接口为开启状态时，通过所述目标虚拟网卡接口传输报文；当所述确定单元确定所述目标虚拟网卡接口为关闭状态时，拒绝通过该目标虚拟网卡接口传输报文。
  15. 一种报文传输装置，应用于使能了网络功能虚拟化的主机，包括处理器和非暂时性机器可读存储介质，
    所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令，
    所述处理器被所述机器可执行指令促使：
    维护所述主机上部署的虚拟机的接口响应链，其中，所述接口响应链包括属于所述虚拟机的虚拟网卡接口与该虚拟网卡接口所关联的物理网卡接口之间的对应关系；
    当需要通过目标虚拟网卡接口传输报文时，根据所述接口响应链中与所述目标虚拟网卡接口对应的物理网卡接口的状态确定所述目标虚拟网卡接口的状态；
    当确定所述目标虚拟网卡接口为开启状态时，通过所述目标虚拟网卡接口传输报文；
    当确定所述目标虚拟网卡接口为关闭状态时，拒绝通过该目标虚拟网卡接口传输报文。
PCT/CN2018/092731 2017-06-27 2018-06-26 虚拟网卡接口的状态控制和报文传输 WO2019001398A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710503089.7A CN108322326B (zh) 2017-06-27 2017-06-27 一种接口状态控制方法、报文传输方法及装置
CN201710503089.7 2017-06-27

Publications (1)

Publication Number Publication Date
WO2019001398A1 true WO2019001398A1 (zh) 2019-01-03

Family

ID=62891472

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/092731 WO2019001398A1 (zh) 2017-06-27 2018-06-26 虚拟网卡接口的状态控制和报文传输

Country Status (2)

Country Link
CN (1) CN108322326B (zh)
WO (1) WO2019001398A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111443982A (zh) * 2019-01-16 2020-07-24 瑞昱半导体股份有限公司 虚拟机器的通讯方法、电子装置以及非暂态电脑可读取记录媒体
US10992515B1 (en) 2019-06-10 2021-04-27 Cisco Technology, Inc. Link state tracking for virtual interfaces
EP3974989A4 (en) * 2019-09-11 2023-07-12 ZTE Corporation METHOD AND DEVICE FOR SETTING LINK STATE FOR VIRTUAL NETWORK INTERFACE CARD, AND STORAGE MEDIA

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109617905B (zh) * 2018-12-29 2022-04-08 新华三技术有限公司 多播攻击的处理方法、装置和实现装置
CN110943941B (zh) * 2019-12-06 2022-03-11 北京天融信网络安全技术有限公司 一种报文接收方法、网卡及电子设备
CN111147340A (zh) * 2019-12-26 2020-05-12 山东超越数控电子股份有限公司 一种对can总线接口进行网络化访问的方法、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101129032A (zh) * 2005-02-25 2008-02-20 Ip输入公司 硬件抽象层
US20110078334A1 (en) * 2009-09-29 2011-03-31 Hitachi, Ltd. Methods and apparatus for managing virtual ports and logical units on storage systems
US20130055240A1 (en) * 2011-08-22 2013-02-28 Vmware, Inc. Virtual port command processing during migration of virtual machine

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8665747B2 (en) * 2009-12-03 2014-03-04 Cisco Technology, Inc. Preventing loops on network topologies built with virtual switches and VMS
CN102609298B (zh) * 2012-01-11 2016-01-13 中国科学技术大学苏州研究院 基于硬件队列扩展的网卡虚拟化系统及其方法
CN103428226B (zh) * 2013-08-30 2017-04-19 天津汉柏汉安信息技术有限公司 一种用户态与内核通信的方法与系统
CN106878204B (zh) * 2016-12-21 2020-09-08 新华三技术有限公司 一种虚拟机的创建方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101129032A (zh) * 2005-02-25 2008-02-20 Ip输入公司 硬件抽象层
US20110078334A1 (en) * 2009-09-29 2011-03-31 Hitachi, Ltd. Methods and apparatus for managing virtual ports and logical units on storage systems
US20130055240A1 (en) * 2011-08-22 2013-02-28 Vmware, Inc. Virtual port command processing during migration of virtual machine

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111443982A (zh) * 2019-01-16 2020-07-24 瑞昱半导体股份有限公司 虚拟机器的通讯方法、电子装置以及非暂态电脑可读取记录媒体
CN111443982B (zh) * 2019-01-16 2023-02-24 瑞昱半导体股份有限公司 虚拟机器的通讯方法、电子装置以及非暂态电脑可读取记录媒体
US10992515B1 (en) 2019-06-10 2021-04-27 Cisco Technology, Inc. Link state tracking for virtual interfaces
US11362883B1 (en) 2019-06-10 2022-06-14 Cisco Technology, Inc. Link state tracking for virtual interfaces
EP3974989A4 (en) * 2019-09-11 2023-07-12 ZTE Corporation METHOD AND DEVICE FOR SETTING LINK STATE FOR VIRTUAL NETWORK INTERFACE CARD, AND STORAGE MEDIA

Also Published As

Publication number Publication date
CN108322326B (zh) 2021-02-26
CN108322326A (zh) 2018-07-24

Similar Documents

Publication Publication Date Title
WO2019001398A1 (zh) 虚拟网卡接口的状态控制和报文传输
US11675746B2 (en) Virtualized server systems and methods including domain joining techniques
US10402341B2 (en) Kernel-assisted inter-process data transfer
EP2879053B1 (en) Virtual machine memory data migration method, related apparatus, and cluster system
EP3117322B1 (en) Method and system for providing distributed management in a networked virtualization environment
CN104094231B (zh) 用于支持无限带网络中的虚拟机的动态迁移的系统和方法
JP6077562B2 (ja) 分散型アプリケーション・オブジェクトに関するアップデート通知の提供
US10592434B2 (en) Hypervisor-enforced self encrypting memory in computing fabric
US8707417B1 (en) Driver domain as security monitor in virtualization environment
US9565095B2 (en) Take-over of network frame handling in a computing environment
US11748006B1 (en) Mount path management for virtual storage volumes in a containerized storage environment
US20130232491A1 (en) Virtual machine communication
US9152447B2 (en) System and method for emulating shared storage
KR101733903B1 (ko) 피어 모니터에서 신뢰성, 이용 가능성 및 서비스 가능성(ｒａｓ) 흐름들을 지원하기 위한 메커니즘
US9547514B2 (en) Maintaining virtual hardware device ID in a virtual machine
WO2013036261A1 (en) Virtual switch extensibility
US20140115576A1 (en) Extensible Network Configuration Management
US20130125115A1 (en) Policy enforcement by hypervisor paravirtualized ring copying
WO2015058724A1 (zh) 云系统数据管理方法
US20180054357A1 (en) Discovering Changes of Network Interface Controller Names
WO2016106756A1 (zh) 一种容灾方法、系统和装置
US20230315584A1 (en) Backing up data for a namespace assigned to a tenant
US10372472B2 (en) System, method, and computer program product for conditionally preventing use of hardware virtualization
US20210344719A1 (en) Secure invocation of network security entities
JP2013191090A (ja) バックアップ制御プログラム、バックアップ制御方法、および情報処理装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18823328

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18823328

Country of ref document: EP

Kind code of ref document: A1