Virtualization in Grid'5000: Difference between revisions

From Grid5000
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
{{Author|Hyacinthe Cartiaux}}
{{Maintainer|Hyacinthe Cartiaux}}
{{Maintainer|Hyacinthe Cartiaux}}
{{Status|In production}}
{{Status|In production}}
Line 76: Line 77:
=== Disk image, virtual machine ===
=== Disk image, virtual machine ===


A disk image containing debian squeeze is available at the following path:
A disk image containing debian wheezy is available at the following path:
<code class="command">/grid5000/images/KVM/squeeze-x64-base.qcow2</code>
<code class="command">/grid5000/images/KVM/wheezy-x64-base.qcow2</code>


It can be used as a base for more advanced work.
It can be used as a base for more advanced work.
For the next steps of this tutorial, copy the disk image to /tmp on the node:
For the next steps of this tutorial, copy the disk image to /tmp on the node:


{{Term|location=node|cmd=<code class="command">cp /grid5000/images/KVM/squeeze-x64-base.qcow2 /tmp/</code>}}
{{Term|location=node|cmd=<code class="command">cp /grid5000/images/KVM/wheezy-x64-base.qcow2 /tmp/</code>}}


=== Network configuration ===
=== Network configuration ===
Line 152: Line 153:
The kvm process is launched in a <code class="command">screen</code> session, if you are not familiar with screen, read its [[Screen|documentation]].
The kvm process is launched in a <code class="command">screen</code> session, if you are not familiar with screen, read its [[Screen|documentation]].


{{Term|location=node|cmd=<code class="command">screen kvm -m 512 -hda '''/tmp/squeeze-x64-base.qcow2''' -cdrom '''/tmp/kvm-context-10.172.0.1.iso''' -net nic,model=virtio,macaddr='''00:16:3E:AC:00:01''' -net tap,ifname='''tap0''',script=no -nographic</code>}}
{{Term|location=node|cmd=<code class="command">screen kvm -m 512 -hda '''/tmp/wheezy-x64-base.qcow2''' -cdrom '''/tmp/kvm-context-10.172.0.1.iso''' -net nic,model=virtio,macaddr='''00:16:3E:AC:00:01''' -net tap,ifname='''tap0''',script=no -nographic</code>}}


