Browse Prior Art Database

KVM Dynamic Network Allocation to External Device

IP.com Disclosure Number: IPCOM000218184D
Publication Date: 2012-May-25
Document File: 2 page(s) / 48K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a KDNA (KVM Dynamic Network Allocation) module which provides a user-friendly yet flexible mechanism for KVM virtual technology when it comes to its network deployments, expansion, bandwidth utilization and management. The proposed KDNA (KVM Dynamic Network Allocation) module which enables us to dynamically add, remove or change network segments into designated ports of host machine. Multiple network segments can co-exist in the same physical port, making the most of its bandwidth. There is no additional NICs required, nor is there a need to change switch settings.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

KVM Dynamic Network Allocation to External Device

    1. Background: This invention is intended to enhance the network capability of KVM virtualizaion. Kernel based virtual (KVM) is one of the most famous virtual machine technologies in the world. When it comes to networking, KVM supports bridges and NAT by default which serves to a wide range of user scenarios. When a host invokes a VM (Virtual Machine), the VM is able to communicate to the external device without knowing that it's being wrapped inside a host machine. On the host machine side, the host needs to set up proper configurations, bridging its virtual network interfaces (TAP) to physical interfaces (eth). In order to make this mechanism more useful in the real world, the host machine is usually connected to external network device such as switches that allows switching of network connectivity to different target device that directly or indirectly connect to it. This is usually achieved by changing Vlans of the switch.

    The downside of this is that whenever the host machine wants to connect to different target device, it is unavoidable to have to change the vlan IDs of the switch ports that physical interfaces of host machine connect to. However, what if we want to have more than one VMs concurrently running and connect to various external device without having to alter vlans sequentially. To achieve this, we would have to add more NICs to host.

This can be impractical in several aspects:

    a. To add new NICs, the host may need to be shutdown, meaning all running Vms need to be down as well.


b. There are only limited number of slots for NIC expansion.

    c. Both switch and host need to be configured if we want to change network with current hardware state.

    d. One port can only be used by one VM without interference at the same time.

    2. Description of the disclosure: The proposed solution is to create a KDNA (KVM Dynamic Network Allocation) module which enables us to dynamically add, remove or change network segments into designated ports of host machine. Multiple network segments can co-exist in the same physical port, making the most of its b...