Changes

== Approaches ==

=== Virtualization on the 2nd level (OpenVZ) ===

The main requirement is that containers should have close to standalone servers networking capabilities. In details:

For input packets context switching is performed in netif_receive_skb(), inherited from the device context. For output, context is inherited from the socket one.

=== Virtualization on the 3d level (IBM) ===

# One can ran servers in several containers listening on *:port without conflict and __without__ forcing the bind to use the IP address assigned to the container;

# The source address will be filled with the container IP address;

# have broadcast and multicast working.

For input packets context switching is inherited from the routing entry, for output - inherited from the socket one.

=== Sockets isolation (Linux-VServer) ===

# all interfaces and IPs are visible on the host

# routing and iptables is configured on the host

# Guest-Guest and Guest-Host traffic via Loopback

Network Context with 'assigned' set of IPs, which are used for 'collision' checks at bind

== Virtualization table ==

{| class="wikitable"