{{Note|text=- <code class="command">tap0</code> is the name of our Tun/Tap interface. Adapt it with the Tun/Tap name on which you want to attach your guest OS. <br />
{{Note|text=- <code class="command">tap0</code> is the name of our Tun/Tap interface. Adapt it with the Tun/Tap name on which you want to attach your guest OS. <br />
Line 171: Line 172:
<pre class="brush: bash">
<pre class="brush: bash">
  <domain type='kvm'>
  <domain type='kvm'>
   <name>squeeze</name>
   <name>wheezy</name>
   <memory>524288</memory>
   <memory>524288</memory>
   <vcpu>1</vcpu>
   <vcpu>1</vcpu>
Line 185: Line 186:
     <disk type='file' device='disk'>
     <disk type='file' device='disk'>
       <driver type='qcow2'/>
       <driver type='qcow2'/>
       <source file='/tmp/squeeze-x64-base.qcow2'/>
       <source file='/tmp/wheezy-x64-base.qcow2'/>
       <target dev='vda' bus='virtio'/>
       <target dev='vda' bus='virtio'/>
     <shareable/>
     <shareable/>
Line 219: Line 220:
* You can also use <code class="command">virsh</code> to manage your guest OS:
* You can also use <code class="command">virsh</code> to manage your guest OS:
** list the running virtual machines: <code class="command">virsh list</code>
** list the running virtual machines: <code class="command">virsh list</code>
** open a console on the "squeeze" virtual machine: <code class="command">virsh console squeeze</code>
** open a console on the "wheezy" virtual machine: <code class="command">virsh console wheezy</code>


{{Note|text=Use <code class="command">CTRL+AltGr+]</code> to disconnect from <code class="command">virsh console</code>}}
{{Note|text=Use <code class="command">CTRL+AltGr+]</code> to disconnect from <code class="command">virsh console</code>}}
Line 415: Line 416:
=== Copy a standard virtual machine image ===
=== Copy a standard virtual machine image ===


Copy the default virtual machine image from <code class="file">/grid5000/images/KVM/squeeze-x64-base.qcow2</code> to <code class="file">/tmp</code>
Copy the default virtual machine image from <code class="file">/grid5000/images/KVM/wheezy-x64-base.qcow2</code> to <code class="file">/tmp</code>


{| width="100%"
{| width="100%"
|-  
|-  
| width="50%" |  
| width="50%" |  
{{Term|location=node(nancy)|cmd=<code class="command">cp /grid5000/images/KVM/squeeze-x64-base.qcow2 /tmp/</code>}}
{{Term|location=node(nancy)|cmd=<code class="command">cp /grid5000/images/KVM/wheezy-x64-base.qcow2 /tmp/</code>}}
||
||
| width="50%" |  
| width="50%" |  
{{Term|location=node(luxembourg)|cmd=<code class="command">cp /grid5000/images/KVM/squeeze-x64-base.qcow2 /tmp/</code>}}
{{Term|location=node(luxembourg)|cmd=<code class="command">cp /grid5000/images/KVM/wheezy-x64-base.qcow2 /tmp/</code>}}
|}
|}


Line 435: Line 436:
<pre class="brush: bash">
<pre class="brush: bash">
<domain type='kvm'>
<domain type='kvm'>
  <name>squeeze</name>
  <name>wheezy</name>
  <memory>362144</memory>
  <memory>362144</memory>
  <vcpu>1</vcpu>
  <vcpu>1</vcpu>
Line 449: Line 450:
   <disk type='file' device='disk'>
   <disk type='file' device='disk'>
     <driver type='qcow2'/>
     <driver type='qcow2'/>
     <source file='/tmp/squeeze-x64-base.qcow2'/>
     <source file='/tmp/wheezy-x64-base.qcow2'/>
     <target dev='vda' bus='virtio'/>
     <target dev='vda' bus='virtio'/>
     <shareable/>
     <shareable/>
Line 479: Line 480:
<pre class="brush: bash">
<pre class="brush: bash">
<domain type='kvm'>
<domain type='kvm'>
  <name>squeeze</name>
  <name>wheezy</name>
  <memory>362144</memory>
  <memory>362144</memory>
  <vcpu>1</vcpu>
  <vcpu>1</vcpu>
Line 493: Line 494:
   <disk type='file' device='disk'>
   <disk type='file' device='disk'>
     <driver type='qcow2'/>
     <driver type='qcow2'/>
     <source file='/tmp/squeeze-x64-base.qcow2'/>
     <source file='/tmp/wheezy-x64-base.qcow2'/>
     <target dev='vda' bus='virtio'/>
     <target dev='vda' bus='virtio'/>
     <shareable/>
     <shareable/>

Revision as of 13:57, 10 October 2013


Purpose

This page presents how to use KVM on the production environment, with a "non-deploy" reservation. The aim is to permit the execution of virtual machines on the nodes, along with a subnet reservation, which will give you a range of routed IP for your experiment.

In the first part, you will learn the basics of g5k-subnets, which is a prerequisite for the rest of this tutorial. The Quick start explains how to run a VM on the production environment in the minimal number of steps. The next part is optional, it explains in details the contextualization mechanism, which allows you to customize your virtual machines. Finally, in the Multi-site experiment section, we will deploy 2 VMs on 2 sites, and we will measure the network bandwidth between them with iperf.

Prerequisite: Network subnets reservation with g5k-subnets

Users deploying VMs on Grid'5000 need to attribute IP address to them. Each site of Grid'5000 is allocated a /14 block for this purpose, divided in 4 smaller blocks.

To answer this problem, there are two solutions:

  • reserve a range of IPs with OAR, contained in the 3 /16 other blocks. OAR permit to share the IP resources among users, and avoid the potential IP conflicts at the same time. In the following, we will use this solution.
  • use IPs from the last /16 block that are allocated via DHCP. (this solution is not described in this tutorial)

Reservation

Subnet reservation through OAR is similar to normal resource reservation.

To reserve 4 /22 subnets and 2 nodes, just type:

Terminal.png frontend:
oarsub -l slash_22=4+nodes=2 -I

You can of course have more complex request. To obtain 4 /22 on different /19 subnets, you can type:

Terminal.png frontend:
oarsub -l slash_19=4/slash_22=1+nodes=2/core=1 -I

Usage

The simplest way to get the list of your allocated subnets is to use the g5k-subnets script provided on the head node of the submission.

# g5k-subnets
10.8.0.0
10.8.8.0

Several other printing options are available (-p option to display the CIDR format, -b to display broadcast address, -n to see the netmask, and -a is equivalent to -bnp):

# g5k-subnets -a
10.8.0.0/21	10.11.255.255	255.255.252.0	10.11.255.254
10.8.8.0/21	10.11.255.255	255.255.252.0	10.11.255.254

You can also summarize the subnets into a larger one if they are contiguous:

# g5k-subnets -sp
10.8.0.0/20

You can display all the available IP in your reservation, and their associated unique mac addresses, with the following command.

# g5k-subnets -im
10.158.16.1     00:16:3E:9E:10:01
...
Note.png Note

For detailed information, see the Subnet reservation page. The Grid5000:Network page also describes our organization of the virtual IP space inside Grid'5000.

Quick start

In this part, we will create a virtual machine in a few steps, and ssh to it.

Job submission

In order to test easily the kvm environment, we use an interactive job, and we reserve one subnet and one node with hardware virtualization capabilities.

Terminal.png frontend:
oarsub -I -l "slash_22=1+{virtual!='none'}/nodes=1"

Disk image, virtual machine

A disk image containing debian wheezy is available at the following path: /grid5000/images/KVM/wheezy-x64-base.qcow2

It can be used as a base for more advanced work. For the next steps of this tutorial, copy the disk image to /tmp on the node:

Terminal.png node:
cp /grid5000/images/KVM/wheezy-x64-base.qcow2 /tmp/

Network configuration

In order to use the network with kvm, a Tun/Tap interface must be created for each virtual machines. This virtual interface will be attached to your virtual machine, and bridged on the production network. Therefore, the virtual machine will be able to get an IP from the DHCP server and access the network.

A script is available to create automatically this interface on the node: create_tap:

Terminal.png node:
sudo create_tap
  • Tun/Tap interfaces are listed by issuing the command /sbin/ifconfig.
Terminal.png node:
/sbin/ifconfig
tap0      Link encap:Ethernet  HWaddr 00:16:3e:db:c6:41
          inet6 addr: fe80::58ff:a4ff:fe97:c6a8/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:29435 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
Note.png Note

- Create one Tun/Tap interface per guest OS.

- Use tunctl if you need to delete a Tun/Tap device.

Terminal.png node:
/usr/sbin/tunctl -d tap0

Generate the contextualization iso file

This file contains a script which will set the network configration of your VM. First, choose an IP in the range you have reserved. The command g5k-subnets will give you more information.

Terminal.png node:
g5k-subnets -a
10.172.0.0/22   10.175.255.255  255.252.0.0     10.175.255.254  10.172.0.0      dns.luxembourg.grid5000.fr      172.16.191.101

You can get the list of available IP, and an associated unique mac address with the following command.

Terminal.png node:
g5k-subnets -im
10.172.0.1      00:16:3E:AC:00:01
10.172.0.2      00:16:3E:AC:00:02
10.172.0.3      00:16:3E:AC:00:03
10.172.0.4      00:16:3E:AC:00:04
10.172.0.5      00:16:3E:AC:00:05
10.172.0.6      00:16:3E:AC:00:06
10.172.0.7      00:16:3E:AC:00:07
10.172.0.8      00:16:3E:AC:00:08
10.172.0.9      00:16:3E:AC:00:09
10.172.0.10     00:16:3E:AC:00:0A
...
Note.png Note

The mac address is a translation of the IP. Do not change it.

We will now suppose that you want to generate a virtual machine with the IP 10.172.0.1. Do not forget to adapt all the following commands and examples to your subnet reservation.

With the following command, we will create a contextualization iso file:

Terminal.png node:
/grid5000/images/KVM/g5k-vm --ip 10.172.0.1 --iso /tmp/kvm-context-10.172.0.1.iso
Note.png Note

In the previous command, adapt to your case the IP and the contextualization file name.

Run the guest OS using the kvm command

Start the virtual machine with the kvm command. The following command is just an example, feel free to adapt it to your use case. The kvm process is launched in a screen session, if you are not familiar with screen, read its documentation.

Terminal.png node:
screen kvm -m 512 -hda /tmp/wheezy-x64-base.qcow2 -cdrom /tmp/kvm-context-10.172.0.1.iso -net nic,model=virtio,macaddr=00:16:3E:AC:00:01 -net tap,ifname=tap0,script=no -nographic
Note.png Note

- tap0 is the name of our Tun/Tap interface. Adapt it with the Tun/Tap name on which you want to attach your guest OS.

- You must adapt the contextualization iso file name and the mac address to your case

- The password for the root account is grid5000

Or, use libvirt

Libvirt is a toolkit for managing virtualization servers. Libvirt is also an abstraction layer for different virtualization solutions, including KVM but also Xen and VMWare ESX.

In our case, we use libvirt on top of KVM.

  • Create a domain file in XML, describing a virtual machine.

eg : domain.xml

 <domain type='kvm'>
  <name>wheezy</name>
  <memory>524288</memory>
  <vcpu>1</vcpu>
  <os>
    <type arch="x86_64">hvm</type>
  </os>
  <clock offset="localtime"/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='file' device='disk'>
      <driver type='qcow2'/>
      <source file='/tmp/wheezy-x64-base.qcow2'/>
      <target dev='vda' bus='virtio'/>
     <shareable/>
    </disk>
    <disk type='file' device='cdrom'>
      <source file='/tmp/kvm-context-10.172.0.1.iso'/>
      <target dev='vdb' bus='virtio'/>
      <readonly/>
    </disk>
    <interface type='ethernet'>
      <target dev='tap0'/>
      <script path='no'/>
      <model type='virtio'/>
      <mac address='00:16:3E:AC:00:01'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/ttyS0'/>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <source path='/dev/ttyS0'/>
      <target port='0'/>
    </console>
  </devices>
 </domain>
Note.png Note

Adapt this file to your case, you must change the mac address and the path of the contextualization iso file

  • Now, the guest OS can be started.
Terminal.png node:
virsh create domain.xml
  • You can also use virsh to manage your guest OS:
    • list the running virtual machines: virsh list
    • open a console on the "wheezy" virtual machine: virsh console wheezy
Note.png Note

Use CTRL+AltGr+] to disconnect from virsh console

  • At this point, you can repeat the full process and launch several VMs in parallel.

SSH to your virtual machine

Finally, you can ssh directly to your VM:

Terminal.png node:
ssh root@10.172.0.1
Note.png Note

The password for the root account is grid5000



KVM contextualization explained

This part describes the basic usage of a contextualization iso file with KVM, in order to configure the virtual machines (especially the network side). The contextualization script can be easily extended for other purposes.

Mechanism

Principe

Contextualization mechanism works like the following :

  • Test for the presence of a CD in the CD drive of the VM
  • if it exists, mount the CD, test the presence of a script post-install, and run it as root
  • if it does not exist, use dhcp on the first network interface.

Installation

The contextualization mechanism is not standard, if you want to use it on your vm, you must copy and adapt a few scripts.

  • The contextualization script is executed during the boot sequence.

This script can be placed in /etc/rc.local, at the end of the file (before the exit 0 if any).

# KVM contextualization script
/usr/local/bin/init
  • Here is an example of a contextualization script :
#!/bin/bash

DEVICE=
[ -b /dev/hdb ] && DEVICE=/dev/hdb
[ -b /dev/sdb ] && DEVICE=/dev/sdb
[ -b /dev/vdb ] && DEVICE=/dev/vdb
[ -b /dev/xvdb ] && DEVICE=/dev/xvdb
[ -b /dev/sr0 ] && DEVICE=/dev/sr0

if [ -b "$DEVICE" ];then
    /bin/mount -t iso9660 $DEVICE /mnt 2> /dev/null

    if [ -f /mnt/post-install ]; then
      bash /mnt/post-install
    fi

    umount /mnt 2> /dev/null
else
    ifup eth0
fi
exit 0

Generate your contextualization iso file

This part explain how to generate the contextualization iso file manually. Note that the manipulation can be automated with the script g5k-vm.

Terminal.png node:
/grid5000/images/KVM/g5k-vm --ip $IP --iso $ISOFILE
  • A basic example of contextualization iso file is available at /grid5000/images/KVM/kvm-context.tgz on each site.
    • the entry point is the file kvm-context/post-install ;
    • this example configure the network interface using a static IP address and the network information provided in the file kvm-context/common/network ;
    • you can customize that iso file for your experiments.
  • Use the tool genisoimage to generate the contextualization iso file.

Retrieve the file kvm-context.tgz

Uncompress the file /grid5000/images/KVM/kvm-context.tgz in your home directory. This tarball contains an example of contextualization script.

Terminal.png node:
tar xzvf /grid5000/images/KVM/kvm-context.tgz

Adapt the network configuration in the contextualization script

  • The contextualization script will apply your network settings.
  • The command g5k-subnets will give you all the needed network information related to your subnet reservation.
Terminal.png node:
g5k-subnets -a
  • Choose an IP and a mac address in your range:
Terminal.png node:
g5k-subnets -im
10.172.0.1      00:16:3E:AC:00:01
10.172.0.2      00:16:3E:AC:00:02
10.172.0.3      00:16:3E:AC:00:03
10.172.0.4      00:16:3E:AC:00:04
10.172.0.5      00:16:3E:AC:00:05
10.172.0.6      00:16:3E:AC:00:06
10.172.0.7      00:16:3E:AC:00:07
10.172.0.8      00:16:3E:AC:00:08
10.172.0.9      00:16:3E:AC:00:09
10.172.0.10     00:16:3E:AC:00:0A
...
  • Following the information displayed, you should adapt the file ./kvm-context/common/network.

This file is used by the script ./kvm-context/distributions/debian/00_network in order to configure the network interface for your VM.

Here is an example:

IPADDR=10.172.0.1
MACADDR=00:16:3e:ac:00:01
GATEWAY=10.175.255.254
NETWORK=10.172.0.0
BROADCAST=10.175.255.255
NETMASK=255.252.0.0
NAMESERVER=172.16.191.101
DOMAIN=luxembourg.grid5000.fr
SEARCH=luxembourg.grid5000.fr

Generate the iso file

Once you have prepared the content of the iso file for the contextualization, you can generate it in /tmp on the node.

Terminal.png node:
genisoimage -r -o $ISOFILE kvm-context/

The file (replace $ISOFILE by a file name) is ready to be attached to a VM, the script included in the iso will be executed and will configure the first network interface at boot time.

Multi-site experiment

In this part, to illustrate what can be done using Virtual machines on the production environment, we will start two virtual machines on two sites, and make them communicate using the virtualization network.

Reservation

Open 2 terminals, and ssh to the frontends of 2 sites, in this example, it will be the frontend of Luxembourg, and the frontend of Nancy. Then, reserve two virtualization-capable nodes and two subnets on two different sites.

Terminal.png frontend:
oarsub -I -l "slash_22=1+{virtual!='none'}/nodes=1"
Terminal.png frontend:
oarsub -I -l "slash_22=1+{virtual!='none'}/nodes=1"

Contextualization

In this part, we will create a contextualization iso, as seen in the previous tutorial KVM.

Choose an IP for each VM, in the output of g5k-subnets -im. Note that g5k-subnets returns completely different information on each site. In the following, we assume that you chose 10.144.8.1 in Nancy, and 10.172.0.1 in Luxembourg.

Terminal.png node(nancy):
g5k-subnets -im | head
Terminal.png node(luxembourg):
g5k-subnets -im | head

Then, generate your contextualization iso file:

Terminal.png node(nancy):
/grid5000/images/KVM/g5k-vm --ip 10.144.8.1 --iso /tmp/kvm-context-10.144.8.1.iso
Terminal.png node(luxembourg):
/grid5000/images/KVM/g5k-vm --ip 10.172.0.1 --iso /tmp/kvm-context-10.172.0.1.iso

Instantiate your VMs

Create the tap interfaces

Terminal.png node(nancy):
sudo create_tap
Terminal.png node(luxembourg):
sudo create_tap

Copy a standard virtual machine image

Copy the default virtual machine image from /grid5000/images/KVM/wheezy-x64-base.qcow2 to /tmp

Terminal.png node(nancy):
cp /grid5000/images/KVM/wheezy-x64-base.qcow2 /tmp/
Terminal.png node(luxembourg):
cp /grid5000/images/KVM/wheezy-x64-base.qcow2 /tmp/

Create the domain.xml file

The domain.xml file contains the description of your virtual machine. You must adapt it, in order to use a mac address provided by g5k-subnets -im. The virtual machine will get the IP associated to its mac address.

<domain type='kvm'>
 <name>wheezy</name>
 <memory>362144</memory>
 <vcpu>1</vcpu>
 <os>
   <type arch="x86_64">hvm</type>
 </os>
 <clock sync="localtime"/>
 <on_poweroff>destroy</on_poweroff>
 <on_reboot>restart</on_reboot>
 <on_crash>destroy</on_crash>
 <devices>
   <emulator>/usr/bin/kvm</emulator>
   <disk type='file' device='disk'>
     <driver type='qcow2'/>
     <source file='/tmp/wheezy-x64-base.qcow2'/>
     <target dev='vda' bus='virtio'/>
     <shareable/>
   </disk>
   <disk type='file' device='cdrom'>
     <source file='/tmp/kvm-context-10.144.8.1.iso'/>
     <target dev='vdb' bus='virtio'/>
     <readonly/>
   </disk>
   <interface type='ethernet'>
     <target dev='tap0'/>
     <script path='no'/>
     <model type='virtio'/>
     <mac address='00:16:3e:90:08:01'/>
   </interface>
   <serial type='pty'>
     <source path='/dev/ttyS0'/>
     <target port='0'/>
   </serial>
   <console type='pty'>
     <source path='/dev/ttyS0'/>
     <target port='0'/>
   </console>
 </devices>
</domain>
<domain type='kvm'>
 <name>wheezy</name>
 <memory>362144</memory>
 <vcpu>1</vcpu>
 <os>
   <type arch="x86_64">hvm</type>
 </os>
 <clock sync="localtime"/>
 <on_poweroff>destroy</on_poweroff>
 <on_reboot>restart</on_reboot>
 <on_crash>destroy</on_crash>
 <devices>
   <emulator>/usr/bin/kvm</emulator>
   <disk type='file' device='disk'>
     <driver type='qcow2'/>
     <source file='/tmp/wheezy-x64-base.qcow2'/>
     <target dev='vda' bus='virtio'/>
     <shareable/>
   </disk>
   <disk type='file' device='cdrom'>
     <source file='/tmp/kvm-context-10.172.0.1.iso'/>
     <target dev='vdb' bus='virtio'/>
     <readonly/>
   </disk>
   <interface type='ethernet'>
     <target dev='tap0'/>
     <script path='no'/>
     <model type='virtio'/>
     <mac address='00:16:3e:ac:00:01'/>
   </interface>
   <serial type='pty'>
     <source path='/dev/ttyS0'/>
     <target port='0'/>
   </serial>
   <console type='pty'>
     <source path='/dev/ttyS0'/>
     <target port='0'/>
   </console>
 </devices>
</domain>

Launch the two VMs

Terminal.png node(nancy):
virsh create domain.xml
Terminal.png node(luxembourg):
virsh create domain.xml

Enjoy !

SSH in your VMs

Terminal.png node(nancy):
ssh root@10.144.8.1
Terminal.png node(luxembourg):
ssh root@10.172.0.1
Note.png Note

The password for the root account is grid5000

Install and run iperf

Finally, we will install iperf and measure the bandwidth between the two VMs:

  • install iperf with apt-get ;
  • then, run iperf in server mode (-s parameter) on one node, and in client mode (-c parameter) on the other.
Terminal.png vm(nancy):
apt-get install iperf
Terminal.png vm(nancy):
iperf -s
root@vm-1:~# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 10.144.8.1 port 5001 connected with 10.172.0.1 port 52389
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec  1.09 GBytes    938 Mbits/sec
Terminal.png vm(luxembourg):
apt-get install iperf
Terminal.png vm(luxembourg):
iperf -c 10.144.8.1
root@vm-1:~# iperf -c 10.144.8.1
------------------------------------------------------------
Client connecting to 10.144.8.1, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 10.172.0.1 port 52389 connected with 10.144.8.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  1.09 GBytes    938 Mbits/sec