LXCR-8047 Created a copy of the NFV Access Guide and Release Notes for intel

30 files changed, 6056 insertions, 141 deletions

diff --git a/doc/book-enea-nfv-access-guide-intel/doc/benchmarks.xml b/doc/book-enea-nfv-access-guide-intel/doc/benchmarks.xml
new file mode 100644
index 0000000..3279601
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/benchmarks.xml
@@ -0,0 +1,1637 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="benchmarks">
+  <title>Benchmarks</title>
+
+  <section id="hw-setup">
+    <title>Hardware Setup</title>
+
+    <para>The following table describes all the needed prequisites for an apt
+    hardware setup:</para>
+
+    <table>
+      <title>Hardware Setup</title>
+
+      <tgroup cols="2">
+        <colspec align="left" />
+
+        <thead>
+          <row>
+            <entry align="center">Item</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry align="left">Server Platform</entry>
+
+            <entry align="left">Supermicro X10SDV-4C-TLN2F
+            http://www.supermicro.com/products/motherboard/xeon/d/X10SDV-4C-TLN2F.cfm</entry>
+          </row>
+
+          <row>
+            <entry align="left">ARCH</entry>
+
+            <entry>x86-64</entry>
+          </row>
+
+          <row>
+            <entry align="left">Processor</entry>
+
+            <entry>1 x Intel Xeon D-1521 (Broadwell), 4 cores, 8
+            hyper-threaded cores per processor</entry>
+          </row>
+
+          <row>
+            <entry align="left">CPU freq</entry>
+
+            <entry>2.40 GHz</entry>
+          </row>
+
+          <row>
+            <entry align="left">RAM</entry>
+
+            <entry>16GB</entry>
+          </row>
+
+          <row>
+            <entry align="left">Network</entry>
+
+            <entry>Dual integrated 10G ports</entry>
+          </row>
+
+          <row>
+            <entry align="left">Storage</entry>
+
+            <entry>Samsung 850 Pro 128GB SSD</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+
+    <para>Generic tests configuration:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>All tests use one port, one core and one Rx/TX queue for fast
+        path traffic.</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="bios">
+    <title>BIOS Settings</title>
+
+    <para>The table below details the BIOS settings for which the default
+    values were changed when doing performance measurements.</para>
+
+    <table>
+      <title>BIOS Settings</title>
+
+      <tgroup cols="4">
+        <colspec align="left" />
+
+        <thead>
+          <row>
+            <entry align="center">Menu Path</entry>
+
+            <entry align="center">Setting Name</entry>
+
+            <entry align="center">Enea NFV Access value</entry>
+
+            <entry align="center">BIOS Default value</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry align="left">CPU Configuration</entry>
+
+            <entry align="left">Direct Cache Access (DCA)</entry>
+
+            <entry>Enable</entry>
+
+            <entry>Auto</entry>
+          </row>
+
+          <row>
+            <entry>CPU Configuration / Advanced Power Management
+            Configuration</entry>
+
+            <entry align="left">EIST (P-States)</entry>
+
+            <entry>Disable</entry>
+
+            <entry>Enable</entry>
+          </row>
+
+          <row>
+            <entry>CPU Configuration / Advanced Power Management Configuration
+            / CPU C State Control</entry>
+
+            <entry align="left">CPU C State</entry>
+
+            <entry>Disable</entry>
+
+            <entry>Enable</entry>
+          </row>
+
+          <row>
+            <entry>CPU Configuration / Advanced Power Management Configuration
+            / CPU Advanced PM Turning / Energy Perf BIAS</entry>
+
+            <entry align="left">Energy Performance Tuning</entry>
+
+            <entry>Disable</entry>
+
+            <entry>Enable</entry>
+          </row>
+
+          <row>
+            <entry>CPU Configuration / Advanced Power Management Configuration
+            / CPU Advanced PM Turning / Energy Perf BIAS</entry>
+
+            <entry align="left">Energy Performance BIAS Setting</entry>
+
+            <entry>Performance</entry>
+
+            <entry>Balanced Performance</entry>
+          </row>
+
+          <row>
+            <entry>CPU Configuration / Advanced Power Management Configuration
+            / CPU Advanced PM Turning / Energy Perf BIAS</entry>
+
+            <entry align="left">Power/Performance Switch</entry>
+
+            <entry>Disable</entry>
+
+            <entry>Enable</entry>
+          </row>
+
+          <row>
+            <entry>CPU Configuration / Advanced Power Management Configuration
+            / CPU Advanced PM Turning / Program PowerCTL _MSR</entry>
+
+            <entry align="left">Energy Efficient Turbo</entry>
+
+            <entry>Disable</entry>
+
+            <entry>Enable</entry>
+          </row>
+
+          <row>
+            <entry>Chipset Configuration / North Bridge / IIO
+            Configuration</entry>
+
+            <entry align="left">EV DFX Features</entry>
+
+            <entry>Enable</entry>
+
+            <entry>Disable</entry>
+          </row>
+
+          <row>
+            <entry>Chipset Configuration / North Bridge / Memory
+            Configuration</entry>
+
+            <entry align="left">Enforce POR</entry>
+
+            <entry>Disable</entry>
+
+            <entry>Enable</entry>
+          </row>
+
+          <row>
+            <entry>Chipset Configuration / North Bridge / Memory
+            Configuration</entry>
+
+            <entry align="left">Memory Frequency</entry>
+
+            <entry>2400</entry>
+
+            <entry>Auto</entry>
+          </row>
+
+          <row>
+            <entry>Chipset Configuration / North Bridge / Memory
+            Configuration</entry>
+
+            <entry align="left">DRAM RAPL Baseline</entry>
+
+            <entry>Disable</entry>
+
+            <entry>DRAM RAPL Mode 1</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+  </section>
+
+  <section id="use-cases">
+    <title>Use Cases</title>
+
+    <section id="docker-benchmarks">
+      <title>Docker related benchmarks</title>
+
+      <section>
+        <title>Forward traffic in Docker</title>
+
+        <para>Benchmarking traffic forwarding using testpmd in a Docker
+        container.</para>
+
+        <para>Pktgen is used to generate UDP traffic that will reach testpmd,
+        running in a Docker image. It will then be forwarded back to source on
+        the return trip (<emphasis role="bold">Forwarding</emphasis>).</para>
+
+        <para>This test measures:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>pktgen TX, RX in packets per second (pps) and Mbps</para>
+          </listitem>
+
+          <listitem>
+            <para>testpmd TX, RX in packets per second (pps)</para>
+          </listitem>
+
+          <listitem>
+            <para>divide testpmd RX / pktgen TX in pps to obtain throughput in
+            percentages (%)</para>
+          </listitem>
+        </itemizedlist>
+
+        <section id="usecase-one">
+          <title>Test Setup for Target 1</title>
+
+          <para>Start by following the steps below:</para>
+
+          <para>SSD boot using the following <literal>grub.cfg</literal>
+          entry: <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt /
+intel_iommu=on  hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting></para>
+
+          <para>Kill unnecessary services:<programlisting>killall ovsdb-server ovs-vswitchd
+rm -rf /etc/openvswitch/*
+mkdir -p /var/run/openvswitch</programlisting>Mount hugepages and configure
+          DPDK:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:03:00.0</programlisting>Run
+          pktgen:<programlisting>cd /usr/share/apps/pktgen/
+./pktgen -c 0xF -n 1 -- -P -m "[3:2].0"</programlisting>In the pktgen console
+          run:<programlisting>str</programlisting>To change framesize for
+          pktgen, from [64, 128, 256, 512]:<programlisting>set 0 size &amp;lt;number&amp;gt;</programlisting></para>
+        </section>
+
+        <section id="usecase-two">
+          <title>Test Setup for Target 2</title>
+
+          <para>Start by following the steps below:</para>
+
+          <para>SSD boot using the following <literal>grub.cfg</literal>
+          entry:</para>
+
+          <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt /
+intel_iommu=on  hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting>
+
+          <para>It is expected to have Docker/guest image on target. Configure
+          the OVS bridge:<programlisting># OVS old config clean-up
+killall ovsdb-server ovs-vswitchd
+rm -rf /etc/openvswitch/*
+mkdir -p /var/run/openvswitch
+
+# Mount hugepages and bind interfaces to dpdk
+mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:03:00.0
+
+# configure openvswitch with DPDK
+export DB_SOCK=/var/run/openvswitch/db.sock
+ovsdb-tool create /etc/openvswitch/conf.db /
+/usr/share/openvswitch/vswitch.ovsschema
+ovsdb-server --remote=punix:$DB_SOCK /
+--remote=db:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach
+ovs-vsctl --no-wait init
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x10
+ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0xc
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem=2048
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
+ovs-vswitchd unix:$DB_SOCK --pidfile --detach /
+--log-file=/var/log/openvswitch/ovs-vswitchd.log
+
+ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=netdev
+ovs-vsctl add-port ovsbr0 vhost-user1 /
+-- set Interface vhost-user1 type=dpdkvhostuser ofport_request=1
+ovs-vsctl add-port ovsbr0 dpdk0 -- set Interface /
+dpdk0 type=dpdk options:dpdk-devargs=0000:03:00.0 ofport_request=2
+
+# configure static flows
+ovs-ofctl del-flows ovsbr0
+ovs-ofctl add-flow ovsbr0 in_port=1,action=output:2
+ovs-ofctl add-flow ovsbr0 in_port=2,action=output:1</programlisting>Import a
+          Docker container:<programlisting>docker import enea-nfv-access-guest-qemux86-64.tar.gz el7_guest</programlisting>Start
+          the Docker container:<programlisting>docker run -it --rm -v /var/run/openvswitch/:/var/run/openvswitch/ /
+-v /mnt/huge:/mnt/huge el7_guest /bin/bash</programlisting>Start the testpmd
+          application in Docker:<programlisting>testpmd -c 0x30 -n 2 --file-prefix prog1  --socket-mem 512 --no-pci /
+--vdev=virtio_user0,path=/var/run/openvswitch/vhost-user1 /
+-d /usr/lib/librte_pmd_virtio.so.1.1  -- --burst 64 --disable-hw-vlan /
+--disable-rss  -i --portmask=0x1 --coremask=0x20  --nb-cores=1 /
+--rxq=1 --txq=1 --txd=512 --rxd=512 --txqflags=0xf00 --port-topology=chained</programlisting>To
+          start traffic <emphasis role="bold">forwarding</emphasis>, run the
+          following command in testpmd CLI:<programlisting>start</programlisting>To
+          start traffic but in <emphasis role="bold">termination</emphasis>
+          mode (no traffic sent on TX), run following command in testpmd
+          CLI:<programlisting>set fwd rxonly
+start</programlisting><table>
+              <title>Results in forwarding mode</title>
+
+              <tgroup cols="8">
+                <tbody>
+                  <row>
+                    <entry align="center"><emphasis
+                    role="bold">Bytes</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen MBits/s
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen pps
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen MBits/s
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">testpmd pps
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">testpmd pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">throughput
+                    (%)</emphasis></entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">64</emphasis></entry>
+
+                    <entry>14877658</entry>
+
+                    <entry>9997</entry>
+
+                    <entry>7832352</entry>
+
+                    <entry>5264</entry>
+
+                    <entry>7831250</entry>
+
+                    <entry>7831250</entry>
+
+                    <entry>52,65%</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">128</emphasis></entry>
+
+                    <entry>8441305</entry>
+
+                    <entry>9994</entry>
+
+                    <entry>7533893</entry>
+
+                    <entry>8922</entry>
+
+                    <entry>7535127</entry>
+
+                    <entry>7682007</entry>
+
+                    <entry>89,27%</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">256</emphasis></entry>
+
+                    <entry>4528831</entry>
+
+                    <entry>9999</entry>
+
+                    <entry>4528845</entry>
+
+                    <entry>9999</entry>
+
+                    <entry>4528738</entry>
+
+                    <entry>4528738</entry>
+
+                    <entry>100%</entry>
+                  </row>
+                </tbody>
+              </tgroup>
+            </table><table>
+              <title>Results in termination mode</title>
+
+              <tgroup cols="4">
+                <tbody>
+                  <row>
+                    <entry align="center"><emphasis
+                    role="bold">Bytes</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">testpmd pps
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">throughput
+                    (%)</emphasis></entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">64</emphasis></entry>
+
+                    <entry>14877775</entry>
+
+                    <entry>8060974</entry>
+
+                    <entry>54,1%</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">128</emphasis></entry>
+
+                    <entry>8441403</entry>
+
+                    <entry>8023555</entry>
+
+                    <entry>95,0%</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">256</emphasis></entry>
+
+                    <entry>4528864</entry>
+
+                    <entry>4528840</entry>
+
+                    <entry>99,9%</entry>
+                  </row>
+                </tbody>
+              </tgroup>
+            </table></para>
+        </section>
+      </section>
+
+      <section id="usecase-three-four">
+        <title>Forward traffic from Docker to another Docker on the same
+        host</title>
+
+        <para>Benchmark a combo test using testpmd running in two Docker
+        instances, one which Forwards traffic to the second one, which
+        Terminates it.</para>
+
+        <para>Packets are generated with pktgen and TX-d to the first testpmd,
+        which will RX and Forward them to the second testpmd, which will RX
+        and terminate them.</para>
+
+        <para>Measurements are made in:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>pktgen TX in pps and Mbits/s</para>
+          </listitem>
+
+          <listitem>
+            <para>testpmd TX and RX pps in Docker1</para>
+          </listitem>
+
+          <listitem>
+            <para>testpmd RX pps in Docker2</para>
+          </listitem>
+        </itemizedlist>
+
+        <para>Throughput found as a percent, by dividing Docker2 <emphasis
+        role="bold">testpmd RX pps</emphasis> by <emphasis role="bold">pktgen
+        TX pps</emphasis>.</para>
+
+        <section id="target-one-usecase-three">
+          <title>Test Setup for Target 1</title>
+
+          <para>Start by following the steps below:</para>
+
+          <para>SSD boot using the following <literal>grub.cfg</literal>
+          entry:</para>
+
+          <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt /
+intel_iommu=on  hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting>
+
+          <para>Configure DPDK:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:03:00.0</programlisting>Run
+          pktgen:<programlisting>cd /usr/share/apps/pktgen/
+./pktgen -c 0xF -n 1 -- -P -m "[3:2].0"</programlisting>Choose one of the
+          values from [64, 128, 256, 512] to change the packet
+          size:<programlisting>set 0 size &lt;number&gt;</programlisting></para>
+        </section>
+
+        <section id="target-two-usecase-four">
+          <title>Test Setup for Target 2</title>
+
+          <para>Start by following the steps below:</para>
+
+          <para>SSD boot using the following <literal>grub.cfg</literal>
+          entry:</para>
+
+          <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 /
+iommu=pt intel_iommu=on  hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting>
+
+          <para><programlisting>killall ovsdb-server ovs-vswitchd
+rm -rf /etc/openvswitch/*
+mkdir -p /var/run/openvswitch</programlisting>Configure DPDK:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:03:00.0</programlisting>Configure the OVS
+          bridge:<programlisting>export DB_SOCK=/var/run/openvswitch/db.sock
+ovsdb-tool create /etc/openvswitch/conf.db /
+/usr/share/openvswitch/vswitch.ovsschema
+ovsdb-server --remote=punix:$DB_SOCK /
+--remote=db:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach
+ovs-vsctl --no-wait init
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x10
+ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0xcc
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem=2048
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
+ovs-vswitchd unix:$DB_SOCK --pidfile --detach /
+--log-file=/var/log/openvswitch/ovs-vswitchd.log
+ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=netdev
+ovs-vsctl add-port ovsbr0 vhost-user1 -- set Interface /
+vhost-user1 type=dpdkvhostuser ofport_request=1
+ovs-vsctl add-port ovsbr0 vhost-user2 -- set Interface /
+vhost-user2 type=dpdkvhostuser ofport_request=2
+ovs-vsctl add-port ovsbr0 dpdk0 -- set Interface dpdk0 /
+type=dpdk options:dpdk-devargs=0000:03:00.0 ofport_request=3
+ovs-ofctl del-flows ovsbr0
+ovs-ofctl add-flow ovsbr0 in_port=3,action=output:2
+ovs-ofctl add-flow ovsbr0 in_port=2,action=output:1</programlisting>Import a
+          Docker container:<programlisting>docker import enea-nfv-access-guest-qemux86-64.tar.gz el7_guest</programlisting>Start
+          the first Docker:<programlisting>docker run -it --rm --cpuset-cpus=4,5 /
+-v /var/run/openvswitch/:/var/run/openvswitch/ /
+-v /mnt/huge:/mnt/huge el7_guest /bin/bash</programlisting>Start the testpmd
+          application in Docker1:<programlisting>testpmd -c 0x30 -n 2 --file-prefix prog1  --socket-mem 512 --no-pci /
+--vdev=virtio_user0,path=/var/run/openvswitch/vhost-user1 /
+-d /usr/lib/librte_pmd_virtio.so.1.1 -- --burst 64 --disable-hw-vlan /
+--disable-rss  -i --portmask=0x1 --coremask=0x20  --nb-cores=1 /
+--rxq=1 --txq=1 --txd=512 --rxd=512 --txqflags=0xf00 --port-topology=chained</programlisting>Configure
+          it in termination mode:<programlisting>set fwd rxonly</programlisting>Run
+          the testpmd application:<programlisting>start</programlisting>Open a
+          new console to the host and start the second Docker
+          instance:<programlisting>docker run -it --rm --cpuset-cpus=0,1 -v /var/run/openvswitch/:/var/run/openvswitch/ /
+-v /mnt/huge:/mnt/huge el7_guest /bin/bash</programlisting>In the second
+          container start testpmd:<programlisting>testpmd -c 0x0F --file-prefix prog2 --socket-mem 512 --no-pci /
+--vdev=virtio_user0,path=/var/run/openvswitch/vhost-user2 /
+-d /usr/lib/librte_pmd_virtio.so.1.1 -- -i --disable-hw-vlan</programlisting>Run
+          the TestPmd application in the second Docker:<programlisting>testpmd -c 0x3 -n 2 --file-prefix prog2  --socket-mem 512 --no-pci /
+--vdev=virtio_user0,path=/var/run/openvswitch/vhost-user2 /
+-d /usr/lib/librte_pmd_virtio.so.1.1 -- --burst 64 --disable-hw-vlan /
+--disable-rss  -i --portmask=0x1 --coremask=0x2  --nb-cores=1 --rxq=1 /
+--txq=1 --txd=512 --rxd=512 --txqflags=0xf00 --port-topology=chained</programlisting>In
+          the testpmd shell, run:<programlisting>start</programlisting>Start
+          pktgen traffic by running the following command in pktgen
+          CLI:<programlisting>start 0</programlisting>To record traffic
+          results:<programlisting>show port stats 0</programlisting>This
+          should be used in testpmd applications.</para>
+
+          <table>
+            <title>Results</title>
+
+            <tgroup cols="5">
+              <tbody>
+                <row>
+                  <entry align="center"><emphasis
+                  role="bold">Bytes</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">Target 1 -
+                  pktgen pps TX</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">Target 2 -
+                  (forwarding) testpmd pps RX</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">Target 2 -
+                  (forwarding) testpmd pps TX</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">Target 2 -
+                  (termination) testpmd pps RX</emphasis></entry>
+                </row>
+
+                <row>
+                  <entry role="bold"><emphasis
+                  role="bold">64</emphasis></entry>
+
+                  <entry>14877713</entry>
+
+                  <entry>5031270</entry>
+
+                  <entry>5031214</entry>
+
+                  <entry>5031346</entry>
+                </row>
+
+                <row>
+                  <entry><emphasis role="bold">128</emphasis></entry>
+
+                  <entry>8441271</entry>
+
+                  <entry>4670165</entry>
+
+                  <entry>4670165</entry>
+
+                  <entry>4670261</entry>
+                </row>
+
+                <row>
+                  <entry role="bold"><emphasis
+                  role="bold">256</emphasis></entry>
+
+                  <entry>4528844</entry>
+
+                  <entry>4490268</entry>
+
+                  <entry>4490268</entry>
+
+                  <entry>4490234</entry>
+                </row>
+
+                <row>
+                  <entry><emphasis role="bold">512</emphasis></entry>
+
+                  <entry>2349458</entry>
+
+                  <entry>2349553</entry>
+
+                  <entry>2349553</entry>
+
+                  <entry>2349545</entry>
+                </row>
+              </tbody>
+            </tgroup>
+          </table>
+        </section>
+      </section>
+
+      <section id="pxe-config-docker">
+        <title>SR-IOV in in Docker</title>
+
+        <para>PCI passthrough tests using pktgen and testpmd in Docker.</para>
+
+        <para>pktgen[DPDK]Docker - PHY - Docker[DPDK] testpmd</para>
+
+        <para>Measurements:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>RX packets per second in testpmd (with testpmd configured in
+            rxonly mode).</para>
+          </listitem>
+        </itemizedlist>
+
+        <section id="target-setup">
+          <title>Test Setup</title>
+
+          <para>Boot Enea NFV Access from SSD:<programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable clocksource=tsc /
+tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 processor.max_cstate=0 /
+mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt intel_iommu=on hugepagesz=1GB /
+hugepages=8 default_hugepagesz=1GB hugepagesz=2M hugepages=2048 /
+vfio_iommu_type1.allow_unsafe_interrupts=1l</programlisting>Allow unsafe
+          interrupts:<programlisting>echo 1 &gt; /sys/module/vfio_iommu_type1/parameters/allow_unsafe_interrupts</programlisting>Configure
+          DPDK:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+dpdk-devbind.py --bind=ixgbe 0000:03:00.0
+ifconfig eno3 192.168.1.2
+echo 2 &gt; /sys/class/net/eno3/device/sriov_numvfs
+modprobe vfio-pci
+dpdk-devbind.py --bind=vfio-pci 0000:03:10.0
+dpdk-devbind.py --bind=vfio-pci 0000:03:10.2</programlisting>Start two docker
+          containers:<programlisting>docker run --privileged -it --rm -v /mnt/huge:/mnt/huge/ /
+--device /dev/vfio/vfio el7_guest /bin/bash
+docker run --privileged -it --rm -v /mnt/huge:/mnt/huge/ /
+--device /dev/vfio/vfio el7_guest /bin/bash</programlisting>In the first
+          container start pktgen:<programlisting>cd /usr/share/apps/pktgen/
+./pktgen -c 0x1f -w 0000:03:10.0 -n 1 --file-prefix pg1 /
+--socket-mem 1024 -- -P -m "[3:4].0"</programlisting>In the pktgen prompt set
+          the destination MAC address:<programlisting>set mac 0 XX:XX:XX:XX:XX:XX
+str</programlisting>In the second container start testpmd:<programlisting>testpmd -c 0x7 -n 1 -w 0000:03:10.2 -- -i --portmask=0x1 /
+--txd=256 --rxd=256 --port-topology=chained</programlisting>In the testpmd
+          prompt set <emphasis role="bold">forwarding</emphasis>
+          rxonly:<programlisting>set fwd rxonly
+start</programlisting><table>
+              <title>Results</title>
+
+              <tgroup cols="5">
+                <tbody>
+                  <row>
+                    <entry align="center"><emphasis
+                    role="bold">Bytes</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">testpmd pps
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen MBits/s
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">throughput
+                    (%)</emphasis></entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">64</emphasis></entry>
+
+                    <entry>14204211</entry>
+
+                    <entry>14204561</entry>
+
+                    <entry>9545</entry>
+
+                    <entry>100</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">128</emphasis></entry>
+
+                    <entry>8440340</entry>
+
+                    <entry>8440201</entry>
+
+                    <entry>9993</entry>
+
+                    <entry>99.9</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">256</emphasis></entry>
+
+                    <entry>4533828</entry>
+
+                    <entry>4533891</entry>
+
+                    <entry>10010</entry>
+
+                    <entry>100</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">512</emphasis></entry>
+
+                    <entry>2349886</entry>
+
+                    <entry>2349715</entry>
+
+                    <entry>10000</entry>
+
+                    <entry>99.9</entry>
+                  </row>
+                </tbody>
+              </tgroup>
+            </table></para>
+        </section>
+      </section>
+    </section>
+
+    <section id="vm-benchmarks">
+      <title>VM related benchmarks</title>
+
+      <section id="usecase-four">
+        <title>Forward/termination traffic in one VM</title>
+
+        <para>Benchmarking traffic (UDP) forwarding and termination using
+        testpmd in a virtual machine.</para>
+
+        <para>The Pktgen application is used to generate traffic that will
+        reach testpmd running on a virtual machine, and be forwarded back to
+        source on the return trip. With the same setup a second measurement
+        will be done with traffic termination in the virtual machine.</para>
+
+        <para>This test case measures:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>pktgen TX, RX in packets per second (pps) and Mbps</para>
+          </listitem>
+
+          <listitem>
+            <para>testpmd TX, RX in packets per second (pps)</para>
+          </listitem>
+
+          <listitem>
+            <para>divide <emphasis role="bold">testpmd RX</emphasis> by
+            <emphasis role="bold">pktgen TX</emphasis> in pps to obtain the
+            throughput in percentages (%)</para>
+          </listitem>
+        </itemizedlist>
+
+        <section id="targetone-usecasefour">
+          <title>Test Setup for Target 1</title>
+
+          <para>Start with the steps below:</para>
+
+          <para>SSD boot using the following <literal>grub.cfg
+          </literal>entry: <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt /
+intel_iommu=on hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting></para>
+
+          <para>Kill unnecessary services: <programlisting>killall ovsdb-server ovs-vswitchd
+rm -rf /etc/openvswitch/*
+mkdir -p /var/run/openvswitch</programlisting>Configure DPDK:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:03:00.0</programlisting>Run
+          pktgen:<programlisting>cd /usr/share/apps/pktgen/
+./pktgen -c 0x7 -n 4 --proc-type auto --socket-mem 256 /
+-w 0000:03:00.0 -- -P -m "[1:2].0"</programlisting>Set pktgen frame size to
+          use from [64, 128, 256, 512]:<programlisting>set 0 size 64</programlisting></para>
+        </section>
+
+        <section id="targettwo-usecasefive">
+          <title>Test Setup for Target 2</title>
+
+          <para>Start by following the steps below:</para>
+
+          <para>SSD boot using the following <literal>grub.cfg</literal>
+          entry: <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt /
+intel_iommu=on  hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting>Kill
+          unnecessary services: <programlisting>killall ovsdb-server ovs-vswitchd
+rm -rf /etc/openvswitch/*
+mkdir -p /var/run/openvswitch</programlisting>Configure DPDK:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:03:00.0</programlisting>Configure
+          OVS:<programlisting>export DB_SOCK=/var/run/openvswitch/db.sock
+ovsdb-tool create /etc/openvswitch/conf.db /
+/usr/share/openvswitch/vswitch.ovsschema
+ovsdb-server --remote=punix:$DB_SOCK /
+--remote=db:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach
+ovs-vsctl --no-wait init
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x10
+ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0xc
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem=2048
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
+ovs-vswitchd unix:$DB_SOCK --pidfile --detach /
+--log-file=/var/log/openvswitch/ovs-vswitchd.log
+
+ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=netdev
+ovs-vsctl add-port ovsbr0 vhost-user1 /
+-- set Interface vhost-user1 type=dpdkvhostuser -- set Interface /
+vhost-user1 ofport_request=2
+ovs-vsctl add-port ovsbr0 dpdk0 -- set Interface dpdk0 /
+type=dpdk options:dpdk-devargs=0000:03:00.0 /
+-- set Interface dpdk0 ofport_request=1
+chmod 777 /var/run/openvswitch/vhost-user1
+
+ovs-ofctl del-flows ovsbr0
+ovs-ofctl add-flow ovsbr0 in_port=1,action=output:2
+ovs-ofctl add-flow ovsbr0 in_port=2,action=output:1</programlisting>Launch
+          QEMU:<programlisting>taskset -c 0,1 qemu-system-x86_64 -cpu host,+invtsc,migratable=no /
+-M q35 -smp cores=2,sockets=1 -vcpu 0,affinity=0 -vcpu 1,affinity=1 /
+-enable-kvm -nographic -realtime mlock=on -kernel /mnt/qemu/bzImage /
+-drive file=/mnt/qemu/enea-nfv-access-guest-qemux86-64.ext4,/
+if=virtio,format=raw -m 4096 -object memory-backend-file,id=mem,/
+size=4096M,mem-path=/mnt/huge,share=on -numa node,memdev=mem /
+-mem-prealloc -chardev socket,id=char0,path=/var/run/openvswitch/vhost-user1 /
+-netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce /
+-device virtio-net-pci,mac=52:54:00:00:00:01,netdev=mynet1,/
+mrg_rxbuf=on,rx_queue_size=1024,csum=off,gso=off,guest_tso4=off,/
+guest_tso6=off,guest_ecn=off -append 'root=/dev/vda console=ttyS0 /
+hugepagesz=2M hugepages=1024 isolcpus=1 nohz_full=1 rcu_nocbs=1 /
+irqaffinity=0 rcu_nocb_poll intel_pstate=disable intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0'</programlisting>Inside QEMU,
+          configure DPDK: <programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:00:02.0</programlisting>Inside QEMU, run
+          testpmd: <programlisting>testpmd -c 0x3 -n 2 -d librte_pmd_virtio.so.1.1  /
+-- --burst 64 --disable-hw-vlan --disable-rss  -i --portmask=0x1 /
+--coremask=0x2  --nb-cores=1 --rxq=1 --txq=1 --txd=512 --rxd=512 /
+--txqflags=0xf00 --port-topology=chained</programlisting>For the <emphasis
+          role="bold">Forwarding test</emphasis>, start testpmd
+          directly:<programlisting>start</programlisting>For the <emphasis
+          role="bold">Termination test</emphasis>, set testpmd to only
+          receive, then start it:<programlisting>set fwd rxonly
+start</programlisting>On target 1, you may start pktgen traffic
+          now:<programlisting>start 0</programlisting>On target 2, use this
+          command to refresh the testpmd display and note the highest
+          values:<programlisting>show port stats 0</programlisting>To stop
+          traffic from pktgen, in order to choose a different frame
+          size:<programlisting>stop 0</programlisting>To clear numbers in
+          testpmd:<programlisting>clear port stats
+show port stats 0</programlisting><table>
+              <title>Results in forwarding mode</title>
+
+              <tgroup cols="8">
+                <tbody>
+                  <row>
+                    <entry align="center"><emphasis
+                    role="bold">Bytes</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen pps
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">testpmd pps
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">testpmd pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen MBits/s
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen MBits/s
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">throughput
+                    (%)</emphasis></entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">64</emphasis></entry>
+
+                    <entry>7926325</entry>
+
+                    <entry>14877576</entry>
+
+                    <entry>7926515</entry>
+
+                    <entry>7926515</entry>
+
+                    <entry>5326</entry>
+
+                    <entry>9997</entry>
+
+                    <entry>53.2</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">128</emphasis></entry>
+
+                    <entry>7502802</entry>
+
+                    <entry>8441253</entry>
+
+                    <entry>7785983</entry>
+
+                    <entry>7494959</entry>
+
+                    <entry>8883</entry>
+
+                    <entry>9994</entry>
+
+                    <entry>88.8</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">256</emphasis></entry>
+
+                    <entry>4528631</entry>
+
+                    <entry>4528782</entry>
+
+                    <entry>4529515</entry>
+
+                    <entry>4529515</entry>
+
+                    <entry>9999</entry>
+
+                    <entry>9999</entry>
+
+                    <entry>99.9</entry>
+                  </row>
+                </tbody>
+              </tgroup>
+            </table><table>
+              <title>Results in termination mode</title>
+
+              <tgroup cols="5">
+                <tbody>
+                  <row>
+                    <entry align="center"><emphasis
+                    role="bold">Bytes</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">testpmd pps
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">pktgen MBits/s
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">throughput
+                    (%)</emphasis></entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">64</emphasis></entry>
+
+                    <entry>14877764</entry>
+
+                    <entry>8090855</entry>
+
+                    <entry>9997</entry>
+
+                    <entry>54.3</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">128</emphasis></entry>
+
+                    <entry>8441309</entry>
+
+                    <entry>8082971</entry>
+
+                    <entry>9994</entry>
+
+                    <entry>95.7</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">256</emphasis></entry>
+
+                    <entry>4528867</entry>
+
+                    <entry>4528780</entry>
+
+                    <entry>9999</entry>
+
+                    <entry>99.9</entry>
+                  </row>
+                </tbody>
+              </tgroup>
+            </table></para>
+        </section>
+      </section>
+
+      <section id="usecase-six">
+        <title>Forward traffic between two VMs</title>
+
+        <para>Benchmark a combo test using two virtual machines, the first
+        with traffic forwarding to the second, which terminates it.</para>
+
+        <para>Measurements are made in:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>pktgen TX in pps and Mbits/s</para>
+          </listitem>
+
+          <listitem>
+            <para>testpmd TX and RX pps in VM1</para>
+          </listitem>
+
+          <listitem>
+            <para>testpmd RX pps in VM2</para>
+          </listitem>
+
+          <listitem>
+            <para>throughput in percents, by dividing<emphasis role="bold">
+            VM2 testpmd RX pps</emphasis> by <emphasis role="bold">pktgen TX
+            pps</emphasis></para>
+          </listitem>
+        </itemizedlist>
+
+        <section id="targetone-usecase-five">
+          <title>Test Setup for Target 1</title>
+
+          <para>Start by doing the following:</para>
+
+          <para>SSD boot using the following <literal>grub.cfg</literal>
+          entry: <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt /
+intel_iommu=on  hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting>Kill
+          Services:<programlisting>killall ovsdb-server ovs-vswitchd
+rm -rf /etc/openvswitch/*
+mkdir -p /var/run/openvswitch</programlisting>Configure DPDK:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:03:00.0</programlisting>Run
+          pktgen:<programlisting>cd /usr/share/apps/pktgen/
+./pktgen -c 0x7 -n 4 --proc-type auto --socket-mem 256 /
+-w 0000:03:00.0 -- -P -m "[1:2].0"</programlisting>Set pktgen frame size to
+          use from [64, 128, 256, 512]:<programlisting>set 0 size 64</programlisting></para>
+        </section>
+
+        <section id="targettwo-usecase-six">
+          <title>Test Setup for Target 2</title>
+
+          <para>Start by doing the following:</para>
+
+          <para>SSD boot using the following <literal>grub.cfg</literal>
+          entry: <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt /
+intel_iommu=on  hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting>Kill
+          Services:<programlisting>killall ovsdb-server ovs-vswitchd
+rm -rf /etc/openvswitch/*
+mkdir -p /var/run/openvswitch</programlisting>Configure DPDK:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:03:00.0</programlisting>Configure
+          OVS:<programlisting>export DB_SOCK=/var/run/openvswitch/db.sock
+ovsdb-tool create /etc/openvswitch/conf.db /
+/usr/share/openvswitch/vswitch.ovsschema
+ovsdb-server --remote=punix:$DB_SOCK /
+--remote=db:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach
+ovs-vsctl --no-wait init
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x10
+ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0xc
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem=2048
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
+ovs-vswitchd unix:$DB_SOCK --pidfile /
+--detach --log-file=/var/log/openvswitch/ovs-vswitchd.log
+
+
+ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=netdev
+ovs-vsctl add-port ovsbr0 dpdk0 /
+-- set Interface dpdk0 type=dpdk options:dpdk-devargs=0000:03:00.0 ofport_request=1
+ovs-vsctl add-port ovsbr0 vhost-user1 /
+-- set Interface vhost-user1 type=dpdkvhostuser ofport_request=2
+ovs-vsctl add-port ovsbr0 vhost-user2 /
+-- set Interface vhost-user2 type=dpdkvhostuser ofport_request=3
+
+
+ovs-ofctl del-flows ovsbr0
+ovs-ofctl add-flow ovsbr0 in_port=1,action=output:2
+ovs-ofctl add-flow ovsbr0 in_port=2,action=output:3</programlisting>Launch
+          first QEMU instance, VM1:<programlisting>taskset -c 0,1 qemu-system-x86_64 -cpu host,+invtsc,migratable=no -M q35 /
+-smp cores=2,sockets=1 -vcpu 0,affinity=0 -vcpu 1,affinity=1 -enable-kvm /
+-nographic -realtime mlock=on -kernel /home/root/qemu/bzImage /
+-drive file=/home/root/qemu/enea-nfv-access-guest-qemux86-64.ext4,/
+if=virtio,format=raw -m 2048 -object memory-backend-file,id=mem,/
+size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem /
+-mem-prealloc -chardev socket,id=char0,path=/var/run/openvswitch/vhost-user1 /
+-netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce /
+-device virtio-net-pci,mac=52:54:00:00:00:01,netdev=mynet1,/
+mrg_rxbuf=on,rx_queue_size=1024,csum=off,gso=off,guest_tso4=off,/
+guest_tso6=off,guest_ecn=off -append 'root=/dev/vda console=ttyS0 /
+hugepagesz=2M hugepages=512 isolcpus=1 nohz_full=1 rcu_nocbs=1 /
+irqaffinity=0 rcu_nocb_poll intel_pstate=disable intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0'</programlisting>Connect to
+          Target 2 through a new SSH session and run a second QEMU instance
+          (to get its own console, separate from instance VM1). We shall call
+          this VM2:<programlisting>taskset -c 4,5 qemu-system-x86_64 -cpu host,+invtsc,migratable=no /
+-M q35 -smp cores=2,sockets=1 -vcpu 0,affinity=4 -vcpu 1,affinity=5 /
+-enable-kvm -nographic -realtime mlock=on -kernel /home/root/qemu2/bzImage /
+-drive file=/home/root/qemu2/enea-nfv-access-guest-qemux86-64.ext4,/
+if=virtio,format=raw -m 2048 -object memory-backend-file,id=mem,size=2048M,/
+mem-path=/mnt/huge,share=on -numa node,memdev=mem -mem-prealloc /
+-chardev socket,id=char1,path=/var/run/openvswitch/vhost-user2 /
+-netdev type=vhost-user,id=mynet1,chardev=char1,vhostforce /
+-device virtio-net-pci,mac=52:54:00:00:00:02,netdev=mynet1,/
+mrg_rxbuf=on,rx_queue_size=1024,csum=off,gso=off,guest_tso4=off,/
+guest_tso6=off,guest_ecn=off -append 'root=/dev/vda console=ttyS0 /
+hugepagesz=2M hugepages=512 isolcpus=1 nohz_full=1 rcu_nocbs=1 /
+irqaffinity=0 rcu_nocb_poll intel_pstate=disable intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0'</programlisting>Configure DPDK
+          inside VM1:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:00:02.0</programlisting>Run testpmd inside
+          VM1:<programlisting>testpmd -c 0x3 -n 2 -d librte_pmd_virtio.so.1.1  /
+-- --burst 64 --disable-hw-vlan --disable-rss  -i /
+--portmask=0x1 --coremask=0x2  --nb-cores=1 --rxq=1 /
+--txq=1 --txd=512 --rxd=512 --txqflags=0xf00 --port-topology=chained</programlisting>Start
+          testpmd inside VM1:<programlisting>start</programlisting>Configure
+          DPDK inside VM2:<programlisting>mkdir -p /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge
+modprobe igb_uio
+dpdk-devbind --bind=igb_uio 0000:00:02.0</programlisting>Run testpmd inside
+          VM2:<programlisting>testpmd -c 0x3 -n 2 -d librte_pmd_virtio.so.1.1  /
+-- --burst 64 --disable-hw-vlan --disable-rss -i --portmask=0x1 /
+--coremask=0x2  --nb-cores=1 --rxq=1 --txq=1 --txd=512 /
+--rxd=512 --txqflags=0xf00 --port-topology=chained</programlisting>Set VM2 for
+          termination and start testpmd:<programlisting>set fwd rxonly
+start</programlisting>On target 1, start pktgen traffic:<programlisting>start 0</programlisting>Use
+          this command to refresh testpmd display in VM1 and VM2 and note the
+          highest values:<programlisting>show port stats 0</programlisting>To
+          stop traffic from pktgen, in order to choose a different frame
+          size:<programlisting>stop 0</programlisting>To clear numbers in
+          testpmd:<programlisting>clear port stats
+show port stats 0</programlisting>For VM1, we record the stats relevant for
+          <emphasis role="bold">forwarding</emphasis>:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>RX, TX in pps</para>
+            </listitem>
+          </itemizedlist>
+
+          <para>Only Rx-pps and Tx-pps numbers are important here, they change
+          every time stats are displayed as long as there is traffic. Run the
+          command a few times and pick the best (maximum) values seen.</para>
+
+          <para>For VM2, we record the stats relevant for <emphasis
+          role="bold">termination</emphasis>:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>RX in pps (TX will be 0)</para>
+            </listitem>
+          </itemizedlist>
+
+          <para>For pktgen, we record only the TX side, because flow is
+          terminated, with no RX traffic reaching pktgen:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>TX in pps and Mbit/s</para>
+            </listitem>
+          </itemizedlist>
+
+          <table>
+            <title>Results in forwarding mode</title>
+
+            <tgroup cols="7">
+              <tbody>
+                <row>
+                  <entry align="center"><emphasis
+                  role="bold">Bytes</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">pktgen pps
+                  TX</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">VM1 testpmd pps
+                  RX</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">VM1 testpmd pps
+                  TX</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">VM2 testpmd pps
+                  RX</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">pktgen MBits/s
+                  TX</emphasis></entry>
+
+                  <entry align="center"><emphasis role="bold">throughput
+                  (%)</emphasis></entry>
+                </row>
+
+                <row>
+                  <entry role="bold"><emphasis
+                  role="bold">64</emphasis></entry>
+
+                  <entry>14877757</entry>
+
+                  <entry>7712835</entry>
+
+                  <entry>6024320</entry>
+
+                  <entry>6015525</entry>
+
+                  <entry>9997</entry>
+
+                  <entry>40.0</entry>
+                </row>
+
+                <row>
+                  <entry><emphasis role="bold">128</emphasis></entry>
+
+                  <entry>8441333</entry>
+
+                  <entry>7257432</entry>
+
+                  <entry>5717540</entry>
+
+                  <entry>5716752</entry>
+
+                  <entry>9994</entry>
+
+                  <entry>67.7</entry>
+                </row>
+
+                <row>
+                  <entry role="bold"><emphasis
+                  role="bold">256</emphasis></entry>
+
+                  <entry>4528865</entry>
+
+                  <entry>4528717</entry>
+
+                  <entry>4528717</entry>
+
+                  <entry>4528621</entry>
+
+                  <entry>9999</entry>
+
+                  <entry>99.9</entry>
+                </row>
+              </tbody>
+            </tgroup>
+          </table>
+        </section>
+      </section>
+
+      <section id="pxe-config-vm">
+        <title>SR-IOV in Virtual Machines</title>
+
+        <para>PCI passthrough tests using pktgen and testpmd in virtual
+        machines.</para>
+
+        <para>pktgen[DPDK]VM - PHY - VM[DPDK] testpmd.</para>
+
+        <para>Measurements:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>pktgen to testpmd in <emphasis
+            role="bold">forwarding</emphasis> mode.</para>
+          </listitem>
+
+          <listitem>
+            <para>pktgen to testpmd in <emphasis
+            role="bold">termination</emphasis> mode.</para>
+          </listitem>
+        </itemizedlist>
+
+        <section id="test-setup-target-four">
+          <title>Test Setup</title>
+
+          <para>SSD boot using the following <literal>grub.cfg</literal>
+          entry: <programlisting>linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp nohz_full=1-7 /
+isolcpus=1-7 rcu-nocbs=1-7 rcu_nocb_poll intel_pstate=disable /
+clocksource=tsc tsc=reliable nohpet nosoftlockup intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0 nmi_watchdog=0 iommu=pt /
+intel_iommu=on  hugepagesz=1GB hugepages=8 default_hugepagesz=1GB /
+hugepagesz=2M hugepages=2048 vfio_iommu_type1.allow_unsafe_interrupts=1</programlisting>Stop
+          other services and mount hugepages: <programlisting>systemctl stop openvswitch
+mkdir -p /mnt/huge
+mount -t hugetlbfs hugetlbfs /mnt/huge</programlisting>Configure SR-IOV
+          interfaces:<programlisting>/usr/share/usertools/dpdk-devbind.py --bind=ixgbe 0000:03:00.0
+echo 2 &gt; /sys/class/net/eno3/device/sriov_numvfs
+ifconfig eno3 10.0.0.1
+modprobe vfio_pci
+/usr/share/usertools/dpdk-devbind.py --bind=vfio-pci 0000:03:10.0
+/usr/share/usertools/dpdk-devbind.py --bind=vfio-pci 0000:03:10.2
+ip link set eno3 vf 0 mac 0c:c4:7a:E5:0F:48
+ip link set eno3 vf 1 mac 0c:c4:7a:BF:52:E7</programlisting>Launch two QEMU
+          instances: <programlisting>taskset -c 4,5 qemu-system-x86_64 -cpu host,+invtsc,migratable=no -M /
+q35 -smp cores=2,sockets=1 -vcpu 0,affinity=4 -vcpu 1,affinity=5 -enable-kvm /
+-nographic -kernel /mnt/qemu/bzImage /
+-drive file=/mnt/qemu/enea-nfv-access-guest-qemux86-64.ext4,if=virtio,/
+format=raw -m 4096 -object memory-backend-file,id=mem,size=4096M,mem-path=/mnt/huge,/
+share=on -numa node,memdev=mem -mem-prealloc -device vfio-pci,host=03:10.0 /
+-append 'root=/dev/vda console=ttyS0 hugepagesz=2M hugepages=1024 /
+isolcpus=1 nohz_full=1 rcu_nocbs=1 irqaffinity=0 rcu_nocb_poll /
+intel_pstate=disable intel_idle.max_cstate=0 /
+processor.max_cstate=0 mce=ignore_ce audit=0'
+
+
+taskset -c 2,3 qemu-system-x86_64 -cpu host,+invtsc,migratable=no -M /
+q35 -smp cores=2,sockets=1 -vcpu 0,affinity=2 -vcpu 1,affinity=3  -enable-kvm /
+-nographic -kernel /mnt/qemu/bzImage /
+-drive file=/mnt/qemu/enea-nfv-access-guest-qemux86-64.ext4,if=virtio,/
+format=raw -m 4096 -object memory-backend-file,id=mem,size=4096M,mem-path=/mnt/huge,/
+share=on -numa node,memdev=mem -mem-prealloc -device vfio-pci,host=03:10.2 /
+-append 'root=/dev/vda console=ttyS0 hugepagesz=2M hugepages=1024 /
+isolcpus=1 nohz_full=1 rcu_nocbs=1 irqaffinity=0 rcu_nocb_poll /
+intel_pstate=disable intel_idle.max_cstate=0 processor.max_cstate=0 /
+mce=ignore_ce audit=0'</programlisting>In the first VM, mount hugepages and
+          start pktgen:<programlisting>mkdir -p /mnt/huge &amp;&amp; \
+mount -t hugetlbfs hugetlbfs /mnt/huge
+modprobe igb_uio
+/usr/share/usertools/dpdk-devbind.py --bind=igb_uio 0000:00:03.0
+cd /usr/share/apps/pktgen
+./pktgen -c 0x3 -- -P -m "1.0"</programlisting>In the pktgen console set the
+          MAC of the destination and start generating
+          packages:<programlisting>set mac 0 0C:C4:7A:BF:52:E7
+str</programlisting>In the second VM, mount hugepages and start
+          testpmd:<programlisting>mkdir -p /mnt/huge &amp;&amp; \
+mount -t hugetlbfs hugetlbfs /mnt/huge
+modprobe igb_uio
+/usr/share/usertools/dpdk-devbind.py --bind=igb_uio 0000:00:03.0
+testpmd -c 0x3 -n 2 -- -i --txd=512 --rxd=512  --port-topology=chained /
+--eth-peer=0,0c:c4:7a:e5:0f:48</programlisting>In order to enable <emphasis
+          role="bold">forwarding</emphasis> mode, in the testpmd console,
+          run:<programlisting>set fwd mac
+start</programlisting>In order to enable <emphasis
+          role="bold">termination</emphasis> mode, in the testpmd console,
+          run:<programlisting>set fwd rxonly
+start</programlisting><table>
+              <title>Results in forwarding mode</title>
+
+              <tgroup cols="5">
+                <tbody>
+                  <row>
+                    <entry align="center"><emphasis
+                    role="bold">Bytes</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">VM1 pktgen pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">VM1 pktgen pps
+                    RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">VM2 testpmd
+                    pps RX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">VM2 testpmd
+                    pps TX</emphasis></entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">64</emphasis></entry>
+
+                    <entry>7102096</entry>
+
+                    <entry>7101897</entry>
+
+                    <entry>7103853</entry>
+
+                    <entry>7103793</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">128</emphasis></entry>
+
+                    <entry>5720016</entry>
+
+                    <entry>5720256</entry>
+
+                    <entry>5722081</entry>
+
+                    <entry>5722083</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">256</emphasis></entry>
+
+                    <entry>3456619</entry>
+
+                    <entry>3456164</entry>
+
+                    <entry>3456319</entry>
+
+                    <entry>3456321</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">512</emphasis></entry>
+
+                    <entry>1846671</entry>
+
+                    <entry>1846628</entry>
+
+                    <entry>1846652</entry>
+
+                    <entry>1846657</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">1024</emphasis></entry>
+
+                    <entry>940799</entry>
+
+                    <entry>940748</entry>
+
+                    <entry>940788</entry>
+
+                    <entry>940788</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">1500</emphasis></entry>
+
+                    <entry>649594</entry>
+
+                    <entry>649526</entry>
+
+                    <entry>649563</entry>
+
+                    <entry>649563</entry>
+                  </row>
+                </tbody>
+              </tgroup>
+            </table><table>
+              <title>Results in termination mode</title>
+
+              <tgroup cols="3">
+                <tbody>
+                  <row>
+                    <entry align="center"><emphasis
+                    role="bold">Bytes</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">VM1 pktgen pps
+                    TX</emphasis></entry>
+
+                    <entry align="center"><emphasis role="bold">VM2 testpmd
+                    RX</emphasis></entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">64</emphasis></entry>
+
+                    <entry>14202904</entry>
+
+                    <entry>14203944</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">128</emphasis></entry>
+
+                    <entry>8434766</entry>
+
+                    <entry>8437525</entry>
+                  </row>
+
+                  <row>
+                    <entry role="bold"><emphasis
+                    role="bold">256</emphasis></entry>
+
+                    <entry>4532131</entry>
+
+                    <entry>4532348</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">512</emphasis></entry>
+
+                    <entry>2349344</entry>
+
+                    <entry>2349032</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">1024</emphasis></entry>
+
+                    <entry>1197293</entry>
+
+                    <entry>1196699</entry>
+                  </row>
+
+                  <row>
+                    <entry><emphasis role="bold">1500</emphasis></entry>
+
+                    <entry>822321</entry>
+
+                    <entry>822276</entry>
+                  </row>
+                </tbody>
+              </tgroup>
+            </table></para>
+        </section>
+      </section>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/book.xml b/doc/book-enea-nfv-access-guide-intel/doc/book.xml
new file mode 100644
index 0000000..ca2f31c
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/book.xml
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!ENTITY % local.common.attrib "xml:base CDATA #IMPLIED">
+]>
+<book id="book_enea_nfv_access_guide">
+  <title><trademark class="registered">Enea</trademark> NFV Access Guide</title>
+  <subtitle>Release Version
+        <xi:include href="eltf_params_updated.xml" xpointer="element(EneaLinux_REL_VER/1)"
+        xmlns:xi="http://www.w3.org/2001/XInclude" /></subtitle>
+                <!-- OLINKDBPATH_USED_BY_XMLMIND ../../s_docbuild/olinkdb  -->
+        <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="overview.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="getting_started.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="hypervisor_virtualization.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="container_virtualization.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="ovs.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="dpdk.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="benchmarks.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="using_nfv_access_sdks.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/container_virtualization.xml b/doc/book-enea-nfv-access-guide-intel/doc/container_virtualization.xml
new file mode 100644
index 0000000..2287146
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/container_virtualization.xml
@@ -0,0 +1,136 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="container-virtualization">
+  <title>Container Virtualization</title>
+
+  <section id="docker">
+    <title>Docker</title>
+
+    <para>Docker is an open-source project that automates the deployment of
+    applications inside software containers, by providing an additional layer
+    of abstraction and automation of operating-system-level virtualization on
+    Linux.</para>
+
+    <para>The software container mechanism uses resource isolation features
+    inside the Linux kernel, such as cgroups and kernel namespaces to allow
+    multiple containers to run within a single Linux instance, avoiding the
+    overhead of starting and maintaining virtual machines.</para>
+
+    <para>Containers are lightweight and include everything needed to run
+    themselves: code, runtime, system tools, system libraries and settings.
+    The main advantage provided by containers is that the encapsulated
+    software is isolated from its surroundings. For example, differences
+    between development and staging environments can be kept separate in order
+    to reduce conflicts between teams running different software on the same
+    infrastructure.</para>
+
+    <para>For a better understanding of what Docker is and how it works, the
+    official documentation provided on the Docker website should be consulted:
+    <ulink
+    url="https://docs.docker.com/">https://docs.docker.com/</ulink>.</para>
+
+    <section id="launch-docker-container">
+      <title>Launching a Docker container</title>
+
+      <para>Docker provides a hello-world container which checks whether your
+      system is running the daemon correctly. This container can be launched
+      by simply running:</para>
+
+      <programlisting>docker run hello-world</programlisting>
+
+      <para>If your installation is working correctly, the following message
+      should be outputted:<programlisting>Hello from Docker!</programlisting></para>
+    </section>
+
+    <section id="run-enfv-guest-image">
+      <title>Run an Enea NFV Access guest image</title>
+
+      <para>Enea NFV Access guest images can run inside Docker as any other
+      container can. Before starting an Enea NFV Access guest image, a root
+      filesystem has to be imported in Docker:</para>
+
+      <programlisting>docker import enea-nfv-access-guest-qemux86-64.tar.gz el7guest</programlisting>
+
+      <para>To check that the Docker image has been imported successfully,
+      run:</para>
+
+      <programlisting>docker images</programlisting>
+
+      <para>Finally, start an Enea NFV Access container with
+      <literal>bash</literal> running as the shell, by running:</para>
+
+      <programlisting>docker run -it el7guest /bin/bash</programlisting>
+    </section>
+
+    <section id="attach-ext-resources-docker-containers">
+      <title>Attach external resources to Docker containers</title>
+
+      <para>Any system resource present on the host machine can be attached or
+      accessed by a Docker container.</para>
+
+      <para>Typically, if a file or folder on the host machine needs to be
+      attached to a container, that container should be launched with the
+      <literal>-v</literal> parameter. For example, to attach the
+      <literal>roots</literal> home folder to a container, the command line
+      for Docker should have the following format:</para>
+
+      <programlisting>docker run -it -v /home/root:/home/host_root/ el7guest /bin/bash</programlisting>
+
+      <para>To check that folders have been properly passed from the host to
+      the container, create a file in the source folder on the host root
+      filesystem and check for its existence inside the containers destination
+      location.</para>
+
+      <section id="attach-vhost-descriptors">
+        <title>Attach vhost file descriptors</title>
+
+        <para>If OVS is running on the host and vhost file descriptors need to
+        be passed to the container, this can be done by either mapping the
+        folder where all the file descriptors are located or mapping the file
+        descriptor itself:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Mapping the folder can be done as exemplified above:</para>
+
+            <programlisting>docker run -it --rm -v /var/run/openvswitch/:/var/run/openvswitch/ el7guest /bin/bash</programlisting>
+          </listitem>
+
+          <listitem>
+            <para>Mapping a file descriptor is done in a similar way, but the
+            <literal>-v</literal> flag needs to point directly to it:</para>
+
+            <programlisting>docker run -it --rm -v /var/run/openvswitch/vhost-user1 el7guest /bin/bash</programlisting>
+          </listitem>
+        </itemizedlist>
+      </section>
+
+      <section id="attach-hugepages-mount-folders">
+        <title>Attach hugepages mount folders</title>
+
+        <para>Hugepages mount folders can also be accessed by a container
+        similarly to how a plain folder is mapped, as shown in 1.3.</para>
+
+        <para>For example, if the host system has hugepages mounted in the
+        <literal>/mnt/huge</literal> location, a container can also access
+        hugepages by being launched with:</para>
+
+        <programlisting>docker run -it -v /mnt/huge el7guest /bin/bash</programlisting>
+      </section>
+
+      <section id="access-pci-bus">
+        <title>Access the PCI bus</title>
+
+        <para>If the host machine has multiple SRIOV instances created, a
+        container can access the instances by being given privileged access to
+        the host system. Unlike folders, PCI devices do not have to be mounted
+        explicitly in order to be accessed and will be available to the
+        container if the <literal>--privileged</literal> flag is passed to the
+        command line:</para>
+
+        <programlisting>docker run --privileged -it el7guest /bin/bash</programlisting>
+      </section>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/dpdk.xml b/doc/book-enea-nfv-access-guide-intel/doc/dpdk.xml
new file mode 100644
index 0000000..aa85317
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/dpdk.xml
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="dpdk">
+  <title>Data Plane Development Kit</title>
+
+  <para>The Intel Data Plane Development Kit (DPDK) is a set of user-space
+  libraries and drivers that provides a programming framework for high-speed
+  packet processing applications. The DPDK includes a number of Poll Mode
+  Drivers that enable direct packet transfer between the physical NIC and
+  user-space without using interrupts, bypassing the Linux kernel network
+  stack entirely.</para>
+
+  <para>In order to take advantage of DPDK, Linux <ulink
+  url="https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt">huge
+  pages</ulink> must be enabled in the system. The allocation of huge pages
+  should preferably be done at boot time by passing parameters on the kernel
+  command line. Add the following to the kernel boot parameters:</para>
+
+  <programlisting>default_hugepagesz=1GB hugepagesz=1GB hugepages=8 hugepagesz=2M hugepages=2048</programlisting>
+
+  <para>For DPDK documentation, see <ulink
+  url="http://dpdk.org/doc/guides-17.08/index.html">http://dpdk.org/doc/guides-17.08/index.html</ulink></para>
+
+  <section id="pktgen">
+    <title>Pktgen</title>
+
+    <para>In addition to DPDK, Enea NFV Access includes Pktgen, a
+    software traffic generator that is powered by the DPDK packet processing
+    framework. Pktgen can act as a transmitter or receiver and is capable of
+    generating 10Gbit wire rate traffic with 64 byte frames.</para>
+
+    <para>Pktgen is installed in <literal>/usr/share/apps/pktgen/</literal>
+    and needs to be executed from this directory.</para>
+
+    <para>For Pktgen documentation, see <ulink
+    url="http://pktgen-dpdk.readthedocs.io">http://pktgen-dpdk.readthedocs.io</ulink></para>
+  </section>
+
+  <section id="dpdk-setup">
+    <title>DPDK setup instructions</title>
+
+    <para>The following setup instructions apply to both host and
+    guest.</para>
+
+    <orderedlist>
+      <listitem>
+        <para>To make the hugepage memory available for DPDK, it must be
+        mounted:</para>
+
+        <programlisting>mkdir /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Load the DPDK igb_uio kernel module:</para>
+
+        <programlisting>modprobe igb_uio</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Bind the device to the igb_uio driver:</para>
+
+        <para><programlisting>dpdk-devbind --bind=igb_uio &lt;PCI device number&gt;</programlisting>The
+        DPDK provides the dpdk-devbind tool to help binding/unbinding devices
+        from specific drivers. See <ulink
+        url="http://dpdk.org/doc/guides-17.08/tools/devbind.html">http://dpdk.org/doc/guides-17.08/tools/devbind.html</ulink>
+        for more information.</para>
+      </listitem>
+    </orderedlist>
+
+    <para>To print the current status of all known network
+    interfaces:<programlisting>dpdk-devbind --status</programlisting></para>
+
+    <para>At this point the system is ready to run DPDK applications.</para>
+  </section>
+
+  <section id="dpdk-example-test-setup">
+    <title>DPDK example test setup</title>
+
+    <para>This is a simple DPDK test setup using two boards connected
+    back-to-back. One board generates traffic using the Pktgen application,
+    and the other board runs the DPDK testpmd example to forward packets back
+    on the same interface.</para>
+
+    <programlisting>Pktgen [DPDK] - Board 1 PHY &lt;--&gt; Board 2 PHY - [DPDK] testpmd</programlisting>
+
+    <orderedlist>
+      <listitem>
+        <para>Setup DPDK on both boards, following the instructions in
+        <xref linkend="dpdk-setup"/>.</para>
+      </listitem>
+
+      <listitem>
+        <para>On board 1, start the Pktgen application:</para>
+
+        <programlisting>cd /usr/share/apps/pktgen/
+./pktgen -c 0x7 -n 4 --socket-mem 1024 -- -P -m "[1:2].0"</programlisting>
+
+        <para>In the Pktgen console, run:</para>
+
+        <programlisting>start 0</programlisting>
+
+        <para>The Pktgen output will display the traffic configuration and
+        statistics.</para>
+      </listitem>
+
+      <listitem>
+        <para>On board 2, start the testpmd application:</para>
+
+        <programlisting>testpmd -c 0x7 -n 4 -- --txd=512 --rxd=512  --port-topology=chained</programlisting>
+
+        <para>For more information, refer to the testpmd application user
+        guide: <ulink
+        url="http://dpdk.org/doc/guides-17.08/testpmd_app_ug/index.html">http://dpdk.org/doc/guides-17.08/testpmd_app_ug/index.html</ulink>.</para>
+      </listitem>
+    </orderedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/eltf_params_template.xml b/doc/book-enea-nfv-access-guide-intel/doc/eltf_params_template.xml
new file mode 100644
index 0000000..eaa7ebd
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/eltf_params_template.xml
@@ -0,0 +1,151 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="eltf_created_params">
+  <title>File with Parameters in the Book Auto-updated by ELFT</title>
+
+  <note>
+    <para>See the <emphasis
+    role="bold">eltf_params_updated_template_howto_use.txt</emphasis> text
+    file for description of how to create the final <emphasis
+    role="bold">eltf_params_updated.xml</emphasis> from this template and for
+    all <emphasis role="bold">REQUIREMENTS</emphasis>. Use the command
+    "<emphasis role="bold">make eltf</emphasis>" to extract a full list of all
+    ELTF variables, which always begins with ELTF_ and don't only rely on the
+    howto text file list! The plan is that ELTF will auto-update this when
+    needed.</para>
+  </note>
+
+  <section id="host_prereq">
+    <title>Common Parameters</title>
+
+    <bridgehead>A programlisting, ID
+    "eltf-prereq-apt-get-commands-host"</bridgehead>
+
+    <para id="eltf-prereq-apt-get-commands-host"><programlisting>ELTF_PL_HOST_PREREQ</programlisting></para>
+
+    <bridgehead>A programlisting, ID
+    "eltf-getting-repo-install-command"</bridgehead>
+
+    <para id="eltf-getting-repo-install-command"><programlisting>ELTF_PL_GET_REPO</programlisting></para>
+
+    <bridgehead>Several phrase elements, various IDs. Ensure EL_REL_VER is
+    correct also compared to the "previous" REL VER in pardoc-distro.xml
+    "prev_baseline".</bridgehead>
+
+    <para id="EneaLinux_REL_VER"><phrase>ELTF_EL_REL_VER</phrase></para>
+
+    <para id="Yocto_VER"><phrase>ELTF_YOCTO_VER</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>ELTF_YOCTO_NAME</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="ELTF_YOCTO_PROJ_DOWNLOAD_URL">ELTF_YOCTO_PROJ_DOWNLOAD_TXTURL</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="ELTF_EL_DOWNLOAD_URL">ELTF_EL_DOWNLOAD_TXTURL</ulink></para>
+
+    <bridgehead>A programlisting, ID "eltf-repo-cloning-enea-linux". Use
+    $MACHINE/default.xml as parameter, where MACHINE is one of the target
+    directory names in the manifest.</bridgehead>
+
+    <para id="eltf-repo-cloning-enea-linux"><programlisting>ELTF_PL_CLONE_W_REPO</programlisting></para>
+
+    <bridgehead>A table with ONE row, only the row with ID
+    "eltf-eclipse-version-row" is included in the book. MANUALLY BOTH in the
+    template.xml and in the updated.xml, set condition hidden on the
+    &lt;row&gt;, if eclipse is not in the release.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row id="eltf-eclipse-version-row">
+            <entry>Eclipse version ELTF_ECLIPSE_VERSION plus command line
+            development tools are included in this Enea NFV Access release.</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <bridgehead>Below is one big section with title "Supported Targets with
+    Parameters". The entire section is included completely in the book via ID
+    "eltf-target-tables-section" and shall be LAST in the template. The
+    template contains ONE target subsection. COPY/APPEND it, if multiple
+    targets exist in the release and optionally add rows with additional
+    target parameters in each target subsection table.</bridgehead>
+  </section>
+
+  <section id="eltf-target-tables-section">
+    <title>Supported Targets with Parameters</title>
+
+    <para>The tables below describes the target(s) supported in this Enea
+    NFV Access release.</para>
+
+    <section id="eltf-target-table-ELTF_T_MANIFEST_DIR">
+      <title>MACHINE ELTF_T_MANIFEST_DIR - Information</title>
+
+      <para><informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="6*" />
+
+            <colspec colwidth="9*" />
+
+            <tbody>
+              <row>
+                <entry>Target official name</entry>
+
+                <entry>ELTF_T_NAME</entry>
+              </row>
+
+              <row>
+                <entry>Architecture and Description</entry>
+
+                <entry>ELTF_T_ARC_DESC</entry>
+              </row>
+
+              <row>
+                <entry>Link to target datasheet</entry>
+
+                <entry>See <ulink
+                url="ELTF_T_DS_URL">ELTF_T_DS_TXTURL</ulink></entry>
+              </row>
+
+              <row>
+                <entry>Poky version</entry>
+
+                <entry>ELTF_T_POKY_VER</entry>
+              </row>
+
+              <row>
+                <entry>GCC version</entry>
+
+                <entry>ELTF_T_GCC_VER</entry>
+              </row>
+
+              <row>
+                <entry>Linux Kernel Version</entry>
+
+                <entry>ELTF_T_KERN_VER</entry>
+              </row>
+
+              <row>
+                <entry>Supported Drivers</entry>
+
+                <entry>ELTF_T_DRIVERS</entry>
+              </row>
+
+              <row>
+                <entry>Enea rpm folder for downloading RPM packages for this
+                target</entry>
+
+                <entry><ulink
+                url="ELTF_T_EL_RPM_URL">ELTF_T_EL_RPM_TXTURL</ulink></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable></para>
+    </section>
+
+    <!-- ELTFADD_MORE_TARGET_SECTIONS_BELOW_IF_NEEDED -->
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-guide-intel/doc/eltf_params_updated.xml
new file mode 100644
index 0000000..1db30fd
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/eltf_params_updated.xml
@@ -0,0 +1,165 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="eltf_created_params">
+  <title>File with Parameters in the Book Auto-updated by ELFT</title>
+
+  <note>
+    <para>See the <emphasis
+    role="bold">eltf_params_updated_template_howto_use.txt</emphasis> text
+    file for description of how to create the final <emphasis
+    role="bold">eltf_params_updated.xml</emphasis> from this template and for
+    all <emphasis role="bold">REQUIREMENTS</emphasis>. Use the command
+    "<emphasis role="bold">make eltf</emphasis>" to extract a full list of all
+    ELTF variables, which always begins with ELTF_ and don't only rely on the
+    howto text file list! The plan is that ELTF will auto-update this when
+    needed.</para>
+  </note>
+
+  <section id="host_prereq">
+    <title>Common Parameters</title>
+
+    <bridgehead>A programlisting, ID
+    "eltf-prereq-apt-get-commands-host"</bridgehead>
+
+    <para id="eltf-prereq-apt-get-commands-host"><programlisting># Host Ubuntu 14.04.5 LTS 64bit
+sudo apt-get -y update
+sudo apt-get -y install sed wget subversion git-core coreutils unzip texi2html \
+   texinfo libsdl1.2-dev docbook-utils fop gawk python-pysqlite2 diffstat \
+   make gcc build-essential xsltproc g++ desktop-file-utils chrpath  \
+   libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm \
+   libxml-parser-perl</programlisting></para>
+
+    <bridgehead>A programlisting, ID
+    "eltf-getting-repo-install-command"</bridgehead>
+
+    <para id="eltf-getting-repo-install-command"><programlisting>mkdir -p ~/bin
+curl https://storage.googleapis.com/git-repo-downloads/repo &gt; ~/bin/repo
+chmod a+x ~/bin/repo
+export PATH=~/bin:$PATH</programlisting></para>
+
+    <bridgehead>Several phrase elements, various IDs. Ensure EL_REL_VER is
+    correct also compared to the "previous" REL VER in pardoc-distro.xml
+    "prev_baseline".</bridgehead>
+
+    <para id="EneaLinux_REL_VER"><phrase>1.1</phrase></para>
+
+    <para id="Yocto_VER"><phrase>2.1</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>krogoth</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="http://www.yoctoproject.org/downloads/core/krogoth/21">http://www.yoctoproject.org/downloads/core/krogoth/21</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="https://linux.enea.com/6">https://linux.enea.com/6</ulink></para>
+
+    <bridgehead>A programlisting, ID "eltf-repo-cloning-enea-linux". Use
+    $MACHINE/default.xml as parameter, where MACHINE is one of the target
+    directory names in the manifest.</bridgehead>
+
+    <para id="eltf-repo-cloning-enea-linux"><programlisting>mkdir enea-linux
+cd enea-linux
+repo init -u git@git.enea.com:linux/manifests/el_manifests-virtualization.git \
+    -b refs/tags/EL6 -m $MACHINE/default.xml
+repo sync</programlisting></para>
+
+    <bridgehead>A table with ONE row, only the row with ID
+    "eltf-eclipse-version-row" is included in the book. MANUALLY in book, set
+    condition hidden if eclipse is not in the release. Do this both in
+    template.xml and updated.xml.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row condition="hidden" id="eltf-eclipse-version-row">
+            <entry>Eclipse version 4.3 (Mars) plus command line development
+            tools are included in this Enea NFV Access release.</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <bridgehead>Below is one big section with title "Supported Targets with
+    Parameters". The entire section is included completely in the book via ID
+    "eltf-target-tables-section" and shall be LAST in the template. The
+    template contains ONE target subsection. COPY/APPEND it, if multiple
+    targets exist in the release and optionally add rows with additional
+    target parameters in each target subsection table.</bridgehead>
+  </section>
+
+  <section id="eltf-target-tables-section">
+    <title>Supported Reference Boards with Parameters</title>
+
+    <para>The tables below describes the target(s) supported in this Enea NFV
+    Access release.</para>
+
+    <section id="eltf-target-table-p2041rdb">
+      <title>MACHINE p2041rdb - Information</title>
+
+      <para><informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="6*" />
+
+            <colspec colwidth="9*" />
+
+            <tbody>
+              <row>
+                <entry>Target official name</entry>
+
+                <entry>P2041RDB</entry>
+              </row>
+
+              <row>
+                <entry>Architecture and Description</entry>
+
+                <entry>Power, e500mc</entry>
+              </row>
+
+              <row>
+                <entry>Link to target datasheet</entry>
+
+                <entry>See <ulink
+                url="http://www.nxp.com/products/microcontrollers-and-processors/power-architecture-processors/qoriq-power-architecture-processors/p2041-qoriq-reference-design-board:RDP2041BOARD">link
+                to NXP's datasheet</ulink></entry>
+              </row>
+
+              <row>
+                <entry>Poky version</entry>
+
+                <entry>Git-commit-id:
+                75ca53211488a3e268037a44ee2a7ac5c7181bd2</entry>
+              </row>
+
+              <row>
+                <entry>GCC version</entry>
+
+                <entry>5.3</entry>
+              </row>
+
+              <row>
+                <entry>Linux Kernel Version</entry>
+
+                <entry>3.12</entry>
+              </row>
+
+              <row>
+                <entry>Supported Drivers</entry>
+
+                <entry>Ethernet, I2C, SPI, PCI Express, USB, Flash,
+                SD/SDHC/SDXC, RTC</entry>
+              </row>
+
+              <row>
+                <entry>Enea rpm folder for downloading RPM packages for this
+                target</entry>
+
+                <entry><ulink
+                url="https://linux.enea.com/6/p2041rgb/rpm">https://linux.enea.com/6/p2041rgb/rpm</ulink></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable></para>
+    </section>
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/getting_started.xml b/doc/book-enea-nfv-access-guide-intel/doc/getting_started.xml
new file mode 100644
index 0000000..dac3015
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/getting_started.xml
@@ -0,0 +1,639 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="plat-release-content">
+  <title>Getting Started with Enea NFV Access</title>
+
+  <para>Using Enea NFV Access requires access to a Linux machine, which is
+  used for preparing a bootable drive or for developing applications. System
+  requirements for the development host are detailed in the <xi:include
+  href="../../s_docbuild/olinkdb/pardoc-common.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(book_enea_nfv_access_release_info/1)" />.</para>
+
+  <section id="sysshell_config">
+    <title>Default Shell Configuration</title>
+
+    <para>Before installing Enea NFV Access, make sure that bash is the
+    default shell.</para>
+
+    <para><emphasis role="bold">To verify the default system
+    shell</emphasis></para>
+
+    <itemizedlist>
+      <listitem>
+        <para>If your system runs Ubuntu, use list to verify if
+        <filename>/usr/bin</filename> is a symbolic link to <emphasis
+        role="bold">bash</emphasis>:</para>
+
+        <programlisting># ls -l /bin/sh
+lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; bash</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Optionally, in case the link points to <literal>dash</literal>,
+        change it through the following steps:</para>
+
+        <programlisting># ls -l /bin/sh
+lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; dash
+# sudo dpkg-reconfigure dash
+Use dash as the default system shell (/bin/sh)? No</programlisting>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="access_installer">
+    <title>Enea NFV Access Installer</title>
+
+    <para>The easiest way to get started with Enea NFV Access is by using the
+    installer provided for each supported architecture in this release. Each
+    installer guides you in the creation of a bootable Enea NFV Access
+    installation on a physical media.</para>
+
+    <section id="prereq">
+      <title>Prerequisites</title>
+
+      <para>The following files are needed on the development host
+      machine:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>A GRUB.efi binary - available from the <ulink url="???">GNU
+          GRUB download page</ulink>.</para>
+        </listitem>
+
+        <listitem>
+          <para>For booting from an SSD/HDD: a rootfs that needs to be
+          installed on the board (e.g.
+          <filename>[path_to_EneaNFV_Access_folder]/[architecture]/inteld1521/images/enea-nfv-access/enea-nfv-access.tar.gz</filename>).</para>
+        </listitem>
+
+        <listitem>
+          <para>For USB booting: a development based rootfs (e.g.
+          <filename>[path_to_EneaNFV_Access_folder]/[architecture]/inteld1521/images/enea-nfv-access-dev/enea-nfv-access-dev-inteld1521.tar.gz</filename>).</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>Using the installer on the development host requires the
+      following:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>A physical drive of 16GB or larger</para>
+        </listitem>
+
+        <listitem>
+          <para>Root permissions</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+
+    <section id="installer_setup_usage">
+      <title>Installer Setup and Usage</title>
+
+      <para><emphasis role="bold">To install Enea NFV Access on a physical
+      drive</emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Go to the installer location: <programlisting># cd [path_to_EneaNFV_Access_folder]/[architecture]/
+install/nfv-installer/script-installer</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Execute the script file, this will bring you to the installer
+          prompt: <programlisting># sudo ./nfv_installer.sh</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Optionally, press ENTER to see the list of available
+          commands:<programlisting>help - displays a guide on how to use the installer
+list-params - lists all available parameters
+list-steps - lists the installer steps and the parameters that they depend on
+set - sets a parameter (e.g. <literal>set drive=/dev/sda</literal>)
+clear - clears a parameter (e.g. <literal>clear drive</literal>)
+list-partitions - lists current drives and partitions
+dry - performs a simulation test run
+run - executes the installer, using the values you set for each parameter
+q or quit - exits the script</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Set the required parameters depending on what steps you want
+          to run:</para>
+
+          <note>
+            <para>When using the installer for the first time, make sure to
+            set ALL parameters in order to be able to run all steps. See <xref
+                linkend="example_two">
+                 "Example 2" 
+              </xref> for details.</para>
+          </note>
+
+          <para><programlisting># set &lt;parameter_name&gt;=&lt;parameter_value&gt;</programlisting></para>
+
+          <orderedlist>
+            <listitem>
+              <para><parameter>drive=&lt;/dev/sdaX&gt;</parameter> - the drive
+              to partition</para>
+            </listitem>
+
+            <listitem>
+              <para><parameter>grub_binary=&lt;file&gt;</parameter> - points
+              to the <filename>GRUB</filename> executable to be installed
+              where <filename>grub_destination</filename> is set.</para>
+            </listitem>
+
+            <listitem>
+              <para><parameter>grub_destination=&lt;drive&gt;</parameter> -
+              specifies the partition where <filename>GRUB</filename> will be
+              installed</para>
+            </listitem>
+
+            <listitem>
+              <para><parameter>rootfs_destination=&lt;drive&gt;</parameter> -
+              specifies the partition where the <filename>rootfs</filename>
+              will be deployed, used by <filename>GRUB</filename> to boot off
+              of.</para>
+            </listitem>
+
+            <listitem>
+              <para><parameter>rootfs_targz=&lt;rootfs.tar.gz
+              file&gt;</parameter> - the archive of the Enea NFV Access
+              <filename>rootfs</filename> you wish to unpack to where
+              <filename>rootfs_destination</filename> is set. Which file you
+              unpack depends on whether you booting from an SSD/HDD or from a
+              USB drive.</para>
+            </listitem>
+          </orderedlist>
+        </listitem>
+
+        <listitem>
+          <para>Optionally, perform a test run before affecting the actual
+          layout of the physical media with the command: <programlisting>dry</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Run the installer: <programlisting>run</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Exit the script: <programlisting>quit</programlisting></para>
+        </listitem>
+      </orderedlist>
+
+      <para>The Enea NFV Access installer creates a bootable media by
+      performing three steps. Each step is executed or not depending on
+      whether certain parameters are set:</para>
+
+      <orderedlist>
+        <listitem>
+          <para><command>Format drive</command> - creates a 512MB partition
+          which will be used by <filename>GRUB</filename>, and another to be
+          used for the <filename>rootfs</filename> (it should occupy the rest
+          of the physical media minus the first partition). This step depends
+          on the following parameter(s): <programlisting>drive=</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">GRUB install</emphasis> - Installs the
+          <literal>grub_binary</literal> on the drive set for
+          <literal>grub_destination</literal>. A <filename>grub.cfg</filename>
+          file will be created that will be configured to boot off of
+          <literal>rootfs_destination</literal>. This step depends on the
+          following parameters:<programlisting>grub_destination=
+grub_binary=
+rootfs_destination=</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Root Filesystem install</emphasis> -
+          Copies and unpacks the files found in
+          <literal>rootfs_targz</literal> to the
+          <literal>rootfs_destination</literal>. This step depends on the
+          following parameters:<programlisting>rootfs_targz=
+rootfs_destination=</programlisting></para>
+        </listitem>
+      </orderedlist>
+
+      <para>After using the installer and setting up the bootable media,
+      connect it to the target machine and configure the target machine to use
+      it as a primary boot device.</para>
+    </section>
+
+    <section id="examples">
+      <title>Examples of Execution</title>
+
+      <para>Below are a few examples of setups that the Enea NFV Access
+      installer can be used for:</para>
+
+      <example id="example_one">
+        <title>Partitioning a drive</title>
+
+        <programlisting>set drive=/dev/sda
+run</programlisting>
+      </example>
+
+      <example id="example_two">
+        <title>Partitioning a drive, installing GRUB and a Root
+        Filesystem:</title>
+
+        <programlisting>set drive=/dev/sda
+set grub_destination=/dev/sda1
+set grub_binary=/home/user/grub-binary.efi
+set rootfs_destination=/dev/sda2
+set rootfs_targz=/home/user/rootfs.tar.gz
+run</programlisting>
+      </example>
+
+      <example id="example_three">
+        <title>Deploying ONLY a root filesystem:</title>
+
+        <programlisting>set rootfs_destination=/dev/sda2
+set rootfs_targz=/home/user/rootfs.tar.gz
+run</programlisting>
+      </example>
+    </section>
+
+    <section id="troubleshooting">
+      <title>Troubleshooting</title>
+
+      <para>GRUB might display the following errors if the default
+      configuration is set to use <filename>hd0</filename> as the primary
+      drive for booting:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>error: no such partition</literal></para>
+        </listitem>
+
+        <listitem>
+          <para><literal>error: disk not found</literal></para>
+        </listitem>
+      </itemizedlist>
+
+      <para>These errors have two possible causes:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>The drive where Enea NFV Access was installed is not
+          identified as <literal>hd0</literal> by BIOS.</para>
+        </listitem>
+
+        <listitem>
+          <para>BIOS has assigned the <literal>hd0</literal> label to a
+          different drive (e.g. a USB stick) than the one where Enea NFV
+          Access was installed.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>To rectify these problems the primary boot drive must be assigned
+      to the correct partition.</para>
+
+      <para><emphasis role="bold">To change the partition for the primary boot
+      drive</emphasis></para>
+
+      <orderedlist>
+        <listitem>
+          <para>Restart the host and in the <filename>GRUB</filename>
+          selection screen, enter the command line by pressing
+          <command>C</command>:</para>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center" contentwidth="600"
+                         fileref="images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg" />
+            </imageobject>
+          </mediaobject>
+        </listitem>
+
+        <listitem>
+          <para>List all of the available partitions with
+          <command>ls</command>: <programlisting>partition list example</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>In order to identify where Enea NFV Access was installed, for
+          each available partition run <emphasis role="bold">ls
+          &lt;partition&gt;</emphasis>: <programlisting>ls hd0</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>After identifying the partition, return to the GRUB selection
+          screen by pressing <command>esc</command></para>
+        </listitem>
+
+        <listitem>
+          <para>Press <command>e</command> to edit and set the boot partition
+          to the one identified previously: <programlisting>edit and set partition example</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>To reboot to see if the change worked, press:
+          <command>F10</command></para>
+        </listitem>
+      </orderedlist>
+    </section>
+  </section>
+
+  <section condition="hidden" id="release-content">
+    <title>NFV Access Release content</title>
+
+    <para>The NFV Access 1.1 Release contains along with other items,
+    documentation, pre-built kernels and images, a bootloader and a
+    SDK.</para>
+
+    <para>The directories structure is detailed below:</para>
+
+    <programlisting>-- documentation/
+   /* NFV Access documentation */
+-- inteld1521/
+   /* artifacts for the host side */
+        -- deb/
+           /* deb packages */
+        -- images/
+            -- enea-image-virtualization-host
+               /* precompiled artifacts for the Host release image */
+                -- various artifacts
+            -- enea-image-virtualization-host-sdk
+               /* precompiled artifacts for the Host SDK image.
+               The SDK image contains userspace tools and kernel
+               configurations necessary for developing, debugging
+               and profiling applications and kernel modules */
+                -- various artifacts
+        -- sdk
+           /* NFV Access SDK for the host */
+                -- enea-glibc-x86_64-enea-image-virtualization-host-sdk /
+                   -corei7-64-toolchain-7.0.sh
+                   /* self-extracting archive installing
+                   cross-compilation toolchain for the host */
+-- qemux86-64
+   /* artifacts for the guest side */
+        -- deb/
+           /* deb packages */
+        -- images/
+            -- enea-image-virtualization-guest
+               /* precompiled artifacts for the Guest image */
+                -- various artifacts
+        -- sdk
+           /* NFV Access SDK for the guest */
+                -- enea-glibc-x86_64-enea-image-virtualization-guest-sdk /
+                   -core2-64-toolchain-7.0.sh
+                   /* self-extracting archive installing cross-compilation
+                   toolchain for the guest (QEMU x86-64) */</programlisting>
+
+    <para>For each combination of image and target, the following set of
+    artifacts is available:</para>
+
+    <programlisting>-- bzImage
+   /* kernel image */
+-- bzImage-&lt;target&gt;.bin
+   /* kernel image, same as above */
+-- config-&lt;target&gt;.config
+   /* kernel configuration file */
+-- core-image-minimal-initramfs-&lt;target&gt;.cpio.gz
+   /* cpio archive of the initramfs */
+-- core-image-minimal-initramfs-&lt;target&gt;.qemuboot.conf
+   /* qemu config file for the initramfs image */
+-- &lt;image-name&gt;-&lt;target&gt;.ext4
+   /* EXT4 image of the rootfs */
+-- &lt;image-name&gt;-&lt;target&gt;.hddimg
+   /* msdos filesystem containing syslinux, kernel, initrd and rootfs image */
+-- &lt;image-name&gt;-&lt;target&gt;.iso
+   /* CD .iso image */
+-- &lt;image-name&gt;-&lt;target&gt;.qemuboot.conf
+   /* qemu config file for the image */
+-- &lt;image-name&gt;-&lt;target&gt;.tar.gz
+   /* tar archive of the image */
+-- &lt;image-name&gt;-&lt;target&gt;.wic
+   /* Wic image */
+-- microcode.cpio
+   /* kernel microcode data */
+-- modules-&lt;target&gt;.tgz
+   /* external kernel modules */
+-- ovmf.*.qcow2
+   /* ovmf firmware for uefi support in qemu */
+-- rmc.db
+   /* Central RMC Database */
+-- systemd-bootx64.efi
+   /* systemd-boot EFI file */
+-- grub-efi-bootx64.efi
+   /* GRUB EFI file */</programlisting>
+  </section>
+
+  <section condition="hidden" id="prebuilt-artifacts">
+    <title>How to use the Prebuilt Artifacts</title>
+
+    <section id="boot-ramdisk">
+      <title>Booting Enea NFV Access using RAMDISK</title>
+
+      <para>There may be use cases, especially at first target ramp-up, where
+      the HDD/SDD has no partitions and you need to prepare the disks for
+      boot. Booting from ramdisk can help with this task.</para>
+
+      <para>The prerequisites needed to proceed:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Enea NFV Access ext4 rootfs image -
+          enea-nfv-access-inteld1521.ext4.gz</para>
+        </listitem>
+
+        <listitem>
+          <para>Enea NFV Access kernel image - bzImage</para>
+        </listitem>
+
+        <listitem>
+          <para>BIOS has PXE boot enabled</para>
+        </listitem>
+
+        <listitem>
+          <para>PXE/tftp server configured and connected (ethernet) to
+          target.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>Unzip enea-nfv-access-inteld1521.ext4 and copy bzImage and
+      enea-nfv-access-inteld1521.ext4 images to the tftpserver configured for
+      PXE boot.</para>
+
+      <para>Use the following as an example for the PXE configuration
+      file:</para>
+
+      <programlisting>default vesamenu.c32
+prompt 1
+timeout 0
+
+label el_ramfs
+    menu label ^EneaLinux_RAMfs
+    kernel bzImage
+    append root=/dev/ram0 initrd=enea-nfv-access-inteld1521.ext4 /
+    ramdisk_size=1200000 console=ttyS0,115200 eralyprintk=ttyS0,115200</programlisting>
+
+      <para>Restart the target. Then enter (F11) in the Boot Menu and select
+      the Ethernet interface used for PXE boot. From the PXE Boot Menu select
+      <emphasis role="bold">Enea NFV Access_RAMfs</emphasis>. Once the Enea
+      NFV Access is started you can partition the HDD/SDD and install GRUB as
+      described in in the following section.</para>
+    </section>
+
+    <section id="install-grub">
+      <title>Partitioning a new harddisk and installing GRUB</title>
+
+      <para>The prerequisites needed:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>grub (<literal>grub-efi-bootx64.efi</literal>) - availalble as
+          a pre-built artifact under
+          <literal>inteld1521/images/enea-nfv-access</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>e2fsprogs-mke2fs_1.43.4-r0.0_amd64.deb,/</literal></para>
+
+          <para><literal>dosfstools_4.1-r0.0_amd64.deb</literal> - available
+          under <literal>inteld1521/deb</literal>.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>Proceed using the following steps:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Boot target with Enea NFV Access from RAMDISK</para>
+        </listitem>
+
+        <listitem>
+          <para>Install prerequisite packages:</para>
+
+          <programlisting>&gt; dpkg -i e2fsprogs-mke2fs_1.43.4-r0.0_amd64.deb
+&gt; dpkg -i dosfstools_4.1-r0.0_amd64.deb</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Partition the disk:</para>
+
+          <programlisting>&gt; fdisk /dev/sda
+fdisk&gt; g   {GPT partition type}
+fdisk&gt; n
+fdisk&gt; 1
+fdisk&gt;     {default start part}
+fdisk&gt; +512M
+fdisk&gt; t
+fdisk&gt; 1 {ESP/EFI partition}
+fdisk&gt; n
+fdisk&gt; 2
+fdisk&gt;    {default start part}
+fdisk&gt; +18G
+fdisk&gt; 3
+fdisk&gt;    {default start part}
+fdisk&gt; +20G
+...
+fdisk&gt; 7
+fdisk&gt;  {default start part}
+fdisk&gt;  {default end end part}
+
+fdisk&gt; p  {print partion table}
+fdisk&gt; w   {write to disk}
+fdisk&gt; q</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Format the partitions:</para>
+
+          <programlisting>&gt; mkfs.fat -F32 -nEFI /dev/sda1
+&gt; mkfs.ext4 -LROOT /dev/sda2
+&gt; mkfs.ext4 -LROOT /dev/sda3
+&gt; mkfs.ext4 -LROOT /dev/sda4
+&gt; mkfs.ext4 -LROOT /dev/sda5
+&gt; mkfs.ext4 -LROOT /dev/sda6
+&gt; mkfs.ext4 -LROOT /dev/sda7</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Create a GRUB partition:</para>
+
+          <programlisting>&gt; mkdir /mnt/boot
+&gt; mount /dev/sda1 /mnt/boot
+&gt; mkdir -p /mnt/boot/EFI/boot
+
+&gt; cp grub-efi-bootx64.efi /mnt/boot/EFI/boot/bootx64.efi
+&gt; vi /mnt/boot/EFI/boot/grub.cfg
+default=1
+
+menuentry "Linux Reference Image" {
+  linux (hd0,gpt2)/boot/bzImage root=/dev/sda2 ip=dhcp
+}
+
+menuentry "Linux sda3" {
+  linux (hd0,gpt3)/boot/bzImage root=/dev/sda3 ip=dhcp
+}
+
+menuentry "Linux sda4" {
+  linux (hd0,gpt4)/boot/bzImage root=/dev/sda4 ip=dhcp
+}
+
+menuentry "Linux sda5" {
+  linux (hd0,gpt5)/boot/bzImage root=/dev/sda5 ip=dhcp
+}
+
+menuentry "Linux sda6" {
+  linux (hd0,gpt6)/boot/bzImage root=/dev/sda6 ip=dhcp
+}
+
+menuentry "Linux sda7" {
+  linux (hd0,gpt7)/boot/bzImage root=/dev/sda7 ip=dhcp
+}</programlisting>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="boot-hdd">
+      <title>Installing and booting Enea NFV Access on the harddisk</title>
+
+      <para>After partitioning the harddisk, boot Enea NFV Access from RAMFS
+      or from a reference image installed on one of the partitions.</para>
+
+      <para>To install Enea NFV Access image on a partition follow these
+      steps:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Copy your image on target:</para>
+
+          <programlisting>server&gt; scp ./enea-nfv-access-inteld1521.tar.gz /
+root@&lt;target_ip&gt;:/home/root/</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Extract image onto the desired partition:</para>
+
+          <programlisting>target&gt; mount /dev/sda3 /mnt/sda
+target&gt; tar -pzxf /home/root/enea-nfv-access-inteld1521.tar.gz /
+-C /mnt/sda</programlisting>
+
+          <para>Alternately, you can do both steps in one command from the
+          server:</para>
+
+          <programlisting>server&gt; cat ./enea-nfv-access-inteld1521.tar.gz | /
+ssh root@&lt;target_ip&gt; "cd /mnt/sda6; tar -zxf -"</programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Reboot</para>
+        </listitem>
+
+        <listitem>
+          <para>From the GRUB menu select your partition</para>
+        </listitem>
+      </orderedlist>
+
+      <note>
+        <para>In order to change kernel boot parameters you need to mount the
+        GRUB partition (i.e. <literal>/dev/sda1</literal>) and change the
+        <literal>EFI/boot/grub.cfg</literal> file.</para>
+      </note>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/hypervisor_virtualization.xml b/doc/book-enea-nfv-access-guide-intel/doc/hypervisor_virtualization.xml
new file mode 100644
index 0000000..9733544
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/hypervisor_virtualization.xml
@@ -0,0 +1,744 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="hypervisor_virt">
+  <title>Hypervisor Virtualization</title>
+
+  <para>The KVM, Kernel-based Virtual Machine, is a virtualization
+  infrastructure for the Linux kernel which turns it into a hypervisor. KVM
+  requires a processor with a hardware virtualization extension.</para>
+
+  <para>KVM uses QEMU, an open source machine emulator and virtualizer, to
+  virtualize a complete system. With KVM it is possible to run multiple guests
+  of a variety of operating systems, each with a complete set of virtualized
+  hardware.</para>
+
+  <section id="launch_virt_machine">
+    <title>Launching a Virtual Machine</title>
+
+    <para>QEMU can make use of KVM when running a target architecture that is
+    the same as the host architecture. For instance, when running
+    qemu-system-x86_64 on an x86-64 compatible processor (containing
+    virtualization extensions Intel VT or AMD-V), you can take advantage of
+    the KVM acceleration, giving you benefit for your host and your guest
+    system.</para>
+
+    <para>Enea NFV Access includes an optimizied version of QEMU with KVM-only
+    support. To use KVM pass<command> --enable-kvm</command> to QEMU.</para>
+
+    <para>The following is an example of starting a guest:</para>
+
+    <programlisting>taskset -c 0,1 qemu-system-x86_64 \
+-cpu host -M q35 -smp cores=2,sockets=1 \
+-vcpu 0,affinity=0 -vcpu 1,affinity=1  \
+-enable-kvm -nographic \
+-kernel bzImage \
+-drive file=enea-nfv-access-guest-qemux86-64.ext4,if=virtio,format=raw \
+-append 'root=/dev/vda console=ttyS0,115200' \
+-m 4096 \
+-object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on \
+-numa node,memdev=mem -mem-prealloc</programlisting>
+  </section>
+
+  <section id="qemu_boot">
+    <title>Main QEMU boot options</title>
+
+    <para>Below are detailed all the pertinent boot options for the QEMU
+    emulator:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>SMP - at least 2 cores should be enabled in order to isolate
+        application(s) running in virtual machine(s) on specific cores for
+        better performance.</para>
+
+        <programlisting>-smp cores=2,threads=1,sockets=1 \</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>CPU affinity - associate virtual CPUs with physical CPUs and
+        optionally assign a default real time priority to the virtual CPU
+        process in the host kernel. This option allows you to start qemu vCPUs
+        on isolated physical CPUs.</para>
+
+        <programlisting>-vcpu 0,affinity=0   \</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Hugepages - KVM guests can be deployed with huge page memory
+        support in order to reduce memory consumption and improve performance,
+        by reducing CPU cache usage. By using huge pages for a KVM guest, less
+        memory is used for page tables and TLB (Translation Lookaside Buffer)
+        misses are reduced, thereby significantly increasing performance,
+        especially for memory-intensive situations.</para>
+
+        <programlisting>-object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on \</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Memory preallocation - preallocate huge pages at startup time
+        can improve performance but it may affect the qemu boot time.</para>
+
+        <programlisting>-mem-prealloc \</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Enable realtime characteristics - run qemu with realtime
+        features. While that mildly implies that "-realtime" alone might do
+        something, it's just an identifier for options that are partially
+        realtime. If you're running in a realtime or low latency environment,
+        you don't want your pages to be swapped out and mlock does that, thus
+        mlock=on. If you want VM density, then you may want swappable VMs,
+        thus mlock=off.</para>
+
+        <programlisting>-realtime mlock=on \</programlisting>
+      </listitem>
+    </itemizedlist>
+
+    <para>If the hardware does not have an IOMMU (known as "Intel VT-d" on
+    Intel-based machines and "AMD I/O Virtualization Technology" on AMD-based
+    machines), it will not be possible to assign devices in KVM.
+    Virtualization Technology features (VT-d, VT-x, etc.) must be enabled from
+    BIOS on the host target before starting a virtual machine.</para>
+  </section>
+
+  <section id="net_in_guest">
+    <title>Networking in guest</title>
+
+    <section id="vhost-user-support">
+      <title>Using vhost-user support</title>
+
+      <para>The goal of vhost-user is to implement a Virtio transport, staying
+      as close as possible to the vhost paradigm of using shared memory,
+      ioeventfds and irqfds. A UNIX domain socket based mechanism allows the
+      set up of resources used by a number of Vrings shared between two
+      userspace processes, which will be placed in shared memory.</para>
+
+      <para>To run QEMU with the vhost-user backend, you have to provide the
+      named UNIX domain socket which needs to be already opened by the
+      backend:</para>
+
+      <programlisting>-object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on \
+-chardev socket,id=char0,path=/var/run/openvswitch/vhost-user1 \
+-netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
+-device virtio-net-pci,netdev=mynet1,mac=52:54:00:00:00:01  \</programlisting>
+
+      <para>The vHost User standard uses a client-server model. The server
+      creates and manages the vHost User sockets and the client connects to
+      the sockets created by the server. It is recommended to use QEMU as
+      server so the vhost-user client can be restarted without affecting the
+      server, otherwise if the server side dies all clients need to be
+      restarted.</para>
+
+      <para>Using vhost-user in QEMU as server will offer the flexibility to
+      stop and start the virtual machine with no impact on virtual switch from
+      the host (vhost-user-client).</para>
+
+      <programlisting>-chardev socket,id=char0,path=/var/run/openvswitch/vhost-user1,server \</programlisting>
+    </section>
+
+    <section id="tap-interface">
+      <title>Using TAP Interfaces</title>
+
+      <para>QEMU can use TAP interfaces to provide full networking capability
+      for the guest OS:</para>
+
+      <programlisting>-netdev tap,id=net0,ifname=tap0,script=no,downscript=no \
+-device virtio-net-pci,netdev=net0,mac=22:EA:FB:A8:25:AE \</programlisting>
+    </section>
+
+    <section id="vfio-passthrough">
+      <title>VFIO passthrough VF (SR-IOV) to guest</title>
+
+      <para>KVM hypervisor support for attaching PCI devices on the host
+      system to guests. PCI passthrough allows guests to have exclusive access
+      to PCI devices for a range of tasks. PCI passthrough allows PCI devices
+      to appear and behave as if they were physically attached to the guest
+      operating system.</para>
+
+      <para>Preparing an Intel system for PCI passthrough:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Enable the Intel VT-d extensions in BIOS</para>
+        </listitem>
+
+        <listitem>
+          <para>Activate Intel VT-d in the kernel by using
+          <literal>intel_iommu=on</literal> as a kernel boot parameter</para>
+        </listitem>
+
+        <listitem>
+          <para>Allow unsafe interrupts in case the system doesn't support
+          interrupt remapping. This can be done using
+          <literal>vfio_iommu_type1.allow_unsafe_interrupts=1</literal> as a
+          boot kernel parameter.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>Create guest with direct passthrough via VFIO framework like
+      so:</para>
+
+      <programlisting>-device vfio-pci,host=0000:03:10.2 \</programlisting>
+
+      <para>On the host, one or more VirtualFunctions (VFs) must be created in
+      order to be allocated for a guest network to access, before starting
+      QEMU:</para>
+
+      <programlisting>$ echo 2 &gt; /sys/class/net/eno3/device/sriov_numvfs
+$ modprobe vfio_pci
+$ dpdk-devbind.py --bind=vfio-pci 0000:03:10.2</programlisting>
+    </section>
+
+    <section id="multiqueue">
+      <title>Multi-queue</title>
+
+      <para>In order to ensure that network performance scales as the number
+      of vCPUs increases, multi-queue support can be used in QEMU.</para>
+
+      <section id="qemu-multiqueue-support">
+        <title>QEMU multi queue support configuration</title>
+
+        <programlisting>-chardev socket,id=char0,path=/var/run/openvswitch/vhost-user1 \
+-netdev type=vhost-user,id=net0,chardev=char0,queues=2 \
+-device virtio-net-pci,netdev=net0,mac=22:EA:FB:A8:25:AE,mq=on,vectors=6
+where vectors is calculated as: 2 + 2 * queues number.</programlisting>
+      </section>
+
+      <section id="inside-guest">
+        <title>Inside guest</title>
+
+        <para>Linux kernel virtio-net driver (one queue is enabled by
+        default):</para>
+
+        <programlisting>$ ethtool -L combined 2 eth0
+DPDK Virtio PMD
+$ testpmd -c 0x7 -- -i --rxq=2 --txq=2 --nb-cores=2 ...</programlisting>
+
+        <para>For QEMU documentation please see: <ulink
+        url="https://qemu.weilnetz.de/doc/qemu-doc.html">https://qemu.weilnetz.de/doc/qemu-doc.html</ulink>.</para>
+      </section>
+    </section>
+  </section>
+
+  <section id="libvirt">
+    <title>Libvirt</title>
+
+    <para>One way to manage guests in Enea NFV Access is by using
+    <literal>libvirt</literal>. Libvirt is used in conjunction with a daemon
+    (<literal>libvirtd</literal>) and a command line utility (virsh) to manage
+    virtualized environments.</para>
+
+    <para>The libvirt library is a hypervisor-independent virtualization API
+    and toolkit that is able to interact with the virtualization capabilities
+    of a range of operating systems. Libvirt provides a common, generic and
+    stable layer to securely manage domains on a node. As nodes may be
+    remotely located, libvirt provides all methods required to provision,
+    create, modify, monitor, control, migrate and stop the domains, within the
+    limits of hypervisor support for these operations.</para>
+
+    <para>The libvirt daemon runs on the Enea NFV Access host. All tools built
+    on libvirt API connect to the daemon to request the desired operation, and
+    to collect information about the configuration and resources of the host
+    system and guests. <literal>virsh</literal> is a command line interface
+    tool for managing guests and the hypervisor. The virsh tool is built on
+    the libvirt management API.</para>
+
+    <para><emphasis role="bold">Major functionality provided by
+    libvirt</emphasis></para>
+
+    <para>The following is a summary from the libvirt <ulink
+    url="http://wiki.libvirt.org/page/FAQ#What_is_libvirt.3F">home
+    page</ulink> describing the major libvirt features:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para><emphasis role="bold">VM management:</emphasis> Various domain
+        lifecycle operations such as start, stop, pause, save, restore, and
+        migrate. Hotplug operations for many device types including disk and
+        network interfaces, memory, and cpus.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Remote machine support:</emphasis> All
+        libvirt functionality is accessible on any machine running the libvirt
+        daemon, including remote machines. A variety of network transports are
+        supported for connecting remotely, with the simplest being
+        <literal>SSH</literal>, which requires no extra explicit
+        configuration. For more information, see: <ulink
+        url="http://libvirt.org/remote.html">http://libvirt.org/remote.html</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Network interface management:</emphasis>
+        Any host running the libvirt daemon can be used to manage physical and
+        logical network interfaces. Enumerate existing interfaces, as well as
+        configure (and create) interfaces, bridges, vlans, and bond devices.
+        For more details see: <ulink
+        url="https://fedorahosted.org/netcf/">https://fedorahosted.org/netcf/</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Virtual NAT and Route based
+        networking:</emphasis> Any host running the libvirt daemon can manage
+        and create virtual networks. Libvirt virtual networks use firewall
+        rules to act as a router, providing VMs transparent access to the host
+        machines network. For more information, see: <ulink
+        url="http://libvirt.org/archnetwork.html">http://libvirt.org/archnetwork.html</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Storage management:</emphasis> Any host
+        running the libvirt daemon can be used to manage various types of
+        storage: create file images of various formats (raw, qcow2, etc.),
+        mount NFS shares, enumerate existing LVM volume groups, create new LVM
+        volume groups and logical volumes, partition raw disk devices, mount
+        iSCSI shares, and much more. For more details, see: <ulink
+        url="http://libvirt.org/storage.html">http://libvirt.org/storage.html</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Libvirt Configuration:</emphasis> A
+        properly running libvirt requires that the following elements be in
+        place:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Configuration files, located in the directory
+            <literal>/etc/libvirt</literal>. They include the daemon's
+            configuration file <literal>libvirtd.conf</literal>, and
+            hypervisor-specific configuration files, like
+            <literal>qemu.conf</literal> for the QEMU.</para>
+          </listitem>
+
+          <listitem>
+            <para>A running libvirtd daemon. The daemon is started
+            automatically in Enea NFV Access host.</para>
+          </listitem>
+
+          <listitem>
+            <para>Configuration files for the libvirt domains, or guests, to
+            be managed by the KVM host. The specifics for guest domains shall
+            be defined in an XML file of a format specified at <ulink
+            url="http://libvirt.org/formatdomain.html">http://libvirt.org/formatdomain.html</ulink>.
+            XML formats for other structures are specified at <ulink type=""
+            url="http://libvirt.org/format.html">http://libvirt.org/format.html</ulink>.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+    </itemizedlist>
+
+    <section id="boot-kvm-guest">
+      <title>Booting a KVM Guest</title>
+
+      <para>There are several ways to boot a KVM guest. Here we describe how
+      to boot using a raw image. A direct kernel boot can be performed by
+      transferring the guest kernel and the file system files to the host and
+      specifying a <literal>&lt;kernel&gt;</literal> and an
+      <literal>&lt;initrd&gt;</literal> element inside the
+      <literal>&lt;os&gt;</literal> element of the guest XML file, as in the
+      following example:</para>
+
+      <programlisting>&lt;os&gt;
+  &lt;kernel&gt;bzImage&lt;/kernel&gt;
+&lt;/os&gt;
+&lt;devices&gt;
+  &lt;disk type='file' device='disk'&gt;
+    &lt;driver name='qemu' type='raw' cache='none'/&gt;
+    &lt;source file='enea-nfv-access-guest-qemux86-64.ext4'/&gt;
+    &lt;target dev='vda' bus='virtio'/&gt;
+  &lt;/disk&gt;
+&lt;/devices&gt;</programlisting>
+    </section>
+
+    <section id="start-guest">
+      <title>Starting a Guest</title>
+
+      <para>Command <command>virsh create</command> starts a guest:</para>
+
+      <programlisting>virsh create example-guest-x86.xml</programlisting>
+
+      <para>If further configurations are needed before the guest is reachable
+      through <literal>ssh</literal>, a console can be started using command
+      <command>virsh console</command>. The example below shows how to start a
+      console where kvm-example-guest is the name of the guest defined in the
+      guest XML file:</para>
+
+      <programlisting>virsh console kvm-example-guest</programlisting>
+
+      <para>This requires that the guest domain has a console configured in
+      the guest XML file:</para>
+
+      <programlisting>&lt;os&gt;
+  &lt;cmdline&gt;console=ttyS0,115200&lt;/cmdline&gt;
+&lt;/os&gt;
+&lt;devices&gt;
+  &lt;console type='pty'&gt;
+     &lt;target type='serial' port='0'/&gt;
+  &lt;/console&gt;
+&lt;/devices&gt;</programlisting>
+    </section>
+
+    <section id="isolation">
+      <title>Isolation</title>
+
+      <para>It may be desirable to isolate execution in a guest, to a specific
+      guest core. It might also be desirable to run a guest on a specific host
+      core.</para>
+
+      <para>To pin the virtual CPUs of the guest to specific cores, configure
+      the <literal>&lt;cputune&gt;</literal> contents as follows:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>First explicitly state on which host core each guest core
+          shall run, by mapping <literal>vcpu</literal> to
+          <literal>cpuset</literal> in the <literal>&lt;vcpupin&gt;</literal>
+          tag.</para>
+        </listitem>
+
+        <listitem>
+          <para>In the <literal>&lt;cputune&gt;</literal> tag it is further
+          possible to specify on which CPU the emulator shall run by adding
+          the cpuset to the <literal>&lt;emulatorpin&gt;</literal> tag.</para>
+
+          <programlisting>&lt;vcpu placement='static'&gt;2&lt;/vcpu&gt;
+&lt;cputune&gt;
+  &lt;vcpupin vcpu='0' cpuset='2'/&gt;
+  &lt;vcpupin vcpu='1' cpuset='3'/&gt;
+  &lt;emulatorpin cpuset="2"/&gt;
+&lt;/cputune&gt;</programlisting>
+
+          <para><literal>libvirt</literal> will group all threads belonging to
+          a qemu instance into cgroups that will be created for that purpose.
+          It is possible to supply a base name for those cgroups using the
+          <literal>&lt;resource&gt;</literal> tag:</para>
+
+          <programlisting>&lt;resource&gt;
+  &lt;partition&gt;/rt&lt;/partition&gt;
+&lt;/resource&gt;</programlisting>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="network-libvirt">
+      <title>Networking using libvirt</title>
+
+      <para>Command <command>virsh net-create</command> starts a network. If
+      any networks are listed in the guest XML file, those networks must be
+      started before the guest is started. As an example, if the network is
+      defined in a file named example-net.xml, it is started as
+      follows:</para>
+
+      <programlisting>virsh net-create example-net.xml
+&lt;network&gt;
+   &lt;name&gt;sriov&lt;/name&gt;
+   &lt;forward mode='hostdev' managed='yes'&gt;
+     &lt;pf dev='eno3'/&gt;
+   &lt;/forward&gt;
+&lt;/network&gt;</programlisting>
+
+      <para><literal>libvirt</literal> is a virtualization API that supports
+      virtual network creation. These networks can be connected to guests and
+      containers by referencing the network in the guest XML file. It is
+      possible to have a virtual network persistently running on the host by
+      starting the network with command <command>virsh net-define</command>
+      instead of the previously mentioned <command>virsh
+      net-create</command>.</para>
+
+      <para>An example for the sample network defined in
+      <literal>meta-vt/recipes-example/virt-example/files/example-net.xml</literal>:</para>
+
+      <programlisting>virsh net-define example-net.xml</programlisting>
+
+      <para>Command <command>virsh net-autostart</command> enables a
+      persistent network to start automatically when the libvirt daemon
+      starts:</para>
+
+      <programlisting>virsh net-autostart example-net</programlisting>
+
+      <para>Guest configuration file (xml) must be updated to access newly
+      created network like so:</para>
+
+      <programlisting>    &lt;interface type='network'&gt;
+      &lt;source network='sriov'/&gt;
+    &lt;/interface&gt;</programlisting>
+
+      <para>The following presented here are a few modes of network access
+      from guest using <command>virsh</command>:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><emphasis role="bold">vhost-user interface</emphasis></para>
+
+          <para>See the Open vSwitch chapter on how to create vhost-user
+          interface using Open vSwitch. Currently there is no Open vSwitch
+          support for networks that are managed by libvirt (e.g. NAT). As of
+          now, only bridged networks are supported (those where the user has
+          to manually create the bridge).</para>
+
+          <programlisting>    &lt;interface type='vhostuser'&gt;
+      &lt;mac address='00:00:00:00:00:01'/&gt;
+      &lt;source type='unix' path='/var/run/openvswitch/vhost-user1' mode='client'/&gt;
+       &lt;model type='virtio'/&gt;
+      &lt;driver queues='1'&gt;
+        &lt;host mrg_rxbuf='off'/&gt;
+      &lt;/driver&gt;
+    &lt;/interface&gt;</programlisting>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">PCI passthrough
+          (SR-IOV)</emphasis></para>
+
+          <para>KVM hypervisor support for attaching PCI devices on the host
+          system to guests. PCI passthrough allows guests to have exclusive
+          access to PCI devices for a range of tasks. PCI passthrough allows
+          PCI devices to appear and behave as if they were physically attached
+          to the guest operating system.</para>
+
+          <para>Preparing an Intel system for PCI passthrough is done like
+          so:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>Enable the Intel VT-d extensions in BIOS</para>
+            </listitem>
+
+            <listitem>
+              <para>Activate Intel VT-d in the kernel by using
+              <literal>intel_iommu=on</literal> as a kernel boot
+              parameter</para>
+            </listitem>
+
+            <listitem>
+              <para>Allow unsafe interrupts in case the system doesn't support
+              interrupt remapping. This can be done using
+              <literal>vfio_iommu_type1.allow_unsafe_interrupts=1</literal> as
+              a boot kernel parameter.</para>
+            </listitem>
+          </itemizedlist>
+
+          <para>VFs must be created on the host before starting the
+          guest:</para>
+
+          <programlisting>$ echo 2 &gt; /sys/class/net/eno3/device/sriov_numvfs
+$ modprobe vfio_pci
+$ dpdk-devbind.py --bind=vfio-pci 0000:03:10.0
+   &lt;interface type='hostdev' managed='yes'&gt;
+     &lt;source&gt;
+       &lt;address type='pci' domain='0x0' bus='0x03' slot='0x10' function='0x0'/&gt;
+     &lt;/source&gt;
+     &lt;mac address='52:54:00:6d:90:02'/&gt;
+   &lt;/interface&gt;</programlisting>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Bridge interface</emphasis></para>
+
+          <para>In case an OVS bridge exists on host, it can be used to
+          connect the guest:</para>
+
+          <programlisting>    &lt;interface type='bridge'&gt;
+      &lt;mac address='52:54:00:71:b1:b6'/&gt;
+      &lt;source bridge='ovsbr0'/&gt;
+      &lt;virtualport type='openvswitch'/&gt;
+      &lt;address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/&gt;
+    &lt;/interface&gt;</programlisting>
+
+          <para>For further details on the network XML format, see <ulink
+          url="http://libvirt.org/formatnetwork.html">http://libvirt.org/formatnetwork.html</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+
+    <section id="libvirt-guest-config-ex">
+      <title>Libvirt guest configuration examples</title>
+
+      <section id="guest-config-vhost-user-interface">
+        <title>Guest configuration with vhost-user interface</title>
+
+        <programlisting>&lt;domain type='kvm'&gt;
+  &lt;name&gt;vm_vhost&lt;/name&gt;
+  &lt;uuid&gt;4a9b3f53-fa2a-47f3-a757-dd87720d9d1d&lt;/uuid&gt;
+  &lt;memory unit='KiB'&gt;4194304&lt;/memory&gt;
+  &lt;currentMemory unit='KiB'&gt;4194304&lt;/currentMemory&gt;
+  &lt;memoryBacking&gt;
+    &lt;hugepages&gt;
+      &lt;page size='1' unit='G' nodeset='0'/&gt;
+    &lt;/hugepages&gt;
+  &lt;/memoryBacking&gt;
+  &lt;vcpu placement='static'&gt;2&lt;/vcpu&gt;
+  &lt;cputune&gt;
+    &lt;shares&gt;4096&lt;/shares&gt;
+    &lt;vcpupin vcpu='0' cpuset='4'/&gt;
+    &lt;vcpupin vcpu='1' cpuset='5'/&gt;
+    &lt;emulatorpin cpuset='4,5'/&gt;
+  &lt;/cputune&gt;
+  &lt;os&gt;
+    &lt;type arch='x86_64' machine='pc'&gt;hvm&lt;/type&gt;
+    &lt;kernel&gt;/mnt/qemu/bzImage&lt;/kernel&gt;
+    &lt;cmdline&gt;root=/dev/vda console=ttyS0,115200&lt;/cmdline&gt;
+    &lt;boot dev='hd'/&gt;
+  &lt;/os&gt;
+  &lt;features&gt;
+    &lt;acpi/&gt;
+    &lt;apic/&gt;
+  &lt;/features&gt;
+  &lt;cpu mode='host-model'&gt;
+    &lt;model fallback='allow'/&gt;
+    &lt;topology sockets='2' cores='1' threads='1'/&gt;
+    &lt;numa&gt;
+      &lt;cell id='0' cpus='0-1' memory='4194304' unit='KiB' memAccess='shared'/&gt;
+    &lt;/numa&gt;
+  &lt;/cpu&gt;
+  &lt;on_poweroff&gt;destroy&lt;/on_poweroff&gt;
+  &lt;on_reboot&gt;restart&lt;/on_reboot&gt;
+  &lt;on_crash&gt;destroy&lt;/on_crash&gt;
+  &lt;devices&gt;
+    &lt;emulator&gt;/usr/bin/qemu-system-x86_64&lt;/emulator&gt;
+    &lt;disk type='file' device='disk'&gt;
+      &lt;driver name='qemu' type='raw' cache='none'/&gt;
+      &lt;source file='/mnt/qemu/enea-nfv-access-guest-qemux86-64.ext4'/&gt;
+      &lt;target dev='vda' bus='virtio'/&gt;
+    &lt;/disk&gt;
+    &lt;interface type='vhostuser'&gt;
+      &lt;mac address='00:00:00:00:00:01'/&gt;
+      &lt;source type='unix' path='/var/run/openvswitch/vhost-user1' mode='client'/&gt;
+       &lt;model type='virtio'/&gt;
+      &lt;driver queues='1'&gt;
+        &lt;host mrg_rxbuf='off'/&gt;
+      &lt;/driver&gt;
+    &lt;/interface&gt;
+    &lt;serial type='pty'&gt;
+      &lt;target port='0'/&gt;
+    &lt;/serial&gt;
+    &lt;console type='pty'&gt;
+      &lt;target type='serial' port='0'/&gt;
+    &lt;/console&gt;
+  &lt;/devices&gt;
+&lt;/domain&gt;</programlisting>
+      </section>
+
+      <section id="guest-config-pci-passthrough">
+        <title>Guest configuration with PCI passthrough</title>
+
+        <programlisting>&lt;domain type='kvm'&gt;
+  &lt;name&gt;vm_sriov1&lt;/name&gt;
+  &lt;uuid&gt;4a9b3f53-fa2a-47f3-a757-dd87720d9d1d&lt;/uuid&gt;
+  &lt;memory unit='KiB'&gt;4194304&lt;/memory&gt;
+  &lt;currentMemory unit='KiB'&gt;4194304&lt;/currentMemory&gt;
+  &lt;memoryBacking&gt;
+    &lt;hugepages&gt;
+      &lt;page size='1' unit='G' nodeset='0'/&gt;
+    &lt;/hugepages&gt;
+  &lt;/memoryBacking&gt;
+  &lt;vcpu&gt;2&lt;/vcpu&gt;
+  &lt;os&gt;
+    &lt;type arch='x86_64' machine='q35'&gt;hvm&lt;/type&gt;
+    &lt;kernel&gt;/mnt/qemu/bzImage&lt;/kernel&gt;
+    &lt;cmdline&gt;root=/dev/vda console=ttyS0,115200&lt;/cmdline&gt;
+    &lt;boot dev='hd'/&gt;
+  &lt;/os&gt;
+  &lt;features&gt;
+    &lt;acpi/&gt;
+    &lt;apic/&gt;
+  &lt;/features&gt;
+  &lt;cpu mode='host-model'&gt;
+    &lt;model fallback='allow'/&gt;
+    &lt;topology sockets='1' cores='2' threads='1'/&gt;
+    &lt;numa&gt;
+      &lt;cell id='0' cpus='0' memory='4194304' unit='KiB' memAccess='shared'/&gt;
+    &lt;/numa&gt;
+  &lt;/cpu&gt;
+  &lt;on_poweroff&gt;destroy&lt;/on_poweroff&gt;
+  &lt;on_reboot&gt;restart&lt;/on_reboot&gt;
+  &lt;on_crash&gt;destroy&lt;/on_crash&gt;
+  &lt;devices&gt;
+    &lt;emulator&gt;/usr/bin/qemu-system-x86_64&lt;/emulator&gt;
+    &lt;disk type='file' device='disk'&gt;
+      &lt;driver name='qemu' type='raw' cache='none'/&gt;
+      &lt;source file='/mnt/qemu/enea-nfv-access-guest-qemux86-64.ext4'/&gt;
+      &lt;target dev='vda' bus='virtio'/&gt;
+    &lt;/disk&gt;
+   &lt;interface type='hostdev' managed='yes'&gt;
+     &lt;source&gt;
+       &lt;address type='pci' domain='0x0' bus='0x03' slot='0x10' function='0x0'/&gt;
+     &lt;/source&gt;
+     &lt;mac address='52:54:00:6d:90:02'/&gt;
+   &lt;/interface&gt;
+    &lt;serial type='pty'&gt;
+      &lt;target port='0'/&gt;
+    &lt;/serial&gt;
+    &lt;console type='pty'&gt;
+      &lt;target type='serial' port='0'/&gt;
+    &lt;/console&gt;
+  &lt;/devices&gt;
+&lt;/domain&gt;</programlisting>
+      </section>
+
+      <section id="guest-config-bridge-interface">
+        <title>Guest configuration with bridge interface</title>
+
+        <programlisting>&lt;domain type='kvm'&gt;
+  &lt;name&gt;vm_bridge&lt;/name&gt;
+  &lt;uuid&gt;4a9b3f53-fa2a-47f3-a757-dd87720d9d1d&lt;/uuid&gt;
+  &lt;memory unit='KiB'&gt;4194304&lt;/memory&gt;
+  &lt;currentMemory unit='KiB'&gt;4194304&lt;/currentMemory&gt;
+  &lt;memoryBacking&gt;
+    &lt;hugepages&gt;
+      &lt;page size='1' unit='G' nodeset='0'/&gt;
+    &lt;/hugepages&gt;
+  &lt;/memoryBacking&gt;
+  &lt;vcpu placement='static'&gt;2&lt;/vcpu&gt;
+  &lt;cputune&gt;
+    &lt;shares&gt;4096&lt;/shares&gt;
+    &lt;vcpupin vcpu='0' cpuset='4'/&gt;
+    &lt;vcpupin vcpu='1' cpuset='5'/&gt;
+    &lt;emulatorpin cpuset='4,5'/&gt;
+  &lt;/cputune&gt;
+  &lt;os&gt;
+    &lt;type arch='x86_64' machine='q35'&gt;hvm&lt;/type&gt;
+    &lt;kernel&gt;/mnt/qemu/bzImage&lt;/kernel&gt;
+    &lt;cmdline&gt;root=/dev/vda console=ttyS0,115200&lt;/cmdline&gt;
+    &lt;boot dev='hd'/&gt;
+  &lt;/os&gt;
+  &lt;features&gt;
+    &lt;acpi/&gt;
+    &lt;apic/&gt;
+  &lt;/features&gt;
+  &lt;cpu mode='host-model'&gt;
+    &lt;model fallback='allow'/&gt;
+    &lt;topology sockets='2' cores='1' threads='1'/&gt;
+    &lt;numa&gt;
+      &lt;cell id='0' cpus='0-1' memory='4194304' unit='KiB' memAccess='shared'/&gt;
+    &lt;/numa&gt;
+  &lt;/cpu&gt;
+  &lt;on_poweroff&gt;destroy&lt;/on_poweroff&gt;
+  &lt;on_reboot&gt;restart&lt;/on_reboot&gt;
+  &lt;on_crash&gt;destroy&lt;/on_crash&gt;
+  &lt;devices&gt;
+    &lt;emulator&gt;/usr/bin/qemu-system-x86_64&lt;/emulator&gt;
+    &lt;disk type='file' device='disk'&gt;
+      &lt;driver name='qemu' type='raw' cache='none'/&gt;
+      &lt;source file='/mnt/qemu/enea-nfv-access-guest-qemux86-64.ext4'/&gt;
+      &lt;target dev='vda' bus='virtio'/&gt;
+    &lt;/disk&gt;
+    &lt;interface type='bridge'&gt;
+      &lt;mac address='52:54:00:71:b1:b6'/&gt;
+      &lt;source bridge='ovsbr0'/&gt;
+      &lt;virtualport type='openvswitch'/&gt;
+      &lt;address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/&gt;
+    &lt;/interface&gt;
+    &lt;serial type='pty'&gt;
+      &lt;target port='0'/&gt;
+    &lt;/serial&gt;
+    &lt;console type='pty'&gt;
+      &lt;target type='serial' port='0'/&gt;
+    &lt;/console&gt;
+  &lt;/devices&gt;
+&lt;/domain&gt;</programlisting>
+      </section>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.png b/doc/book-enea-nfv-access-guide-intel/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.png
new file mode 100644
index 0000000..c28d643
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.png
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg b/doc/book-enea-nfv-access-guide-intel/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg
new file mode 100644
index 0000000..319bf7e
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg
@@ -0,0 +1,3 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
+<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" preserveAspectRatio="xMidYMid meet" viewBox="0 0 640 640" width="640" height="640"><defs><path d="M0 93L640 93L640 547L0 547L0 93Z" id="b4lgbdl3I5"></path><clipPath id="clipbKzvApRlV"><use xlink:href="#b4lgbdl3I5" opacity="1"></use></clipPath></defs><g><g><g><g clip-path="url(#clipbKzvApRlV)" opacity="1"><image xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAoAAAAHGCAYAAADkJDrPAAAABmJLR0QA/wD/AP+gvaeTAAAACXBIWXMAAA3XAAAN1wFCKJt4AAAAB3RJTUUH4QsPCjUWZQ2x8QAAGJBJREFUeNrt3UtypDoCBdB0R63DK/CCvBKPalijWol36R5ldz4e6IM+SOiciI5+ZTsFSEJcxCffPh7vPw8AAJbxH1UAACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIDATH5//112u7fb/vz3qnWyep+Aq/xSBcx8kPjz+fWP373+e/uz2O9rLH8rd/1Cn6dt/8ktY++zqf0zt9/lrt/Zskvrp0b99ugDpevVsv1AAISEQXf7s94H1u3PSgNm6ednccU21ToBOApxOeX/+fwKBslR96/W9TvjSQQIgMAtAvRRUHv+7evf7JUXC3qlM2ih5fesv+e6pK7D9u+OPne2fl9/d1THV87QpQbEo+1PneEPfT5UPzknmEIgAiBcbO+g2nPW4U6zG2dmWM9cYj86gJYu/+q2qlF+Sf3GLi+nfn6kPlgyQ5tbP6vt7yAAQuUDWMkBY/R7qHLXp/b61yqv9eXXs+W3bO8z97rm3r5QOjNWuv0CGgiALBS0rpgFPFp+6SxDy3uotvUSu/yWu74j3td21Hat+0brYNny86H1j52glPYnQACEpOBx1QEmtvzel6Jrb1etehlt+2cOf6X1mRL4Y+tvhg3uw3sAuW1ANPtwbf2P1gazh7/Z6wcQAKHaAWvk5Y8YQp/rlHqwz1n/uwTuvZc177Vni8CUW4cldd66vWL1c/Qg0EjrD3fmEjDT2HvFQ2iQTvn7kpvccwNeyvKvfAikdv3Etm97mbh0+WcP6me3MeU1NjX6WG77HK1jSv8tXf+Ue3Nj25O6/WdPsGrVzwz3u0LI28fj/Uc1AACswyVgAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEABAAAQAQAAEAEAABABAAAQAQAAEAEAABABAAAQAQAAEAEAABABAAAQAoMSvFoX+/v6rZgEATvjz+dV8GWYAAQAW86tl4T0SLADAHfS8gmoGEABgMQIgAIAACACAAAgAgAAIAIAACADABH71WpCXQwMA/NNVr8wzAwgAsBgBEABAABzX5+enFiuoi571p60wVgCM69dIK/P5+fn4/v6O/uyK9Zjt4Ndi/Wevl71gcHZ7juqiRvnPMko+u7f8o1A0e5sCMHkAJN3oB+0R16/WCcZRkKpR/uvfl3z26Ge122XUkwKhFiDsskvAJZdoPj8///e/WJmvP3v+d+jz27/JKb9VnYTWM2f9Y/VXcztCdVXafq3q/+rAsxfWRruUGes7r78/at9QGaWfz+n7LhMDK+s6Axi6bJZ6UN3+beksyeu/z8689A4aR8EgZf1L6y919iV1lqxnXddYTqiMq/tM6+XH2i5lBjL079LPx/rfKLeYACwXAJ8Dc0kAKB2sVx/sZw4p2/5z9uD9Gg5a3St5ZX2Hll/rHsir+l+LkxUAAbBjCHT2TWn/Odt3esyAtio/JcDFZri35YUeFKl1f2Srzxs/ACYJgM8Dzvb/gesDT+wSd2x20ww9wBy6PgSSc78OhPrQmX7Tup9d3Y97Lf9Z/wAIgEVn97kPcYx+wPeEYZv67fWUbOv2Oyp/uz2tLx+Xrn9Keb0vCc8W2gGuctl7AI8uH8XuQQpdhtr73ZkB/ug+s9Tyay13bx32XosSqqMW730LtWXK+qVsf4uAl9K/crZ/u301yi9pu9jyS9cv9hRtafkztA/AXbx9PN5/ahf6+/vv4/F4PP58fv3rZ6twbyMr9Gn9HKDMXlZ6/VkrvglE+IMkZtAA7qNbAOyRZkfx8Xhfant5LNW3V92vAe7kP6oAAEAABABAABzDag+S1K6LnvWnrbj7WKGPz9fO2gz+79doO/P2nqK9n12xHrMNii3Wf/Z62TsAnN2eo7qoUX7JU2Ch5R8d/NzHt+a+sKI/n1/aDkYMgOQNZNbvmhOMoyBVo/zXvy/57NHParfLqAdTB3iAGwbA1wPwdoYjdAB8/nfo89v/zim/1cF0+/OjGaLY+sfqr3b7HNVVaftdGUD2tqFVmBpxtiLWd2IzkKH2r/H5nL5/tv/H9tOz21f6+5T9o6R+S/e/bbkp74sNbf/Z9jULCJMGwL0BrWSW5PXfZ2deemzn3gB2NOsR+mxp/aXOvqTOkvWs6xrLCZVxdZ9pvfxY26UGkKN/l34+1v96nECUbF/rE6Ba9Vujjx6dmOds/7aNR7mFCATAQQ9yqw8GM4eU7UHi7ODeawb0qvoumYFabf9drbw7jY+tZuJBAITBB/2zB6seM6Ctyk+9xLW3/JzbC84GgtIDcu7nZ7sXtmVgSTlBulv91u5/IAACUwSKnuWn3H9nhn7s7VO/wJMXQTPdGf6fz69Tl39azw5cPfvQa/nP+me9k4+9B80AAXC4g9xVB/zf338Njg3q9+gp2RbLbdl+R+XvHWBbXj4uXf+U8npfEu5Rfs1+FyvnzCXbZ9uk9J3W5V/ddqkPA8GKhroEvDewxp7wCwWCswP10X1mqeXXWm7sNQlH98LVuE8uZ0DNXb/U9q8d8FL6V872b7evRvklbRdbfun6xZ6yLC1/hvZp2f9at1+t7W9VZ7nbnzJeCHpw7O3j8f7T6sxs5Z3PWSYr9OmV+7l9fL460GbM0Ed75ScPgRhkIIkZlsfy2z57+xuXQQA0yIC+jfaHZXkKGABAAAQAQAAchFerlNVFz/rTVhgrAMY11D2AozxlOPtDHK3W/w4Pt9S6if2oLmqUX/IUWGz5HuIAYLgASLrZvgP1TicYoReAl5Yf+y7Xku1rcYI16kmBYAsQNuU9gEffRHD01vftf4c+v/2bnPJrbFfKz4++hSG2/rH6q90+R9tR2n6t6v/qwNPrm05a7Ht7vz9q31AZpZ/P6fsuEwMrm24GcHuQLJ0l2X6TwSizGqF1CH0DSeyzpfWXOvuSOkvWs65rLCdUxtV9Jrb80vWLtV3KDGPo36Wfj/U/L7IGmDgAlg7Wqw/2o4eUlGBZGtSPvkqwZni/sr5Tln/Vt/WMtv8Kf4AACJME2NLw0mMGtFX5KQ9x5M7K5Zafs36l2yfAAQiAIABXvoybU/720mosfF6xfQCk8SJopvIMMGcekGh90//VDxXEll9rNvJZ/wAIgMMc5EY44HvCsE399npKtnX7HZW/3Z5RH1DIeYq29yXh2UI7wFWGugS8d0CPPeEXCgRnA8LRfWap5dda7t467L0WJVRHtQNE6Onj1PVLbf/aAS+lf+Vs/3b7apRf0nYpy4+1X2zbQ/cTlm7/DO0DcBdvH4/3n1Zn1SsPrl4vwQp9Wj8HmDM/eQhE+IMkZtAA7kMAbHSgBH0bgFF5ChgAQAAEAEAAHIRXNpTVRc/601bcfazQx+drZ20G//drtJ15hKcMZ3+Io9X63+HhlloPMRzVRY3yS54Cy30NjHv61t0XVrT9PnEQAJlyILN+15xghF4AXlr+69+XfDa1vNKD4agHUwd4gBsGwKMXQaceAEOf3/53TvmtZhW2Pz+aIUp9CXPs+1xrtc9RXZW235UBZG8bWgXUEWcrYn0nNMMYa/8an8/p+2f7f2w/Pbt9pb9P2T9K6rd0/zt6yXvq+pX2v5H3KxAATwy+pbMk228yGGVWI7QOoW8giX22tP5SZ19SZ8l61nWt78EdddYptvzS9Yu1XWoAOfp36edj/a/HCUTJ9rU+AapVvzX66NGJec72x74qcpSxHATAQQ7iqw8Go4eUlGBZGtR7zYBeVd8py7/q23pG239XK+9O42OrmXgQAGHwQf/swarHDGir8lMvcYWWH5shLgkEpQfk3M/Pdi9sy8CScoJ0t/qt3f9AAASmCBRnDpBnL2On3H9nhn7s7VO/wJMXQTPdGf6fz69Tl39azw5cPfsQW36t2chn/bPeycfeg2aAADjEQW6EA/7v778Gxwb1e/SUbIvltmy/o/L3DrCjvk4ntY56XxLuUX7NfpcS2s+sW2rfaV3+1W2X+jAQrGioS8B7A2vsCb9QIDg7UB/dZ5Zafq3lxl6TcHQvXI375HIG1Nz1S23/2gEvpX/lbP92+2qUX9J2KcuPtV9s20P3E5Zu/wzt07L/lf6+R/22rLPc7U8ZLwQ9OPb28Xj/aXVmtvLO5yyTFfr0yv3cPj5fHWgzZuijvfKTh0AMMpDEDMtj+W2fvf2NyyAAGmRA30b7w7I8BQwAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACAAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAIACqAgAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAQAAEAEAABABAAAQAQAAEAEAABABgXL9aFv77+68aBgAYjBlAAIDFvH083n9UAwDAOswAAgAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIOz6/f1XJQCAAAgAgADIITNoACAAslAoey5nhBAoiDJiXzvTL/XltnUxU/vN0n/0WQFw6UFptZ3u9/ffx5/Pr8fj8Xj8+fxaagCYZVtHX8/f33+brqODkvpbuf9rXwRAmniGv6N/Q24fso2MVn+pyz8TplLKbrl8qOWXKgjvkNsdOfb71LKf/733+de/q7n81vXznF1MXf+rDxKvs6E52xcqo3X/KG3/lv27tPzU/SOnPWNtFNr/Yvvmmf235f4Vq7+Uz8f6d842nK2/nDoqab+jZZeOUa2WX2N8GGn8RQAcLvyFBsDSATJUTuhgVWv5resnd/1HuRRe6wDYun+0Xr+ry0/ZP1qEwb1Z8aPbRUr6f+v9q3R8qTn7drb+cuuopP3O1HfN7c9dfun4MNL4yxhcAk48KN91ebXXLWf9r9rWnqF59LPsWS7Vjbq83rdUlJY/Wn88E67sD2uMTbRnBvDgzC1lev6q8LLy8luHv5LtS+k/d+/fZhXm2r96B46R9w/9BwFQCPzHjjTaQxNXLj/lnrlZQv5RPdaaYRn1QNe6fzuwP9TfoPtH7P7kOyzf/kcOl4ADO9Jqr0mZ8Qz37FN8NT4XKmP0/qN/U9K/Z+5/z2Vfve+BADhwuGj1mavXeZRll4awknv5Ug8+e0/VPd8DNtts6BX9O/b5O9xScKf9O9S/Zx6rtutx5bv8ei4/tIyj3139nkP6WeoS8N5B/3WQK/39mfXIfWjiytfA7F3CyBkoSj+//VyNy5WxF2PvLSN0+bhl/ygtv0b/Dr2Kotb+U2P/OFtGyfa1Hp9ajy81tunK+ostv9ZTyEfl91h+yfhQa/zlPt4+Hu8/qmE9PZ+EVY+gf4+4LaO9Rgt68hAInJxhaDGDAfp3G6NdQTF+cDUzgAAAi/EQCMAg3JMFCIAAi6l1Y74gCQiALMMrRbhDnXo6M95+V9SPNlFnAuDknXH7PzulQaH3+t9h+1tuw9XvtgyND73Gj6u/8cf+Cfe33FPAHsOH8n3ojgfJ2Gs6vMZj3HEcEACrHABC39eY86LcM7/PPTvdvoQ0tP6xl5iWlp+z7meWf2Y5NdsnZf1Lt790/Uv6z9Xl1+gfV37Xa68xKqV9SvebVvtnjfZLWbcV98+jlzxvv3/56Pc1xv9Y+3kNjgA41SxAzgxA6xmElM+H/h1ajxrlp561lyz/yvaLrX/p9peu/9UzXK3rN7f8HrOUPQ9grWcgW++ftdrvaAba/rm/DbF97DXYlYz/sfYzgz6e5R4C2d7Ds+18tTtjrLzey5vpgHfH9Rtt/a+ur5bLb7Fv+Z7UtfflO++fKcvK/WrGu4/Xs1v+HsDcvw8N/rHv4Cz9js4esxq55duB+5/AlAaYULuNfgP91eFrezmtd//3pLvtm3X9axz/EACHDpCxA0TpAWT1GT7976vK52P9c9T+M0r/LL3cuOr+effxZebtO7pEe6cTKP7JewAbDgShpyVjv4cr+yf7B0jA+CMA8q+DQqwzt+jsd7/k5iBdb3vP1E3rS8Ity7+qL/S8T/DOlxzvsC/P/E7C2usu7I3HJeDMs5bQY+ylvy9d/plyaq7fCMsPvaagVvuU3sty9vOt+09K+aFXZbSu39zyc2cYWqx/z/Fn9P2zRvulvKpl5f2zZv8q3X9SynMJ+FpvH4/3H9UAUHf2xMENGJlLwADCH7AYM4AAAIsxAwgZ3MgMgAAIi6l1g78gCYAA2EnNg+6IXwk10vrcOeCM8P4qX0l2736ubbHf0JrXwJzsvCvf5O0m92tfX6D+73Hwm60NQy+1P/qb2DdLnKmD0fu//RMBEAHJYAq7+0ZsBmTUPh9ar6OvEgt9bZ792/EBAfCyM9naZ6ihzz8Hu5bLL92+2PqnzGIc/S53+0u3/Uz9154lOSq/1QDYevtb7h85/W/vZb2x39feP1u3Yen+c7cDbcr4U7L9pfUbW7/UgHy0/NL9t0b5KftPyklB7NhxtnwvmhYAs2aUcs5QS3fw0uX32L7Q70N/lzrDkbN+pdueW/+1+1aL8lv2v9bbV2OGaO9vY3309cBWc/9sdR9Trf1nhBm22LJzvykjtE1Xj5+p4+PZ5bcYI3sfn0L9u/X4ggBY1Blq7OCtO+Ponf3q9eu9/Npf1XRl/2v1tWMjtUXpV3fdff9J/aqyWQ+6o49PpevXunztKQBO7eoB3dNRBoiRt3/2/tl6/a++BNV6+1IDxOxBcJTxebRAGtr+7Sx779m3O5yACIDOAJeu+x73WHE+XMx8wtJj/Y0f/w6Cd9qPnTDOcYVJEEzjRdAMuRPbcWG+E4Qen4HUY4j+JQAWDTgjvPB3tQH1+ZLju2yLfWnM+ild9gxte3SzvQPj9X3oijaovcy9Wx6e/av1Sfx22fp0viUfAjm6zLh3xlB6U3jPz5duX+ryQ/dapL4q5miHLnmKq0b91exbd1v+Xt/KGXRr9b9R1v/MDEPKk9xn958e/W9ve1+fgu3RvkfjT+/+kzs+1ug/LY9/PfpXqH/n9p+U+nQlKezt4/H+oxoY5WzaY/wAfcZX1uYhEIbhDA4A+jADCACwGE8BAwAIgAAACIAAAAiAAAAIgAAATGCp18AcvTTy6EWse78LvUjTe+wAAAFwQHtfUv4a7GIBLvZvAIDRuQR8MkACAMzKN4Fs+EJpAEAAXIwZPgDg7lwCBgAQAHlVckn46LO/v/+61AwAXMYl4BfbV7w8f3b283vlAQBc7e3j8f6jGgAA1uESMACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAABd/Bd3tasDZYM0pAAAAABJRU5ErkJggg==" x="0" y="0" width="640" height="454" transform="matrix(1 0 0 1 1.1368683772161603e-13 93.00000000000006)"></image></g></g></g></g></svg>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/images/virtual_network_functions.png b/doc/book-enea-nfv-access-guide-intel/doc/images/virtual_network_functions.png
new file mode 100644
index 0000000..4011de8
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/images/virtual_network_functions.png
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/overview.xml b/doc/book-enea-nfv-access-guide-intel/doc/overview.xml
new file mode 100644
index 0000000..961939c
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/overview.xml
@@ -0,0 +1,165 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="overview">
+  <title>Overview</title>
+
+  <para>The Enea NFV Access Guide available with this release of the Enea NFV
+  Access seeks to provide further information that will help all intended
+  users make the most out of the virtualization features.</para>
+
+  <section id="description">
+    <title>Enea NFV Access Description</title>
+
+    <para>Enea NFV Access is a lightweight virtualization software designed
+    for deployment on edge devices at customer premises. Streamlined for high
+    networking performance and minimal footprints for both host platform and
+    VNFs, it enables very high compute density.</para>
+
+    <para>Enea NFV Access also provides a foundation for vCPE agility and
+    innovation, reducing cost and complexity for computing at the network
+    edge. It supports multiple architectures and scales from small white box
+    edge devices up to high-end network servers. Thanks to the streamlined
+    footprint, Enea NFV Access can be deployed on systems as small as single
+    2-core ARM devices. It scales up to clustered 24 core x86 Xeon servers and
+    beyond, allowing multiple VNFs on the same machine, and eliminating the
+    need to use different virtualization software for different hardware
+    platforms, saving costs through single source provisioning.</para>
+
+    <para>Optimized virtual networking performance provides low virtualized
+    networking latency, high virtualized networking throughput (10 Gb wire
+    speed), and low processing overhead. It allows high compute density on
+    white box hardware, maintaining performance when moving functionality from
+    application specific appliances to software on standard hardware. The
+    optimized boot speed minimizes the time from reboot to active services,
+    improving availability.</para>
+
+    <para>Enea NFV Access provides virtualization using both containers and
+    virtual machines. Containers provide lightweight virtualization for a
+    smaller VNF footprint and a very short time interval from start to enabled
+    network services. VMs provide virtualization with secure VNF sandboxing
+    and is the preferred virtualization method for OPNFV compliance. Enea NFV
+    Access allows combinations of containers and VMs for highest possible user
+    adaptability.</para>
+
+    <para>Flexible interfaces for VNF lifecycle management and service
+    function chaining, are important to allow a smooth transition from
+    traditional network appliances to virtualized network functions in
+    existing networks, as they plug into a variety of interfaces. Enea NFV
+    Access supports VNF lifecycle management and service function chaining
+    through OpenStack, NETCONF, REST, CLI and Docker. It integrates a powerful
+    device management framework that enables full FCAPS functionality for
+    powerful management of the platform.</para>
+
+    <para>Building on open source, Enea NFV Access prevents vendor lock-in
+    thanks to its completely open standards and interfaces. Unlike proprietary
+    platforms that either do not allow decoupling of software from hardware,
+    or prevent NVF portability, Enea NFV Access includes optimized components
+    with open interfaces to allow full portability and
+    interoperability.</para>
+  </section>
+
+  <section id="components">
+    <title>Components</title>
+
+    <para>Enea NFV Access is built on highly optimized open source and
+    value-adding components that provide standard interfaces but with boosted
+    performance.</para>
+
+    <mediaobject>
+      <imageobject>
+        <imagedata align="center"
+                   fileref="images/virtual_network_functions.png" />
+      </imageobject>
+    </mediaobject>
+
+    <para>The Access Platform includes the following key components:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Linux Kernel &ndash; Optimized Linux kernel with the focus on
+        vCPE systems characteristics.</para>
+      </listitem>
+
+      <listitem>
+        <para>KVM &ndash; Virtualization with virtual machines. KVM is the
+        standard virtualization engine for Linux based systems.</para>
+      </listitem>
+
+      <listitem>
+        <para>Docker &ndash; Docker provides a lightweight configuration using
+        containers. Docker is the standard platform for container
+        virtualization.</para>
+      </listitem>
+
+      <listitem>
+        <para>Virtual switching &ndash; Optimized OVS-DPDK provides high
+        throughput and low latency.</para>
+      </listitem>
+
+      <listitem>
+        <para>Edge Link &ndash; Edge Link provides interfaces to orchestration
+        for centralized VNF lifecycle management and service function
+        chaining:</para>
+
+        <orderedlist>
+          <listitem>
+            <para>NETCONF</para>
+          </listitem>
+
+          <listitem>
+            <para>OpenStack</para>
+          </listitem>
+
+          <listitem>
+            <para>Docker</para>
+          </listitem>
+
+          <listitem>
+            <para>REST</para>
+          </listitem>
+
+          <listitem>
+            <para>CLI</para>
+          </listitem>
+        </orderedlist>
+      </listitem>
+
+      <listitem>
+        <para>APT packet management &ndash; Feature rich repository of
+        prebuilt open source packages for extending and adapting the platform
+        using APT Package Management.</para>
+      </listitem>
+
+      <listitem>
+        <para>CLI based VNF management &ndash; CLI access over virsh and
+        libvirt.</para>
+      </listitem>
+
+      <listitem>
+        <para>FCAPS framework &ndash; The device management framework for
+        managing the platform is capable of providing full FCAPS functionality
+        to orchestration or network management systems.</para>
+      </listitem>
+
+      <listitem>
+        <para>Data plane &ndash; High performance data plane that includes the
+        following optimized data plane drivers:</para>
+
+        <orderedlist>
+          <listitem>
+            <para>DPDK</para>
+          </listitem>
+
+          <listitem>
+            <para>OpenFastPath (OFP)</para>
+          </listitem>
+
+          <listitem>
+            <para>ODP</para>
+          </listitem>
+        </orderedlist>
+      </listitem>
+    </itemizedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/ovs.xml b/doc/book-enea-nfv-access-guide-intel/doc/ovs.xml
new file mode 100644
index 0000000..fdbd692
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/ovs.xml
@@ -0,0 +1,161 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="ovs">
+  <title>Open Virtual Switch</title>
+
+  <para>Open vSwitch (OVS) is an open-source multilayer virtual switch
+  designed to be used in virtualized environments to forward traffic between
+  different VMs on the same host, and also between VMs and the physical
+  network.</para>
+
+  <para>Native OVS forwarding is handled by two major components: a user-space
+  daemon called <literal>ovs-vswitchd</literal> and a
+  <literal>fastpath</literal> kernel module used to accelerate the data path.
+  The fastpath kernel module will handle packets received on the NIC by simply
+  consulting a flow table with corresponding action rules (e.g to forward the
+  packet or modify its headers). If no matching entry is found in the flow
+  table, the packet is copied to the user-space and sent to the ovs-vswitchd
+  deamon which determines how it should be handled ("slowpath").</para>
+
+  <para>The packet is then passed back to the kernel module together with the
+  desired action and the flow table is updated, so that subsequent packets in
+  the same flow can be handled in fastpath without any user-space interaction.
+  In this way, OVS eliminates a lot of the context switching between
+  kernel-space and user-space, but the throughput is still limited by the
+  capacity of the Linux kernel stack.</para>
+
+  <section id="ovs-dpdk">
+    <title>OVS-DPDK</title>
+
+    <para>To improve performance, OVS supports integration with Intel DPDK
+    libraries to operate entirely in user-space (OVS-DPDK). DPDK Poll Mode
+    Drivers (PMDs) enable direct transfers of packets between the physical NIC
+    and user-space, thereby eliminating the overhead of interrupt handling and
+    Linux kernel network stack processing. OVS-DPDK provides DPDK-backed
+    vhost-user ports as the primary way to connect guests to this datapath.
+    The vhost-user interfaces are transparent to the guest.</para>
+  </section>
+
+  <section id="ovs-commands">
+    <title>OVS commands</title>
+
+    <para>OVS provides a rich set of command line management tools, most
+    importantly:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>ovs-vsctl: Used to manage and inspect switch configurations,
+        e.g. to create bridges and to add/remove ports.</para>
+      </listitem>
+
+      <listitem>
+        <para>ovs-ofctl: Used to configure and monitor flows.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>For more information about Open vSwitch, see <ulink
+    url="http://openvswitch.org">http://openvswitch.org</ulink>.</para>
+  </section>
+
+  <section id="config-ovs-dpdk">
+    <title>Configuring OVS-DPDK for improved performance</title>
+
+    <section id="dpdk-lcore-mask">
+      <title>dpdk-lcore-mask</title>
+
+      <para>Specifies the CPU core affinity for DPDK lcore threads. The lcore
+      threads are used for DPDK library tasks. For performance it is best to
+      set this to a single core on the system, and it should not overlap the
+      pmd-cpu-mask, as seen in the example below.</para>
+
+      <para>Example: To use core 1:</para>
+
+      <programlisting>ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x1</programlisting>
+    </section>
+
+    <section id="pmd-cpu-mask">
+      <title>pmd-cpu-mask</title>
+
+      <para>The DPDK PMD threads polling for incoming packets are CPU bound
+      and should be pinned to isolated cores for optimal performance.</para>
+
+      <para>If OVS-DPDK receives traffic on multiple ports, for example when
+      DPDK and vhost-user ports are used for bi-directional traffic, the
+      performance can be significantly improved by creating multiple PMD
+      threads and affinitizing them to separate cores in order to share the
+      workload, by each being responsible for an individual port. The cores
+      should not be hyperthreads on the same CPU.</para>
+
+      <para>The PMD core affinity is specified by setting an appropriate core
+      mask. Example: using cores 2 and 3:</para>
+
+      <programlisting>ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0xc</programlisting>
+    </section>
+  </section>
+
+  <section id="setup-ovs-dpdk">
+    <title>How to set up OVS-DPDK</title>
+
+    <para>The DPDK must be configured prior to setting up OVS-DPDK. See
+     <xref linkend="dpdk-setup"/> for DPDK setup instructions, then follow these steps:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Clean up the environment:</para>
+
+        <programlisting>killall ovsdb-server ovs-vswitchd
+rm -f /var/run/openvswitch/vhost-user*
+rm -f /etc/openvswitch/conf.db</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Start the ovsdb-server:</para>
+
+        <programlisting>export DB_SOCK=/var/run/openvswitch/db.sock
+ovsdb-tool create /etc/openvswitch/conf.db /usr/share/openvswitch/vswitch.ovsschema
+ovsdb-server --remote=punix:$DB_SOCK /
+--remote=db:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Start ovs-vswitchd with DPDK support enabled:</para>
+
+        <programlisting>ovs-vsctl --no-wait init
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x1
+ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0xc
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
+ovs-vswitchd unix:$DB_SOCK --pidfile --detach /
+--log-file=/var/log/openvswitch/ovs-vswitchd.log</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Create the OVS bridge and attach ports:</para>
+
+        <programlisting>ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=netdev
+ovs-vsctl add-port ovsbr0 dpdk0 -- set Interface dpdk0 type=dpdk /
+:dpdk-devargs=&lt;PCI device&gt;</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Add DPDK vhost-user ports:</para>
+
+        <programlisting>ovs-vsctl add-port ovsbr0 vhost-user1 -- set Interface vhost-user1 type=dpdkvhostuser</programlisting>
+
+        <para>This command creates a socket at
+        <literal>/var/run/openvswitch/vhost-user1</literal>, which can be
+        provided to the VM on the QEMU command line. See <xref linkend="net_in_guest"/> for
+        details.</para>
+      </listitem>
+
+      <listitem>
+        <para>Define flows:</para>
+
+        <programlisting>ovs-ofctl del-flows ovsbr0
+ovs-ofctl show ovsbr0
+ovs-ofctl add-flow ovsbr0 in_port=1,action=output:2
+ovs-ofctl add-flow ovsbr0 in_port=2,action=output:1</programlisting>
+      </listitem>
+    </orderedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml b/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml
new file mode 100644
index 0000000..4b10d2a
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/doc/using_nfv_access_sdks.xml
@@ -0,0 +1,472 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="workflow">
+  <title>Using Enea NFV Access SDKs</title>
+
+  <para>Enea NFV Access comes with a standard SDK which can be used to develop
+  user-applications and kernel modules for both host and guest images.</para>
+
+  <para>The standard SDK consists of:</para>
+
+  <itemizedlist>
+    <listitem>
+      <para>Cross-Development Toolchain: cross-compiler and
+      cross-debugger</para>
+    </listitem>
+
+    <listitem>
+      <para>Libraries, Headers and Symbols that are specific to the
+      image</para>
+    </listitem>
+
+    <listitem>
+      <para>Environment Setup Script which defines the environment
+      variables</para>
+    </listitem>
+  </itemizedlist>
+
+  <para>To install the SDK on your host development machine, there is an
+  installation script available under the Download section on <emphasis
+  role="bold">portal.enea.com</emphasis>:</para>
+
+  <itemizedlist>
+    <listitem>
+      <para>x86_64/install/install-sdk.sh</para>
+    </listitem>
+  </itemizedlist>
+
+  <para>After installing the SDK, a developer will be able to compile and
+  generate executables for the preferred target machine. Cross-gdb
+  (<filename>x86_64-enea-linux-gdb</filename>) is created by the
+  Cross-Development toolchain. It can be used to debug applications on the
+  target platform from the development workstation. For kernel debugging,
+  <command>ftrace</command> and <command>kgdb</command> are enabled on the
+  host sdk image.</para>
+
+  <para>Various user-space tools helpful in the development process, are also
+  provided. The tools include <emphasis role="bold">LatencyTop</emphasis>,
+  <emphasis role="bold">Perf</emphasis>, <emphasis
+  role="bold">CrossTap</emphasis>, <emphasis role="bold">OProfile</emphasis>,
+  <emphasis role="bold">Lttng-ust</emphasis> and <emphasis
+  role="bold">GDBserver</emphasis>.</para>
+
+  <section id="install-crosscomp">
+    <title>Installing the Cross-Compilation Toolchain</title>
+
+    <para>Before cross-compiling applications for your target, you need to
+    install the corresponding toolchain on your workstation. To do that,
+    simply run the installer and follow the steps included with it:</para>
+
+    <orderedlist>
+      <listitem>
+        <para><programlisting>$ ./install-sdk.sh</programlisting>When
+        prompted, select to install the toolchain in the desired directory,
+        referred to as <literal>sdkdir</literal>.</para>
+
+        <para>A default path where the toolchain will be installed will be
+        shown in the prompt. The installer unpacks the environment setup
+        script in <literal>sdkdir</literal> and the toolchain under
+        <literal>sdkdir/sysroots</literal>.</para>
+
+        <note>
+          <para>Choose a unique directory for each toolchain. Installing a
+          second toolchain of any type in the same directory as a previously
+          installed one will break the <literal>$PATH</literal> variable of
+          the first one.</para>
+        </note>
+      </listitem>
+
+      <listitem>
+        <para>Setup the toolchain environment for your target by sourcing the
+        environment-setup script. Example: <programlisting>$ source sdkdir/environment-setup-corei7-64-enea-linux</programlisting></para>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="crosscomp-apps">
+    <title>Cross-Compiling Applications from Command Line</title>
+
+    <para>Once the environment-setup script is sourced, you can make your
+    applications as per usual and get them compiled for your target. Below you
+    see how to cross-compile from command line.</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Create a Makefile for your application. Example: a simple
+        Makefile and application:</para>
+
+        <programlisting>helloworld:helloworld.o
+        $(CC) -o helloworld helloworld.o
+clean:
+        rm -f *.o helloworld
+#include stdio.h;
+int main(void) {
+        printf("Hello World\n");
+        return 0;
+}</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Run <command>make</command> to cross-compile your application
+        according to the environment set up:</para>
+
+        <programlisting>$ make</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Deploy the helloworld program to your target and run it:</para>
+
+        <programlisting># ./helloworld
+hello world</programlisting>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="crosscomp-kern-mod">
+    <title>Cross-Compiling Kernel Modules</title>
+
+    <para>Before cross-compiling kernle modules, you need to make sure the
+    installed toolchain includes the kernel source tree, which should be
+    available at:
+    <literal>sdkdir/sysroots/targetarch-enea-linux/usr/src/kernel</literal>.</para>
+
+    <para>Once the environment-setup script is sourced, you can make your
+    kernel modules as usual and get them compiled for your target. Below you
+    see how to cross-compile a kernel module.</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Create a Makefile for the kernel module. Example: a simple
+        Makefile and kernel module:</para>
+
+        <programlisting>obj-m := hello.o
+PWD := $(shell pwd)
+
+KERNEL_SRC := full path to kernel source tree
+
+all: scripts
+    $(MAKE) -C $(KERNEL_SRC) M=$(PWD) LDFLAGS="" modules
+scripts:
+    $(MAKE) -C $(KERNEL_SRC) scripts
+clean:
+    $(MAKE) -C $(KERNEL_SRC) M=$(PWD) LDFLAGS="" clean
+#include linux/module.h     /* Needed by all modules */
+#include linux/kernel.h     /* Needed for KERN_INFO */
+#include linux/init.h       /* Needed for the macros */
+
+static int __init hello_start(void)
+{
+    printk(KERN_INFO "Loading hello module...\n");
+    printk(KERN_INFO "Hello, world\n");
+    return 0;
+}
+
+static void __exit hello_end(void)
+{
+    printk(KERN_INFO "Goodbye, world\n");
+}
+
+module_init(hello_start);
+module_exit(hello_end);
+
+MODULE_LICENSE("GPL");</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Run <command>make</command> to cross-compile your kernel module
+        according to the environment set up:</para>
+
+        <programlisting>$ make</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Deploy the kernel module <literal>hello.ko</literal> to your
+        target and install/remove it:</para>
+
+        <programlisting># insmod hello.ko
+# rmmod hello.ko
+# dmesg
+[...] Loading hello module...
+[...] Hello, world
+[...] Goodbye, world</programlisting>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="deploy-artifacts">
+    <title>Deploying your artifacts</title>
+
+    <section id="deploy_onhost">
+      <title>Deploying on host</title>
+
+      <para>You can use <literal>ssh</literal> to deploy your artifacts on the
+      host target. For this you will need a network connection to the target,
+      to use <literal>scp</literal> to copy to the desired location.</para>
+
+      <para><programlisting># scp helloworld root@&lt;target_ip_address&gt;:/tmp</programlisting></para>
+    </section>
+
+    <section id="deploy_onguest">
+      <title>Deploying on guest</title>
+
+      <para>You can deploy your artifacts onto the guest VM running on the
+      target, by using TAP Networking. You can use the
+      <filename>/etc/qemu-ifup</filename> script to create the tap interface
+      on the host and attach it to the existing virtual bridge
+      (<literal>virbr0</literal>). This bridge interface is created by the
+      <filename>libvirt</filename> library and can be used to connect to the
+      outside network. To be able to transfer files to the guest via
+      <literal>scp</literal>, port forwarding should be enabled on the host.
+      The script sets iptables rules to forward traffic from a host port to
+      the guest default SSH port (22).</para>
+
+      <para>Follow the steps below to create this setup:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>On the host, run the <literal>qemu-ifup</literal> script
+          located in <literal>/etc</literal> directory:</para>
+
+          <para><programlisting># /etc/qemu-ifup &ndash;t tap0 &ndash;a 192.168.122.10 &ndash;p 1050 &ndash;g 22</programlisting></para>
+
+          <itemizedlist>
+            <listitem>
+              <para><emphasis role="bold">tap0</emphasis> - the tap interface
+              name which will be created and added to the virtual bridge
+              (virbr0).</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">192.168.122.10</emphasis> - the IP
+              address of the guest virtual network device. It has to be in the
+              same network with the IP address of the virbr0 interface.</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">1050</emphasis> - the host port
+              which is set to forward traffic from the host to the
+              guest.</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">22</emphasis> - the default SSH
+              guest port used in port forwarding.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>Launch the virtual machine specifying the newly created tap
+          interface:</para>
+
+          <para><programlisting>-device e1000,netdev=net0 \
+-netdev tap,id=net0,ifname=tap0,script=no,downscript=no</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>On the guest, after logging, configure the virtual network
+          device and set the default gateway as the <literal>virbr0</literal>
+          ip address:</para>
+
+          <para><programlisting>ip addr add 192.168.122.10/24 dev enp0s2
+ip link set enp0s2 up
+ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Now you can use <literal>scp</literal> from your development
+          machine to deploy your artifacts on the guest, by giving the host
+          port for forwarding as a command parameter: <programlisting>scp -P 1050 helloworld root@target_ip_address:/tmp</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>On the host, after finishing the deployment session and
+          stopping the virtual machine, you can use the
+          <literal>qemu-ifdown</literal> script to clean up the configuration
+          on host. The following command will remove the tap interface and all
+          the iptables rules for the specific ip address: <programlisting># /etc/qemu-ifdown &ndash;t tap0 &ndash;a 192.168.122.10</programlisting>If
+          we need to remove only a particular port forwarding rule from
+          iptables, this should be run: <programlisting># /etc/qemu-ifdown &ndash;t tap0 &ndash;a 192.168.122.10 &ndash;p 1050 &ndash;g 22</programlisting></para>
+        </listitem>
+      </orderedlist>
+    </section>
+  </section>
+
+  <section id="crossdebugging">
+    <title>Cross-Debugging on Enea NFV Access</title>
+
+    <para>The cross-debugger (<literal>x86_64-enea-linux-gdb</literal>) is
+    created when installing the SDK on the development machine. It is helpful
+    for debugging both the kernel and user-applications. In order to perform
+    this task, we need the following tools to be available on the target
+    machine:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Kgdb &ndash; for kernel cross-debugging</para>
+      </listitem>
+
+      <listitem>
+        <para>GDBServer &ndash; for application cross-debugging</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>The Host Development image provides both of these tools and has to
+    be booted on the target machine for cross-debugging sessions.</para>
+
+    <section id="ua_debug_host">
+      <title>User-application Cross-Debugging on Host</title>
+
+      <para>To debug a user-application on host, a TCP connection has to be
+      established between the host and development machines. GDBserver is the
+      program which runs on the target machine and allows you to run GDB on
+      your workstation. Below you can find how a simple
+      <filename>helloworld</filename> application can be debugged using
+      GDBServer and cross-gdb.</para>
+
+      <para>On target, launch the GDBServer, specifying how to communicate
+      with GDB and the name of your program:<programlisting># gdbserver :&lt;port_no&gt; /tmp/helloworld</programlisting>The
+      target will now be listening on the port given as a parameter to the
+      gdbserver. On the development machine, from the
+      <literal>&lt;sdkdir&gt;</literal>, start the cross-gdb:<programlisting># x86_64-enea-linux-gdb &lt;path_to_the_program&gt;/helloworld</programlisting>Connect
+      the GDB to the target: <programlisting>(gdb) target remote &lt;target_ip_address&gt;:&lt;port_no&gt;</programlisting>Now
+      remote debugging is started and the GDB commands are available to debug
+      your program from the target machine.</para>
+    </section>
+
+    <section id="us_debug_guest">
+      <title>User-application Cross-Debugging on Guest</title>
+
+      <para>To debug a user-application on guest, a TCP connection has to be
+      established between the host and development machines. Similarly, as
+      when deploying artifacts on guest, for a cross-debugging session, TAP
+      Networking is required.</para>
+
+      <para>A tap interface should be added to the existing virtual bridge
+      (<literal>virbr0</literal>), along with port forwarding rules created in
+      iptables. In order to do this, the script
+      <filename>/etc/qemu-ifup</filename> can pe used:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>On the host, run the script <literal>qemu-ifup</literal>
+          located in <literal>/etc</literal> directory: <programlisting># /etc/qemu-ifup &ndash;t tap0 &ndash;a 192.168.122.10 &ndash;p 1051 &ndash;g 1025</programlisting></para>
+
+          <itemizedlist>
+            <listitem>
+              <para><emphasis role="bold">tap0</emphasis> - the tap interface
+              name which will be created and added to virtual bridge
+              (virbr0).</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">192.168.122.10</emphasis> - the IP
+              address of the guest virtual network device. It has to be in the
+              same network with the IP address of the virbr0 interface.</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">1051</emphasis> &ndash; the host
+              port which is set to forward traffic from the host to the guest
+              and is used by gdb target remote command.</para>
+            </listitem>
+
+            <listitem>
+              <para><emphasis role="bold">1025</emphasis>&ndash; the port used
+              by GDBServer on guest for listening.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>Launch the virtual machine, specifying the newly created tap
+          interface:<programlisting>-device e1000,netdev=net0 \
+-netdev tap,id=net0,ifname=tap0,script=no,downscript=no</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>On the guest, after logging, configure the virtual network
+          device and set the default gateway to virbr0 ip
+          address:<programlisting>ip addr add 192.168.122.10/24 dev enp0s2
+ip link set enp0s2 up
+ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>GDBserver is the program which runs on the guest VM and allows
+          you to run GDB on your workstation. On the guest, launch GBDserver
+          specifying how to communicate with GDB and the name of your program:
+          <programlisting># gdbserver :1025 /tmp/helloworld</programlisting>The
+          guest is now listening on port 1025, given as a parameter to the
+          gdbserver.</para>
+        </listitem>
+
+        <listitem>
+          <para>On the development machine, from the<filename>
+          &lt;sdkdir&gt;</filename>, start the cross-gdb:<programlisting># x86_64-enea-linux-gdb &lt;path_to_the_program&gt;/helloworld</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Connect GDB to the target:<programlisting>(gdb) target remote &lt;target_ip_address&gt;:1051</programlisting>Now
+          remote debugging is started and the GDB commands are available to
+          debug your program from the guest VM.</para>
+        </listitem>
+
+        <listitem>
+          <para>On the host, after finishing the cross-debugging session and
+          stopping the virtual machine, you can use the
+          <filename>qemu-ifdown</filename> script to clean up the
+          configuration on host:<programlisting># /etc/qemu-ifdown -t tap0 -a 192.168.122.10</programlisting></para>
+        </listitem>
+      </orderedlist>
+    </section>
+
+    <section id="kernel_crossdebug">
+      <title>Kernel Cross-Debugging</title>
+
+      <para>In order to debug the kernel, a serial connection is required
+      between the development and target machines. Debugging commands will be
+      sent from your workstation to the target machine via a serial
+      port.</para>
+
+      <para>The KGDB kernel options are enabled in the Enea NFV Access Host
+      SDK image and the tool can be used in the following way:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>On target, once serial communication is established, configure
+          <literal>kgdboc</literal> after the kernel boots:<programlisting># echo ttyS0,115200 &gt; /sys/module/kgdboc/parameters/kgdboc</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>In order to connect to gdb via kgdboc, the kernel must first
+          be stopped:<programlisting># echo g &gt; /proc/sysrq-trigger</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Close the console to the target, eg.: <command>Ctrl +
+          ]</command> for a telnet session.</para>
+        </listitem>
+
+        <listitem>
+          <para>On your development machine, start cross-gdb using the vmlinux
+          kernel image as a parameter. The image is located in
+          <filename>&lt;sdkdir&gt;/sysroots/corei7-64-enea-linux/boot/</filename>
+          and should be the same as the image found in the
+          <literal>/boot</literal> directory from the target.<programlisting># x86_64-enea-linux-gdb /
+./sysroots/corei7-64-enea-linux/boot/vmlinux-4.9.30-intel-pk-standard</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Connect GDB to the target machine using target command and the
+          serial device:<programlisting>(gdb) set remotebaud 115200
+(gdb) target remote /dev/ttyS0</programlisting></para>
+        </listitem>
+      </itemizedlist>
+
+      <para>The kernel can now be debugged in a similar manner as an
+      application program.</para>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-guide-intel/swcomp.mk b/doc/book-enea-nfv-access-guide-intel/swcomp.mk
new file mode 100644
index 0000000..0d205f3
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide-intel/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-nfv-access-guide
+BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) Guide"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
index ed74f48..b6cf927 100644
--- a/doc/book-enea-nfv-access-guide/doc/getting_started.xml
+++ b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
@@ -5,254 +5,332 @@
   <title>Getting Started with Enea NFV Access</title>
 
   <para>Using Enea NFV Access requires access to a Linux machine, which is
-  used for preparing the bootable drive or for developing applications. System
+  used for preparing a bootable drive or for developing applications. System
   requirements for the development host are detailed in the <xi:include
   href="../../s_docbuild/olinkdb/pardoc-common.xml"
   xmlns:xi="http://www.w3.org/2001/XInclude"
-  xpointer="element(book_enea_nfv_access_release_info/1)" /> document included
-  with this release.</para>
+  xpointer="element(book_enea_nfv_access_release_info/1)" />.</para>
 
   <section id="sysshell_config">
-    <title>System Shell Configuration</title>
+    <title>Default Shell Configuration</title>
 
-    <para>Before installing Enea NFV Access, ensure that bash is the default
-    shell.</para>
+    <para>Before installing Enea NFV Access, make sure that bash is the
+    default shell.</para>
 
-    <para>If your system runs Ubuntu, you can use ls -l to ensure
-    <filename>/usr/bin</filename> is a symbolic link to bash. In case the link
-    points to dash, which is default in some Ubuntu versions, change it to
-    bash by running <emphasis role="bold">sudo dpkg-reconfigure
-    dash</emphasis> and answer <emphasis role="bold">No</emphasis> to the
-    question <literal>Use dash as the default system shell
-    (/bin/sh)?</literal>:</para>
+    <para><emphasis role="bold">To verify the default system
+    shell</emphasis></para>
 
-    <programlisting># ls -l /bin/sh
+    <itemizedlist>
+      <listitem>
+        <para>If your system runs Ubuntu, use list to verify if
+        <filename>/usr/bin</filename> is a symbolic link to <emphasis
+        role="bold">bash</emphasis>:</para>
+
+        <programlisting># ls -l /bin/sh
 lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; bash</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Optionally, in case the link points to <literal>dash</literal>,
+        change it through the following steps:</para>
+
+        <programlisting># ls -l /bin/sh
+lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; dash
+# sudo dpkg-reconfigure dash
+Use dash as the default system shell (/bin/sh)? No</programlisting>
+      </listitem>
+    </itemizedlist>
   </section>
 
   <section id="access_installer">
     <title>Enea NFV Access Installer</title>
 
-    <para>The easiest way to get up and running with Enea NFV Access is to use
-    the installer provided in the install directory for each supported
-    architecture in this release. The purpose of this installer is to guide
-    you through creating a bootable Enea NFV Access installation on a physical
-    media (e.g. USB stick or HDD).</para>
+    <para>The easiest way to get started with Enea NFV Access is by using the
+    installer provided for each supported architecture in this release. Each
+    installer guides you in the creation of a bootable Enea NFV Access
+    installation on a physical media.</para>
 
-    <section id="installer_prereq">
-      <title>Installer Prerequisites</title>
+    <section id="prereq">
+      <title>Prerequisites</title>
 
-      <para>Using the installer on the development host requires the
-      following:</para>
+      <para>The following files are needed on the development host
+      machine:</para>
 
       <itemizedlist>
         <listitem>
-          <para>a GRUB .efi binary</para>
+          <para>A GRUB.efi binary - available from the <ulink url="???">GNU
+          GRUB download page</ulink>.</para>
         </listitem>
 
         <listitem>
-          <para>a physical drive of 16GB or larger</para>
+          <para>For booting from an SSD/HDD: a rootfs that needs to be
+          installed on the board (e.g.
+          <filename>[path_to_EneaNFV_Access_folder]/[architecture]/inteld1521/images/enea-nfv-access/enea-nfv-access.tar.gz</filename>).</para>
         </listitem>
 
         <listitem>
-          <para>For USB booting you will need: a development based rootfs,
-          provided with the release (e.g.
-          <filename>enea-nfv-access-dev-inteld1521.tar.gz</filename>).</para>
+          <para>For USB booting: a development based rootfs (e.g.
+          <filename>[path_to_EneaNFV_Access_folder]/[architecture]/inteld1521/images/enea-nfv-access-dev/enea-nfv-access-dev-inteld1521.tar.gz</filename>).</para>
         </listitem>
+      </itemizedlist>
 
+      <para>Using the installer on the development host requires the
+      following:</para>
+
+      <itemizedlist>
         <listitem>
-          <para>For booting from an SSD or HDD you will need: any rootfs that
-          needs to be installed on the board, provided with the release (e.g.
-          <filename>enea-nfv-access.tar.gz</filename>).</para>
+          <para>A physical drive of 16GB or larger</para>
+        </listitem>
+
+        <listitem>
+          <para>Root permissions</para>
         </listitem>
       </itemizedlist>
     </section>
 
-    <section id="installer_usage">
-      <title>Installer Usage</title>
-
-      <para>The <emphasis role="bold">Enea NFV Access installer</emphasis>
-      shall be executed on the development host machine with root permissions.
-      Once the <filename>nfv_installer</filename> prompt is displayed, press
-      <literal>ENTER</literal> to get the full list of built-in
-      commands:</para>
-
-      <programlisting>help              - a guide on how to use the installer
-list-params       - lists parameters
-list-steps        - lists the available steps and the parameters that they depend on
-set               - sets a parameter (e.g. "set drive=/dev/sda")
-clear             - clears a parameter (e.g. "clear drive")
-list-partitions   - lists current drives and partitions
-dry               - describes the steps to be executed and checks if the files exist
-run               - executes the steps
-q or quit         - exits the script</programlisting>
-
-      <para>Enea NFV Access creates a bootable media by performing these
-      steps:</para>
+    <section id="installer_setup_usage">
+      <title>Installer Setup and Usage</title>
+
+      <para><emphasis role="bold">To install Enea NFV Access on a physical
+      drive</emphasis></para>
 
       <orderedlist>
         <listitem>
-          <para>Create two partitions on a designated drive (e.g.
-          /dev/sda):</para>
+          <para>Go to the installer location: <programlisting># cd [path_to_EneaNFV_Access_folder]/[architecture]/install/
+nfv-installer/script-installer</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Execute the script file, this will bring you to the installer
+          prompt: <programlisting># sudo ./nfv_installer.sh</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Optionally, press ENTER to see the list of available
+          commands:<programlisting>help - displays a guide on how to use the installer
+list-params - lists all available parameters
+list-steps - lists the installer steps and the parameters that they depend on
+set - sets a parameter (e.g. <literal>set drive=/dev/sda</literal>)
+clear - clears a parameter (e.g. <literal>clear drive</literal>)
+list-partitions - lists current drives and partitions
+dry - performs a simulation test run
+run - executes the installer, using the values you set for each parameter
+q or quit - exits the script</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>Set the required parameters depending on what steps you want
+          to run:</para>
+
+          <note>
+            <para>When using the installer for the first time, make sure to
+            set ALL parameters in order to be able to run all steps. See <xref
+                linkend="example_two">
+                 "Example 2" 
+              </xref> for details.</para>
+          </note>
+
+          <para><programlisting># set &lt;parameter_name&gt;=&lt;parameter_value&gt;</programlisting></para>
+
+          <orderedlist>
+            <listitem>
+              <para><parameter>drive=&lt;/dev/sdaX&gt;</parameter> - the drive
+              to partition</para>
+            </listitem>
+
+            <listitem>
+              <para><parameter>grub_binary=&lt;file&gt;</parameter> - points
+              to the <filename>GRUB</filename> executable to be installed
+              where <filename>grub_destination</filename> is set.</para>
+            </listitem>
+
+            <listitem>
+              <para><parameter>grub_destination=&lt;drive&gt;</parameter> -
+              specifies the partition where <filename>GRUB</filename> will be
+              installed</para>
+            </listitem>
 
-          <itemizedlist>
             <listitem>
-              <para>a 512MB partition for GRUB</para>
+              <para><parameter>rootfs_destination=&lt;drive&gt;</parameter> -
+              specifies the partition where the <filename>rootfs</filename>
+              will be deployed, used by <filename>GRUB</filename> to boot off
+              of.</para>
             </listitem>
 
             <listitem>
-              <para>the rest of the drive is reserved for the rootfs</para>
+              <para><parameter>rootfs_targz=&lt;rootfs.tar.gz
+              file&gt;</parameter> - the archive of the Enea NFV Access
+              <filename>rootfs</filename> you wish to unpack to where
+              <filename>rootfs_destination</filename> is set. Which file you
+              unpack depends on whether you booting from an SSD/HDD or from a
+              USB drive.</para>
             </listitem>
-          </itemizedlist>
+          </orderedlist>
         </listitem>
 
         <listitem>
-          <para>Configure GRUB on one partition (usually the first
-          one).</para>
+          <para>Optionally, perform a test run before affecting the actual
+          layout of the physical media with the command: <programlisting>dry</programlisting></para>
         </listitem>
 
         <listitem>
-          <para>Copy a root filesystem on the other partition.</para>
+          <para>Run the installer: <programlisting>run</programlisting></para>
         </listitem>
-      </orderedlist>
 
-      <note>
-        <para>Running step 3 will implicitly copy the installer on that root
-        filesystem in
-        <filename>/usr/bin/install_nfvaccess.sh.</filename></para>
-      </note>
+        <listitem>
+          <para>Exit the script: <programlisting>quit</programlisting></para>
+        </listitem>
+      </orderedlist>
 
-      <para>Each step mentioned above is executed or not depending on whether
-      certain parameters are set. Run the
-      <command><literal>list-steps</literal></command> command in order to
-      understand the built-in steps that the installer can execute and what
-      parameters they depend on. The command will print the following:</para>
+      <para>The Enea NFV Access installer creates a bootable media by
+      performing three steps. Each step is executed or not depending on
+      whether certain parameters are set:</para>
 
       <orderedlist>
         <listitem>
-          <para><command>Format drive</command> - Uses the drive set for the
-          <literal>drive</literal> parameter to create a 512MB partition for
-          GRUB and another partition for the rootfs. The rootfs partition will
-          be as large as the physical media minus 512MB. This step depends on
-          the following parameter(s): <programlisting>drive=</programlisting></para>
+          <para><command>Format drive</command> - creates a 512MB partition
+          which will be used by <filename>GRUB</filename>, and another to be
+          used for the <filename>rootfs</filename> (it should occupy the rest
+          of the physical media minus the first partition). This step depends
+          on the following parameter(s): <programlisting>drive=</programlisting></para>
         </listitem>
 
         <listitem>
           <para><emphasis role="bold">GRUB install</emphasis> - Installs the
-          binary pointed to by <literal>grub_binary</literal> on the drive set
-          in <literal>grub_destination</literal>. A
-          <filename>grub.cfg</filename> file will be created that will be
-          configured to boot off of <literal>rootfs_destination</literal>.
-          This step depends on the following parameters:<programlisting>grub_destination=
+          <literal>grub_binary</literal> on the drive set for
+          <literal>grub_destination</literal>. A <filename>grub.cfg</filename>
+          file will be created that will be configured to boot off of
+          <literal>rootfs_destination</literal>. This step depends on the
+          following parameters:<programlisting>grub_destination=
 grub_binary=
 rootfs_destination=</programlisting></para>
         </listitem>
 
         <listitem>
-          <para><emphasis role="bold">Root filesystem install</emphasis> -
-          Copies the files found in <literal>rootfs_targz</literal> to the
-          drive set in <literal>rootfs_destination</literal>. This step
-          depends on the following parameters:<programlisting>rootfs_targz=
+          <para><emphasis role="bold">Root Filesystem install</emphasis> -
+          Copies and unpacks the files found in
+          <literal>rootfs_targz</literal> to the
+          <literal>rootfs_destination</literal>. This step depends on the
+          following parameters:<programlisting>rootfs_targz=
 rootfs_destination=</programlisting></para>
         </listitem>
       </orderedlist>
 
-      <para>Parameters can be set through the <command>set</command> command
-      or cleared using the <command>clear</command> command. Since some
-      parameters are common for multiple steps, as is
-      <literal>rootfs_destination</literal> for the GRUB and rootfs
-      installation steps, you can get a list of all the parameters, by running
-      <literal>list-params</literal>.</para>
-
-      <para>The following parameters can be configured:<programlisting>grub_destination=[drive]    - specifies the drive where GRUB will be installed
-grub_binary=[file]          - points to the GRUB executable to be installed
-                              where grub_destination is set
-rootfs_destination=[drive]  - specifies where the rootfs will be deployed
-rootfs_targz=[.tar.gz file] - what file to unpack to where rootfs_destination is set
-drive=[/dev/sdaX]           - what drive to partition</programlisting></para>
-
-      <para>Before performing the actual partitioning and copying, a dry run,
-      using the <command>dry</command> command, can be executed without
-      affecting the actual layout of the physical media. Once all the
-      parameters are set according to the intended scenario, simply execute
-      the <command>run</command> command to set up the bootable media. Below
-      are a few examples of how the Enea NFV Access installer may be
-      used.</para>
-
-      <para>Example of partitioning a drive:<programlisting>set drive=/dev/sda
-run</programlisting></para>
-
-      <para>Example of partitioning a drive, installing GRUB and a root
-      filesystem:<programlisting>set drive=/dev/sda
+      <para>After using the installer and setting up the bootable media,
+      connect it to the target machine and configure the target machine to use
+      it as a primary boot device.</para>
+    </section>
+
+    <section id="examples">
+      <title>Examples of Execution</title>
+
+      <para>Below are a few examples of setups that the Enea NFV Access
+      installer can be used for:</para>
+
+      <example id="example_one">
+        <title>Partitioning a drive</title>
+
+        <programlisting>set drive=/dev/sda
+run</programlisting>
+      </example>
+
+      <example id="example_two">
+        <title>Partitioning a drive, installing GRUB and a Root
+        Filesystem:</title>
+
+        <programlisting>set drive=/dev/sda
 set grub_destination=/dev/sda1
 set grub_binary=/home/user/grub-binary.efi
 set rootfs_destination=/dev/sda2
 set rootfs_targz=/home/user/rootfs.tar.gz
-run</programlisting></para>
+run</programlisting>
+      </example>
 
-      <para>Example of deploying ONLY a root filesystem:<programlisting>set rootfs_destination=/dev/sda2
-set rootfs_targz=/home/user/rootfs.tar.gz
-runs</programlisting></para>
+      <example id="example_three">
+        <title>Deploying ONLY a root filesystem:</title>
 
-      <para>After using the installer and setting up the bootable media,
-      connect it to the target machine and configure the target machine to use
-      it as a primary boot device.</para>
+        <programlisting>set rootfs_destination=/dev/sda2
+set rootfs_targz=/home/user/rootfs.tar.gz
+run</programlisting>
+      </example>
     </section>
 
     <section id="troubleshooting">
       <title>Troubleshooting</title>
 
-      <para>GRUB might display the following: <literal>error: no such
-      partition</literal> or <filename>error: disk not found</filename>, if
-      the default GRUB config is set to use <filename>hd0</filename> as the
-      primary drive for booting. Due to this, the errors described above have
-      two possible causes:</para>
+      <para>GRUB might display the following errors if the default
+      configuration is set to use <filename>hd0</filename> as the primary
+      drive for booting:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>error: no such partition</literal></para>
+        </listitem>
+
+        <listitem>
+          <para><literal>error: disk not found</literal></para>
+        </listitem>
+      </itemizedlist>
+
+      <para>These errors have two possible causes:</para>
 
       <itemizedlist>
         <listitem>
           <para>The drive where Enea NFV Access was installed is not
-          identified as <literal>hd0</literal> by the BIOS.</para>
+          identified as <literal>hd0</literal> by BIOS.</para>
         </listitem>
 
         <listitem>
-          <para>The BIOS has assigned the <literal>hd0</literal> label to a
+          <para>BIOS has assigned the <literal>hd0</literal> label to a
           different drive (e.g. a USB stick) than the one where Enea NFV
           Access was installed.</para>
         </listitem>
       </itemizedlist>
 
-      <para>The solution for these errors is detailed below:</para>
+      <para>To rectify these problems the primary boot drive must be assigned
+      to the correct partition.</para>
+
+      <para><emphasis role="bold">To change the partition for the primary boot
+      drive</emphasis></para>
 
       <orderedlist>
         <listitem>
-          <para>In the GRUB selection screen press
-          <command><literal>c</literal></command> to enter the command
-          line.</para>
+          <para>Restart the host and in the <filename>GRUB</filename>
+          selection screen, enter the command line by pressing
+          <command>C</command>:</para>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center" contentwidth="600"
+                         fileref="images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg" />
+            </imageobject>
+          </mediaobject>
         </listitem>
 
         <listitem>
-          <para>Run <command>ls</command> to list all of the available
-          partitions</para>
+          <para>List all of the available partitions with
+          <command>ls</command>: <programlisting>partition list example</programlisting></para>
         </listitem>
 
         <listitem>
-          <para>For each available partition run <command>ls
-          PARTITION</command> in order to identify where Enea NFV Access was
-          installed.</para>
+          <para>In order to identify where Enea NFV Access was installed, for
+          each available partition run <emphasis role="bold">ls
+          &lt;partition&gt;</emphasis>: <programlisting>ls hd0</programlisting></para>
         </listitem>
 
         <listitem>
-          <para>After identifying the partition, press <command>ESC</command>
-          to return to the GRUB selection screen and press
-          <command>e</command> to edit the boot command.</para>
+          <para>After identifying the partition, return to the GRUB selection
+          screen by pressing <command>esc</command></para>
         </listitem>
 
         <listitem>
-          <para>Set the boot partition to the one identified in step 3</para>
+          <para>Press <command>e</command> to edit and set the boot partition
+          to the one identified previously: <programlisting>edit and set partition example</programlisting></para>
         </listitem>
 
         <listitem>
-          <para>Press <literal>F10</literal> to boot</para>
+          <para>To reboot to see if the change worked, press:
+          <command>F10</command></para>
         </listitem>
       </orderedlist>
     </section>
diff --git a/doc/book-enea-nfv-access-guide/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.png b/doc/book-enea-nfv-access-guide/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.png
new file mode 100644
index 0000000..c28d643
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.png
diff --git a/doc/book-enea-nfv-access-guide/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg b/doc/book-enea-nfv-access-guide/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg
new file mode 100644
index 0000000..319bf7e
--- /dev/null
+++ b/doc/book-enea-nfv-access-guide/doc/images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg
@@ -0,0 +1,3 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
+<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" preserveAspectRatio="xMidYMid meet" viewBox="0 0 640 640" width="640" height="640"><defs><path d="M0 93L640 93L640 547L0 547L0 93Z" id="b4lgbdl3I5"></path><clipPath id="clipbKzvApRlV"><use xlink:href="#b4lgbdl3I5" opacity="1"></use></clipPath></defs><g><g><g><g clip-path="url(#clipbKzvApRlV)" opacity="1"><image xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAoAAAAHGCAYAAADkJDrPAAAABmJLR0QA/wD/AP+gvaeTAAAACXBIWXMAAA3XAAAN1wFCKJt4AAAAB3RJTUUH4QsPCjUWZQ2x8QAAGJBJREFUeNrt3UtypDoCBdB0R63DK/CCvBKPalijWol36R5ldz4e6IM+SOiciI5+ZTsFSEJcxCffPh7vPw8AAJbxH1UAACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIDATH5//112u7fb/vz3qnWyep+Aq/xSBcx8kPjz+fWP373+e/uz2O9rLH8rd/1Cn6dt/8ktY++zqf0zt9/lrt/Zskvrp0b99ugDpevVsv1AAISEQXf7s94H1u3PSgNm6ednccU21ToBOApxOeX/+fwKBslR96/W9TvjSQQIgMAtAvRRUHv+7evf7JUXC3qlM2ih5fesv+e6pK7D9u+OPne2fl9/d1THV87QpQbEo+1PneEPfT5UPzknmEIgAiBcbO+g2nPW4U6zG2dmWM9cYj86gJYu/+q2qlF+Sf3GLi+nfn6kPlgyQ5tbP6vt7yAAQuUDWMkBY/R7qHLXp/b61yqv9eXXs+W3bO8z97rm3r5QOjNWuv0CGgiALBS0rpgFPFp+6SxDy3uotvUSu/yWu74j3td21Hat+0brYNny86H1j52glPYnQACEpOBx1QEmtvzel6Jrb1etehlt+2cOf6X1mRL4Y+tvhg3uw3sAuW1ANPtwbf2P1gazh7/Z6wcQAKHaAWvk5Y8YQp/rlHqwz1n/uwTuvZc177Vni8CUW4cldd66vWL1c/Qg0EjrD3fmEjDT2HvFQ2iQTvn7kpvccwNeyvKvfAikdv3Etm97mbh0+WcP6me3MeU1NjX6WG77HK1jSv8tXf+Ue3Nj25O6/WdPsGrVzwz3u0LI28fj/Uc1AACswyVgAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEABAAAQAQAAEAEAABABAAAQAQAAEAEAABABAAAQAQAAEAEAABABAAAQAoMSvFoX+/v6rZgEATvjz+dV8GWYAAQAW86tl4T0SLADAHfS8gmoGEABgMQIgAIAACACAAAgAgAAIAIAACADABH71WpCXQwMA/NNVr8wzAwgAsBgBEABAABzX5+enFiuoi571p60wVgCM69dIK/P5+fn4/v6O/uyK9Zjt4Ndi/Wevl71gcHZ7juqiRvnPMko+u7f8o1A0e5sCMHkAJN3oB+0R16/WCcZRkKpR/uvfl3z26Ge122XUkwKhFiDsskvAJZdoPj8///e/WJmvP3v+d+jz27/JKb9VnYTWM2f9Y/VXcztCdVXafq3q/+rAsxfWRruUGes7r78/at9QGaWfz+n7LhMDK+s6Axi6bJZ6UN3+beksyeu/z8689A4aR8EgZf1L6y919iV1lqxnXddYTqiMq/tM6+XH2i5lBjL079LPx/rfKLeYACwXAJ8Dc0kAKB2sVx/sZw4p2/5z9uD9Gg5a3St5ZX2Hll/rHsir+l+LkxUAAbBjCHT2TWn/Odt3esyAtio/JcDFZri35YUeFKl1f2Srzxs/ACYJgM8Dzvb/gesDT+wSd2x20ww9wBy6PgSSc78OhPrQmX7Tup9d3Y97Lf9Z/wAIgEVn97kPcYx+wPeEYZv67fWUbOv2Oyp/uz2tLx+Xrn9Keb0vCc8W2gGuctl7AI8uH8XuQQpdhtr73ZkB/ug+s9Tyay13bx32XosSqqMW730LtWXK+qVsf4uAl9K/crZ/u301yi9pu9jyS9cv9hRtafkztA/AXbx9PN5/ahf6+/vv4/F4PP58fv3rZ6twbyMr9Gn9HKDMXlZ6/VkrvglE+IMkZtAA7qNbAOyRZkfx8Xhfant5LNW3V92vAe7kP6oAAEAABABAABzDag+S1K6LnvWnrbj7WKGPz9fO2gz+79doO/P2nqK9n12xHrMNii3Wf/Z62TsAnN2eo7qoUX7JU2Ch5R8d/NzHt+a+sKI/n1/aDkYMgOQNZNbvmhOMoyBVo/zXvy/57NHParfLqAdTB3iAGwbA1wPwdoYjdAB8/nfo89v/zim/1cF0+/OjGaLY+sfqr3b7HNVVaftdGUD2tqFVmBpxtiLWd2IzkKH2r/H5nL5/tv/H9tOz21f6+5T9o6R+S/e/bbkp74sNbf/Z9jULCJMGwL0BrWSW5PXfZ2deemzn3gB2NOsR+mxp/aXOvqTOkvWs6xrLCZVxdZ9pvfxY26UGkKN/l34+1v96nECUbF/rE6Ba9Vujjx6dmOds/7aNR7mFCATAQQ9yqw8GM4eU7UHi7ODeawb0qvoumYFabf9drbw7jY+tZuJBAITBB/2zB6seM6Ctyk+9xLW3/JzbC84GgtIDcu7nZ7sXtmVgSTlBulv91u5/IAACUwSKnuWn3H9nhn7s7VO/wJMXQTPdGf6fz69Tl39azw5cPfvQa/nP+me9k4+9B80AAXC4g9xVB/zf338Njg3q9+gp2RbLbdl+R+XvHWBbXj4uXf+U8npfEu5Rfs1+FyvnzCXbZ9uk9J3W5V/ddqkPA8GKhroEvDewxp7wCwWCswP10X1mqeXXWm7sNQlH98LVuE8uZ0DNXb/U9q8d8FL6V872b7evRvklbRdbfun6xZ6yLC1/hvZp2f9at1+t7W9VZ7nbnzJeCHpw7O3j8f7T6sxs5Z3PWSYr9OmV+7l9fL460GbM0Ed75ScPgRhkIIkZlsfy2z57+xuXQQA0yIC+jfaHZXkKGABAAAQAQAAchFerlNVFz/rTVhgrAMY11D2AozxlOPtDHK3W/w4Pt9S6if2oLmqUX/IUWGz5HuIAYLgASLrZvgP1TicYoReAl5Yf+y7Xku1rcYI16kmBYAsQNuU9gEffRHD01vftf4c+v/2bnPJrbFfKz4++hSG2/rH6q90+R9tR2n6t6v/qwNPrm05a7Ht7vz9q31AZpZ/P6fsuEwMrm24GcHuQLJ0l2X6TwSizGqF1CH0DSeyzpfWXOvuSOkvWs65rLCdUxtV9Jrb80vWLtV3KDGPo36Wfj/U/L7IGmDgAlg7Wqw/2o4eUlGBZGtSPvkqwZni/sr5Tln/Vt/WMtv8Kf4AACJME2NLw0mMGtFX5KQ9x5M7K5Zafs36l2yfAAQiAIABXvoybU/720mosfF6xfQCk8SJopvIMMGcekGh90//VDxXEll9rNvJZ/wAIgMMc5EY44HvCsE399npKtnX7HZW/3Z5RH1DIeYq29yXh2UI7wFWGugS8d0CPPeEXCgRnA8LRfWap5dda7t467L0WJVRHtQNE6Onj1PVLbf/aAS+lf+Vs/3b7apRf0nYpy4+1X2zbQ/cTlm7/DO0DcBdvH4/3n1Zn1SsPrl4vwQp9Wj8HmDM/eQhE+IMkZtAA7kMAbHSgBH0bgFF5ChgAQAAEAEAAHIRXNpTVRc/601bcfazQx+drZ20G//drtJ15hKcMZ3+Io9X63+HhlloPMRzVRY3yS54Cy30NjHv61t0XVrT9PnEQAJlyILN+15xghF4AXlr+69+XfDa1vNKD4agHUwd4gBsGwKMXQaceAEOf3/53TvmtZhW2Pz+aIUp9CXPs+1xrtc9RXZW235UBZG8bWgXUEWcrYn0nNMMYa/8an8/p+2f7f2w/Pbt9pb9P2T9K6rd0/zt6yXvq+pX2v5H3KxAATwy+pbMk228yGGVWI7QOoW8giX22tP5SZ19SZ8l61nWt78EdddYptvzS9Yu1XWoAOfp36edj/a/HCUTJ9rU+AapVvzX66NGJec72x74qcpSxHATAQQ7iqw8Go4eUlGBZGtR7zYBeVd8py7/q23pG239XK+9O42OrmXgQAGHwQf/swarHDGir8lMvcYWWH5shLgkEpQfk3M/Pdi9sy8CScoJ0t/qt3f9AAASmCBRnDpBnL2On3H9nhn7s7VO/wJMXQTPdGf6fz69Tl39azw5cPfsQW36t2chn/bPeycfeg2aAADjEQW6EA/7v778Gxwb1e/SUbIvltmy/o/L3DrCjvk4ntY56XxLuUX7NfpcS2s+sW2rfaV3+1W2X+jAQrGioS8B7A2vsCb9QIDg7UB/dZ5Zafq3lxl6TcHQvXI375HIG1Nz1S23/2gEvpX/lbP92+2qUX9J2KcuPtV9s20P3E5Zu/wzt07L/lf6+R/22rLPc7U8ZLwQ9OPb28Xj/aXVmtvLO5yyTFfr0yv3cPj5fHWgzZuijvfKTh0AMMpDEDMtj+W2fvf2NyyAAGmRA30b7w7I8BQwAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACAAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAIACqAgAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAAAEQAAABEAAAARAAQAAEAEAABABAAAQAQAAEAEAABABgXL9aFv77+68aBgAYjBlAAIDFvH083n9UAwDAOswAAgAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIOz6/f1XJQCAAAgAgADIITNoACAAslAoey5nhBAoiDJiXzvTL/XltnUxU/vN0n/0WQFw6UFptZ3u9/ffx5/Pr8fj8Xj8+fxaagCYZVtHX8/f33+brqODkvpbuf9rXwRAmniGv6N/Q24fso2MVn+pyz8TplLKbrl8qOWXKgjvkNsdOfb71LKf/733+de/q7n81vXznF1MXf+rDxKvs6E52xcqo3X/KG3/lv27tPzU/SOnPWNtFNr/Yvvmmf235f4Vq7+Uz8f6d842nK2/nDoqab+jZZeOUa2WX2N8GGn8RQAcLvyFBsDSATJUTuhgVWv5resnd/1HuRRe6wDYun+0Xr+ry0/ZP1qEwb1Z8aPbRUr6f+v9q3R8qTn7drb+cuuopP3O1HfN7c9dfun4MNL4yxhcAk48KN91ebXXLWf9r9rWnqF59LPsWS7Vjbq83rdUlJY/Wn88E67sD2uMTbRnBvDgzC1lev6q8LLy8luHv5LtS+k/d+/fZhXm2r96B46R9w/9BwFQCPzHjjTaQxNXLj/lnrlZQv5RPdaaYRn1QNe6fzuwP9TfoPtH7P7kOyzf/kcOl4ADO9Jqr0mZ8Qz37FN8NT4XKmP0/qN/U9K/Z+5/z2Vfve+BADhwuGj1mavXeZRll4awknv5Ug8+e0/VPd8DNtts6BX9O/b5O9xScKf9O9S/Zx6rtutx5bv8ei4/tIyj3139nkP6WeoS8N5B/3WQK/39mfXIfWjiytfA7F3CyBkoSj+//VyNy5WxF2PvLSN0+bhl/ygtv0b/Dr2Kotb+U2P/OFtGyfa1Hp9ajy81tunK+ostv9ZTyEfl91h+yfhQa/zlPt4+Hu8/qmE9PZ+EVY+gf4+4LaO9Rgt68hAInJxhaDGDAfp3G6NdQTF+cDUzgAAAi/EQCMAg3JMFCIAAi6l1Y74gCQiALMMrRbhDnXo6M95+V9SPNlFnAuDknXH7PzulQaH3+t9h+1tuw9XvtgyND73Gj6u/8cf+Cfe33FPAHsOH8n3ojgfJ2Gs6vMZj3HEcEACrHABC39eY86LcM7/PPTvdvoQ0tP6xl5iWlp+z7meWf2Y5NdsnZf1Lt790/Uv6z9Xl1+gfV37Xa68xKqV9SvebVvtnjfZLWbcV98+jlzxvv3/56Pc1xv9Y+3kNjgA41SxAzgxA6xmElM+H/h1ajxrlp561lyz/yvaLrX/p9peu/9UzXK3rN7f8HrOUPQ9grWcgW++ftdrvaAba/rm/DbF97DXYlYz/sfYzgz6e5R4C2d7Ds+18tTtjrLzey5vpgHfH9Rtt/a+ur5bLb7Fv+Z7UtfflO++fKcvK/WrGu4/Xs1v+HsDcvw8N/rHv4Cz9js4esxq55duB+5/AlAaYULuNfgP91eFrezmtd//3pLvtm3X9axz/EACHDpCxA0TpAWT1GT7976vK52P9c9T+M0r/LL3cuOr+effxZebtO7pEe6cTKP7JewAbDgShpyVjv4cr+yf7B0jA+CMA8q+DQqwzt+jsd7/k5iBdb3vP1E3rS8Ity7+qL/S8T/DOlxzvsC/P/E7C2usu7I3HJeDMs5bQY+ylvy9d/plyaq7fCMsPvaagVvuU3sty9vOt+09K+aFXZbSu39zyc2cYWqx/z/Fn9P2zRvulvKpl5f2zZv8q3X9SynMJ+FpvH4/3H9UAUHf2xMENGJlLwADCH7AYM4AAAIsxAwgZ3MgMgAAIi6l1g78gCYAA2EnNg+6IXwk10vrcOeCM8P4qX0l2736ubbHf0JrXwJzsvCvf5O0m92tfX6D+73Hwm60NQy+1P/qb2DdLnKmD0fu//RMBEAHJYAq7+0ZsBmTUPh9ar6OvEgt9bZ792/EBAfCyM9naZ6ihzz8Hu5bLL92+2PqnzGIc/S53+0u3/Uz9154lOSq/1QDYevtb7h85/W/vZb2x39feP1u3Yen+c7cDbcr4U7L9pfUbW7/UgHy0/NL9t0b5KftPyklB7NhxtnwvmhYAs2aUcs5QS3fw0uX32L7Q70N/lzrDkbN+pdueW/+1+1aL8lv2v9bbV2OGaO9vY3309cBWc/9sdR9Trf1nhBm22LJzvykjtE1Xj5+p4+PZ5bcYI3sfn0L9u/X4ggBY1Blq7OCtO+Ponf3q9eu9/Npf1XRl/2v1tWMjtUXpV3fdff9J/aqyWQ+6o49PpevXunztKQBO7eoB3dNRBoiRt3/2/tl6/a++BNV6+1IDxOxBcJTxebRAGtr+7Sx779m3O5yACIDOAJeu+x73WHE+XMx8wtJj/Y0f/w6Cd9qPnTDOcYVJEEzjRdAMuRPbcWG+E4Qen4HUY4j+JQAWDTgjvPB3tQH1+ZLju2yLfWnM+ild9gxte3SzvQPj9X3oijaovcy9Wx6e/av1Sfx22fp0viUfAjm6zLh3xlB6U3jPz5duX+ryQ/dapL4q5miHLnmKq0b91exbd1v+Xt/KGXRr9b9R1v/MDEPKk9xn958e/W9ve1+fgu3RvkfjT+/+kzs+1ug/LY9/PfpXqH/n9p+U+nQlKezt4/H+oxoY5WzaY/wAfcZX1uYhEIbhDA4A+jADCACwGE8BAwAIgAAACIAAAAiAAAAIgAAATGCp18AcvTTy6EWse78LvUjTe+wAAAFwQHtfUv4a7GIBLvZvAIDRuQR8MkACAMzKN4Fs+EJpAEAAXIwZPgDg7lwCBgAQAHlVckn46LO/v/+61AwAXMYl4BfbV7w8f3b283vlAQBc7e3j8f6jGgAA1uESMACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAgAAIAIAACACAAAgAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAAAAiAAAAIgAAACIAAAAiAAAAIgAAACIAAAAiAAAAIgAABd/Bd3tasDZYM0pAAAAABJRU5ErkJggg==" x="0" y="0" width="640" height="454" transform="matrix(1 0 0 1 1.1368683772161603e-13 93.00000000000006)"></image></g></g></g></g></svg>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/about_release.xml b/doc/book-enea-nfv-access-release-info-intel/doc/about_release.xml
new file mode 100644
index 0000000..b76f3ff
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/about_release.xml
@@ -0,0 +1,272 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="relinfo-about-release">
+  <title>About This Release</title>
+
+  <para>Enea NFV Access <xi:include href="eltf_params_updated.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(EneaLinux_REL_VER/1)" /> is a maintenance update to Enea
+  NFV Access 1.0 with the major changes listed below:<remark>INFO <emphasis
+  role="bold">eltf_params_updated.xml</emphasis> contains many parameters in
+  the book, also in the open source books, and MUST be created FROM <emphasis
+  role="bold">eltf_params_template.xml</emphasis>. The parameters are
+  automatically used in the books, via xi:include statements, similar to how
+  parameters from pardoc-distro.xml are included in the book. Read the file
+  <emphasis role="bold">eltf_params_updated_template_how_to_use.txt</emphasis>
+  for important details about formats and how to do! The idea is that ELTF
+  will auto-create/update it.</remark></para>
+
+  <itemizedlist>
+    <listitem>
+      <para>Key Component updates:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>DPDK 17.08</para>
+        </listitem>
+
+        <listitem>
+          <para>OVS 2.8</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
+      <para>Feature Extensions:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Element ODM: FCAPS framework with NETCONF and Yang.</para>
+        </listitem>
+
+        <listitem>
+          <para>EdgeLink Netconf (beta): NETCONF based VNF lifecycle
+          Management Tool.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
+      <para>Extended Tools Feature Set:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>python-pip</para>
+        </listitem>
+
+        <listitem>
+          <para>dosfstools</para>
+        </listitem>
+
+        <listitem>
+          <para>htop</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
+    <listitem>
+      <para>Unified cross-development SDK for host and virtualized
+      environments.</para>
+    </listitem>
+
+    <listitem>
+      <para>Native toolchain support on development image.</para>
+    </listitem>
+
+    <listitem>
+      <para>USB-stick based installation</para>
+    </listitem>
+
+    <listitem>
+      <para>Product Maintenance:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Optimizations</para>
+        </listitem>
+
+        <listitem>
+          <para>Security patches</para>
+        </listitem>
+
+        <listitem>
+          <para>Bug fixes</para>
+        </listitem>
+
+        <listitem>
+          <para>Updated documentation</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+  </itemizedlist>
+
+  <section id="release-content">
+    <title>Enea NFV Access Release Content</title>
+
+    <para>The current release contains along with other items, documentation,
+    pre-built kernels and images, a bootloader and a SDK. The directories
+    structure is detailed below:</para>
+
+    <programlisting>-- documentation/
+   /* Enea NFV Access documentation */
+-- x86-64 /* architecture */
+        -- inteld1521/
+           /* artifacts for the host side */
+                -- deb/
+                   /* deb packages */
+                -- images/
+                    -- enea-nfv-access
+                       /* precompiled artifacts for the platform release image */
+                        -- various artifacts (rootfs, kernel, config etc.)
+                    -- enea-nfv-access-dev
+                       /* precompiled artifacts for the development process. The image
+                          contains userspace tools and kernel configurations necessary
+                          for developing, debugging and profiling applications and
+                          kernel modules */
+                        -- various artifacts
+        -- qemux86-64
+           /* artifacts for the guest side */
+                -- deb/
+                   /* deb packages */
+                -- images/
+                    -- enea-nfv-access-guest
+                       /* precompiled artifacts for the QEMU/Docker release image  */
+                        -- various artifacts
+                    -- enea-nfv-access-guest-dev
+                       /* precompiled artifacts for the development process. The image
+                          contains userspace tools and kernel configurations necessary
+                          for developing, debugging and profiling applications and
+                          kernel modules  */
+                        -- various artifacts
+        -- install
+                -- sdk
+                   /* SDK related artifacts including SDK installer and manifests  */
+                        -- install-sdk.sh
+                           /* self-extracting archive installing cross-compilation
+                              toolchain for the platform */
+                -- nfv-installer
+                   /* Various tools assisting in booting Enea NFV Access  */
+                        -- script-installer
+                           /* installer tool intended for creating a bootable Enea
+                              NFV Access installation on a physical media  */</programlisting>
+
+    <para>For each combination of image and target, the following set of
+    artifacts is available:</para>
+
+    <programlisting>-- bzImage
+   /* kernel image */
+-- bzImage-target.bin
+   /* kernel image, same as above */
+-- config-target.config
+   /* kernel configuration file */
+-- image-name-target.ext4.gz
+   /* compressed EXT4 image of the rootfs */
+-- image-name-target.qcow2
+   /* QCOW image for QEMU - only for guest images */
+-- image-name-target.qemuboot.conf
+   /* qemu config file for the guest images */
+-- image-name-target.tar.gz
+   /* tar archive of the image */
+-- modules-&lt;target&gt;.tgz
+   /* external kernel modules */
+-- grub-efi-bootx64.efi
+   /* GRUB EFI file */</programlisting>
+  </section>
+
+  <section id="relinfo-supported-host-environment">
+    <title>Supported Host Environment</title>
+
+    <para>The following environments have been validated as host environments
+    for Enea NFV Access 1.1: <emphasis role="bold">Ubuntu 16.04 LTS,
+    64bit</emphasis>.</para>
+
+    <para><remark>Hardcoded now in this XML file. Might be moved to the
+    parameter file later.</remark> <remark>INFO Below is a complete section
+    with ID "eltf-target-tables-section" included from
+    elft_params_updated.xml. It contains a variable number of target tables
+    and the section title should be "Supported Targets with Parameters". It
+    has have a short sentence about what it is in the beginning. The subtitles
+    shall have the directory name of the target in the manifest.</remark>For
+    more details on host requirements and how to configure the host
+    environment, please see <xref linkend="sys-req-prerequisites" />.</para>
+  </section>
+
+  <xi:include href="eltf_params_updated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude"
+              xpointer="element(eltf-target-tables-section)" />
+
+  <section id="relinfo-provided-sdk">
+    <title>Provided Toolchain(s) (SDK)</title>
+
+    <para>The provided SDK contains toolchains supporting cross-compilation of
+    applications for both the host and the guest targets on an x86-64
+    machine.</para>
+
+    <para><remark>(Possibly add this in later) See the <trademark
+    class="registered">Enea</trademark> NFV Access Application Development
+    Guide for information on how to build and install a
+    toolchain.</remark></para>
+  </section>
+
+  <section id="relinfo-documentation">
+    <title>Provided Documentation</title>
+
+    <para>Enea NFV Access is provided with the following set of
+    documents:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Enea NFV Access Release Information - This document, describing
+        the Enea NFV Access release content.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Guide - A document describing how to use Enea
+        NFV Access, as well as use cases and benchmark results.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Open Source Report - A document containing the
+        open source and license information pertaining to packages provided
+        with Enea NFV Access.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Development Open Source Report - A document
+        containing open source and license information pertaining to packages
+        provided with Enea NFV Access for application developers.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Guest Open Source Report - A document containing
+        open source and license information concerning packages provided with
+        Enea NFV Access for a guest target.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Guest Development Open Source Report - A
+        document detailing the open source and license information of packages
+        provided with Enea NFV Access for applications development on a guest
+        target.</para>
+      </listitem>
+
+      <listitem condition="hidden">
+        <para>Enea NFV Access Test Report - The document that summarizes the
+        test results for the Enea NFV Access release.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Security Report - The document that lists all
+        security fixes included in the Enea NFV Access release.</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="security_fixes">
+    <title>Security Fixes</title>
+
+    <para>A detailed list of all security patches included with this release
+    is available in the Enea NFV Access Security Report document.</para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/book.xml b/doc/book-enea-nfv-access-release-info-intel/doc/book.xml
new file mode 100644
index 0000000..1ce7046
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/book.xml
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!ENTITY % local.common.attrib "xml:base CDATA #IMPLIED">
+]>
+<book id="book_enea_nfv_access_release_info">
+  <title><trademark class="registered">Enea</trademark> NFV Access Release
+  Information</title>
+
+  <subtitle>Release Version <xi:include href="eltf_params_updated.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(EneaLinux_REL_VER/1)" /></subtitle>
+
+  <!-- OLINKDBPATH_USED_BY_XMLMIND ../../s_docbuild/olinkdb  -->
+
+  <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="about_release.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="system_requirements_prerequisites.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="getting_enea_nfv_access.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="main_changes.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="known_bugs_and_limitations.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="../../s_docbuild/template/docsrc_common/contacting_enea_enea_linux.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_template.xml b/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_template.xml
new file mode 100644
index 0000000..eaa7ebd
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_template.xml
@@ -0,0 +1,151 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="eltf_created_params">
+  <title>File with Parameters in the Book Auto-updated by ELFT</title>
+
+  <note>
+    <para>See the <emphasis
+    role="bold">eltf_params_updated_template_howto_use.txt</emphasis> text
+    file for description of how to create the final <emphasis
+    role="bold">eltf_params_updated.xml</emphasis> from this template and for
+    all <emphasis role="bold">REQUIREMENTS</emphasis>. Use the command
+    "<emphasis role="bold">make eltf</emphasis>" to extract a full list of all
+    ELTF variables, which always begins with ELTF_ and don't only rely on the
+    howto text file list! The plan is that ELTF will auto-update this when
+    needed.</para>
+  </note>
+
+  <section id="host_prereq">
+    <title>Common Parameters</title>
+
+    <bridgehead>A programlisting, ID
+    "eltf-prereq-apt-get-commands-host"</bridgehead>
+
+    <para id="eltf-prereq-apt-get-commands-host"><programlisting>ELTF_PL_HOST_PREREQ</programlisting></para>
+
+    <bridgehead>A programlisting, ID
+    "eltf-getting-repo-install-command"</bridgehead>
+
+    <para id="eltf-getting-repo-install-command"><programlisting>ELTF_PL_GET_REPO</programlisting></para>
+
+    <bridgehead>Several phrase elements, various IDs. Ensure EL_REL_VER is
+    correct also compared to the "previous" REL VER in pardoc-distro.xml
+    "prev_baseline".</bridgehead>
+
+    <para id="EneaLinux_REL_VER"><phrase>ELTF_EL_REL_VER</phrase></para>
+
+    <para id="Yocto_VER"><phrase>ELTF_YOCTO_VER</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>ELTF_YOCTO_NAME</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="ELTF_YOCTO_PROJ_DOWNLOAD_URL">ELTF_YOCTO_PROJ_DOWNLOAD_TXTURL</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="ELTF_EL_DOWNLOAD_URL">ELTF_EL_DOWNLOAD_TXTURL</ulink></para>
+
+    <bridgehead>A programlisting, ID "eltf-repo-cloning-enea-linux". Use
+    $MACHINE/default.xml as parameter, where MACHINE is one of the target
+    directory names in the manifest.</bridgehead>
+
+    <para id="eltf-repo-cloning-enea-linux"><programlisting>ELTF_PL_CLONE_W_REPO</programlisting></para>
+
+    <bridgehead>A table with ONE row, only the row with ID
+    "eltf-eclipse-version-row" is included in the book. MANUALLY BOTH in the
+    template.xml and in the updated.xml, set condition hidden on the
+    &lt;row&gt;, if eclipse is not in the release.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row id="eltf-eclipse-version-row">
+            <entry>Eclipse version ELTF_ECLIPSE_VERSION plus command line
+            development tools are included in this Enea NFV Access release.</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <bridgehead>Below is one big section with title "Supported Targets with
+    Parameters". The entire section is included completely in the book via ID
+    "eltf-target-tables-section" and shall be LAST in the template. The
+    template contains ONE target subsection. COPY/APPEND it, if multiple
+    targets exist in the release and optionally add rows with additional
+    target parameters in each target subsection table.</bridgehead>
+  </section>
+
+  <section id="eltf-target-tables-section">
+    <title>Supported Targets with Parameters</title>
+
+    <para>The tables below describes the target(s) supported in this Enea
+    NFV Access release.</para>
+
+    <section id="eltf-target-table-ELTF_T_MANIFEST_DIR">
+      <title>MACHINE ELTF_T_MANIFEST_DIR - Information</title>
+
+      <para><informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="6*" />
+
+            <colspec colwidth="9*" />
+
+            <tbody>
+              <row>
+                <entry>Target official name</entry>
+
+                <entry>ELTF_T_NAME</entry>
+              </row>
+
+              <row>
+                <entry>Architecture and Description</entry>
+
+                <entry>ELTF_T_ARC_DESC</entry>
+              </row>
+
+              <row>
+                <entry>Link to target datasheet</entry>
+
+                <entry>See <ulink
+                url="ELTF_T_DS_URL">ELTF_T_DS_TXTURL</ulink></entry>
+              </row>
+
+              <row>
+                <entry>Poky version</entry>
+
+                <entry>ELTF_T_POKY_VER</entry>
+              </row>
+
+              <row>
+                <entry>GCC version</entry>
+
+                <entry>ELTF_T_GCC_VER</entry>
+              </row>
+
+              <row>
+                <entry>Linux Kernel Version</entry>
+
+                <entry>ELTF_T_KERN_VER</entry>
+              </row>
+
+              <row>
+                <entry>Supported Drivers</entry>
+
+                <entry>ELTF_T_DRIVERS</entry>
+              </row>
+
+              <row>
+                <entry>Enea rpm folder for downloading RPM packages for this
+                target</entry>
+
+                <entry><ulink
+                url="ELTF_T_EL_RPM_URL">ELTF_T_EL_RPM_TXTURL</ulink></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable></para>
+    </section>
+
+    <!-- ELTFADD_MORE_TARGET_SECTIONS_BELOW_IF_NEEDED -->
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_updated.xml
new file mode 100644
index 0000000..e6d3929
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_updated.xml
@@ -0,0 +1,156 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="eltf_created_params">
+  <title>File with Parameters in the Book Auto-updated by ELFT</title>
+
+  <note>
+    <para>See the <emphasis
+    role="bold">eltf_params_updated_template_howto_use.txt</emphasis> text
+    file for description of how to create the final <emphasis
+    role="bold">eltf_params_updated.xml</emphasis> from this template and for
+    all <emphasis role="bold">REQUIREMENTS</emphasis>. Use the command
+    "<emphasis role="bold">make eltf</emphasis>" to extract a full list of all
+    ELTF variables, which always begins with ELTF_ and don't only rely on the
+    howto text file list! The plan is that ELTF will auto-update this when
+    needed.</para>
+  </note>
+
+  <section id="host_prereq">
+    <title>Common Parameters</title>
+
+    <bridgehead>A programlisting, ID
+    "eltf-prereq-apt-get-commands-host"</bridgehead>
+
+    <para id="eltf-prereq-apt-get-commands-host"><programlisting># Host Ubuntu 16.04 LTS 64bit
+sudo apt-get -y update
+sudo apt-get -y install sed wget subversion git-core coreutils unzip texi2html \
+   texinfo libsdl1.2-dev docbook-utils fop gawk python-pysqlite2 diffstat \
+   make gcc build-essential xsltproc g++ desktop-file-utils chrpath  \
+   libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm \
+   libxml-parser-perl</programlisting></para>
+
+    <bridgehead>A programlisting, ID
+    "eltf-getting-repo-install-command"</bridgehead>
+
+    <para id="eltf-getting-repo-install-command"><programlisting>mkdir -p ~/bin
+curl https://storage.googleapis.com/git-repo-downloads/repo &gt; ~/bin/repo
+chmod a+x ~/bin/repo
+export PATH=~/bin:$PATH</programlisting></para>
+
+    <bridgehead>Several phrase elements, various IDs. Ensure EL_REL_VER is
+    correct also compared to the "previous" REL VER in pardoc-distro.xml
+    "prev_baseline".</bridgehead>
+
+    <para id="EneaLinux_REL_VER"><phrase>1.1</phrase></para>
+
+    <para id="Yocto_VER"><phrase>2.1</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>krogoth</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="http://www.yoctoproject.org/downloads/core/krogoth/21">http://www.yoctoproject.org/downloads/core/krogoth/21</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="https://linux.enea.com/6">https://linux.enea.com/6</ulink></para>
+
+    <bridgehead>A programlisting, ID "eltf-repo-cloning-enea-linux". Use
+    $MACHINE/default.xml as parameter, where MACHINE is one of the target
+    directory names in the manifest.</bridgehead>
+
+    <para id="eltf-repo-cloning-enea-linux"><programlisting>mkdir enea-linux
+cd enea-linux
+repo init -u git@git.enea.com:linux/manifests/el_manifests-virtualization.git \
+    -b refs/tags/EL6 -m $MACHINE/default.xml
+repo sync</programlisting></para>
+
+    <bridgehead>A table with ONE row, only the row with ID
+    "eltf-eclipse-version-row" is included in the book. MANUALLY in book, set
+    condition hidden if eclipse is not in the release. Do this both in
+    template.xml and updated.xml.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row condition="hidden" id="eltf-eclipse-version-row">
+            <entry>Eclipse version 4.3 (Mars) plus command line development
+            tools are included in this Enea NFV Access release.</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <bridgehead>Below is one big section with title "Supported Targets with
+    Parameters". The entire section is included completely in the book via ID
+    "eltf-target-tables-section" and shall be LAST in the template. The
+    template contains ONE target subsection. COPY/APPEND it, if multiple
+    targets exist in the release and optionally add rows with additional
+    target parameters in each target subsection table.</bridgehead>
+  </section>
+
+  <section id="eltf-target-tables-section">
+    <title>Supported Reference Boards with Parameters</title>
+
+    <para>The table(s) below describes the target(s) supported in this Enea
+    NFV Access release.</para>
+
+    <section id="eltf-target-table-D-1521">
+      <title>MACHINE Intel Xeon D-1521 - Information</title>
+
+      <para><informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="6*" />
+
+            <colspec colwidth="9*" />
+
+            <tbody>
+              <row>
+                <entry>Target official name</entry>
+
+                <entry>Intel Xeon D-1521</entry>
+              </row>
+
+              <row>
+                <entry>Architecture and Description</entry>
+
+                <entry>x86-64</entry>
+              </row>
+
+              <row>
+                <entry>Link to target datasheet</entry>
+
+                <entry>See link to <ulink
+                url="https://ark.intel.com/products/91202/Intel-Xeon-Processor-D-1521-6M-Cache-2_40-GHz">Intel's
+                datasheet</ulink></entry>
+              </row>
+
+              <row>
+                <entry>Poky version</entry>
+
+                <entry>Git-commit-id:
+                f01b909a266498853e6b3f10e6b39f2d95148129</entry>
+              </row>
+
+              <row>
+                <entry>GCC version</entry>
+
+                <entry>5.3<remark>FIXME</remark></entry>
+              </row>
+
+              <row>
+                <entry>Linux Kernel Version</entry>
+
+                <entry>3.12<remark>FIXME</remark></entry>
+              </row>
+
+              <row condition="hidden">
+                <entry>Supported Drivers</entry>
+
+                <entry>Ethernet, RTC, UART</entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable></para>
+    </section>
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_updated_template_how_to_use.txt b/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_updated_template_how_to_use.txt
new file mode 100644
index 0000000..62e5d02
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/eltf_params_updated_template_how_to_use.txt
@@ -0,0 +1,320 @@
+eltf_params_template_updated_howto_use.txt
+
+This is a way to collect all parameters for an Enea NFV Access release
+in one parameter file, easy to automatically update by ELTF regularly.
+
+NOTE: Both the release info AND the open source books use parameters from
+      here, but the XML file is inside the release info book directory.
+
+NOTE: The manifest_conf.mk, or overridden by the environment variable
+      MANIFESTHASH, contains the full tag (or hashvalue) for downloading
+      the manifest when the books are built. The list of target
+      directories are fetched from the manifest into the book.
+      The eltf_params_updates.xml can all the time contain
+      the final next complete tag e.g. refs/tags/EL6 or similar
+      in the ELTF_PL_CLONE_W_REPO parameter command lines.
+
+The ordinary book XML files use xi:include statements to include elements
+from this parameter file. The book XML files can thus be manually edited.
+Before editing, you must run "make init".
+Any other text in the template or updated.xml file, outside the parts that
+are included in the book, are not used but still all must be correct
+DocBook XML files.
+
+ELTF work:
+ template => ELTF replaces ALL ELTF_xxx variables => updated XML file
+    => push to git only if changed
+
+
+eltf_params_template.xml  (in git)
+   File used by ELTF to autocreate/update the real parameter
+   file eltf_params_updated.xml.
+
+eltf_params_updated.xml  (in git)
+   Real parameter file where ELTF has replaced all ELTF_xx variables with
+   strings, in several cases with multiline strings.
+   No spaces or linefeed allowed in beginning or end of the variable values!
+
+
+xi:include: Each parameter is xi:include'ed in various book files, using
+   the IDs existing in the parameter files.
+   In most cases the 1:st element inside an element with an ID is included
+   using a format like eltf-prereq-apt-get-commands-host/1.
+   In very few cases the element with the ID is included in the book, one
+   example is the target section which has an ID, but which contains
+   multiple subsections, one per target.
+   All IDs in a book must be unique.
+
+DocBook XML: All XML files must be correct DocBook XML files.
+
+Do NOT edit/save the real *updated.xml file with XMLmind to avoid changes
+   not done by ELTF. But it is OK to open the real file in XMLmind to
+   check that the format is correct.
+
+ELTF should autocreate a temporary "real" file but only replace
+   and push the eltf_params_updated.xml if it is changed.
+
+
+make eltf
+   This lists all ELTF_xxx variables and some rules how to treat them
+
+DocBook Format: All elements - rules:
+   Several strict generic XML rules apply for all strings:
+    1. No TABs allowed or any other control chr than "linefeed"
+    2. Only 7-bit ASCII
+    3. Any < > & must be converted to &lt; &gt; and &amp;
+       Similar for any other non-7-bit-ASCII but avoid those!
+    4. No leading spaces or linefeeds when replacing the ELTF_* variable
+    5. No trailing spaces or linefeeds when replacing the ELTF_* variable
+    6. Note: Keep existing spaces before/efter ELTF_* in a few cases.
+
+DocBook Format: <programlisting> - rules: ELTF*PL* variables
+   Several strict rules apply for the multiline string in programlisting
+   in addition to the general XML rules above:
+    7. Max line length < 80 char
+    8. Use backslash (\) to break longer lines
+    9. Use spaces (e.g. 4) to indent continuation lines in programlistings
+   10. No trailing spaces on any line
+   11. No spaces or linefeed immediately after leading <programlisting>
+   12. No spaces or linefeed before trailing </programlisting>
+
+DocBook Format: <ulink> - rules: ELTF_*URL* variables
+   13. ELTF_*URL and corresponding ELTF_*TXTURL shall be identical strings
+   14. Only if the URL is extremely long, the TXTURL can be a separate string
+
+Each target has one section with target parameters:
+       <section id="eltf-target-table-ELTF_T_MANIFEST_DIR">
+        <title>MACHINE ELTF_T_MANIFEST_DIR - Information</title>
+          ..... with many ELTF_ variables ....
+       </section>
+
+   15. If there is only one target. ELTF just replaces ELTF parameters
+
+   16. It there are multiple targets. ELTF copies the section and appends the
+       section the required number of times.
+       Each section ID will become unique: eltf-target-table-ELTF_T_MANIFEST_DIR
+       Each section title will become unique
+
+Tables with target parameters in each target section:
+   17. It is possible for ELTF to append more rows with one parameter each
+       to these tables, because the entire tables are included in the book
+
+Special - NOT YET READY DEFINED how to handle the optionally included
+   Eclipse and its version, but this is a first suggestion:
+   18. Just now ELTF can define ELFT_ECLIPSE_VERSION as a full string
+       with both version number and name,
+   19. MANUALLY if Eclipse is NOT included in the release,
+       the release manager should manually set condition="hidden" on
+       the entire section in the book XML about Eclipse
+
+
+
+BELOW WE TRY TO EXPLAIN EACH ELTF_* variable, but always check with make eltf
+if there are more new variables, missing in this description file.
+
+_____________________________________________________________________________
+ELTF_PL_HOST_PREREQ       Multiline list of host prerequisites, e.g. commands
+                          like sudo apt-get install xxxx or similar.
+                          First line = comment with the complete host name!
+                          It is possible to include multiple hosts by just
+                          adding an empty line, comment with host name, etc.
+                          xi:include eltf-prereq-apt-get-commands-host/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+# Host Ubuntu 14.04.5 LTS 64bit
+sudo apt-get update
+sudo apt-get install sed wget subversion git-core coreutils unzip texi2html \
+   texinfo libsdl1.2-dev docbook-utils fop gawk python-pysqlite2 diffstat \
+   make gcc build-essential xsltproc g++ desktop-file-utils chrpath  \
+   libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm \
+   libxml-parser-perl
+
+_____________________________________________________________________________
+ELTF_PL_GET_REPO          Multiline commands to download the repo tool
+                          xi:include eltf-getting-repo-install-command/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+mkdir -p ~/bin
+curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
+chmod a+x ~/bin/repo
+export PATH=~/bin:$PATH
+
+_____________________________________________________________________________
+ELTF_EL_REL_VER           General parameter string: The version of this Enea
+                          NFV Access release. Major version and optional .Minor
+                          Typically created from MAJOR and MINOR in enea.conf
+                          MINOR in enea.conf is empty or contains a dot+minor
+                          xi_include EneaLinux_REL_VER/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Examples:
+6
+  or
+6.1
+
+_____________________________________________________________________________
+ELTF_YOCTO_VER            General parameter string: Yocto version, created
+                          from DISTRO in poky.ent
+                          xi:include Yocto_VER/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Example:
+2.1
+
+_____________________________________________________________________________
+ELTF_YOCTO_NAME           General parameter string: Yocto name (branch), created
+                          from DISTRO_NAME_NO_CAP in poky.ent
+                          xi:include Yocto_NAME/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Example:
+krogoth
+
+_____________________________________________________________________________
+ELTF_YOCTO_PROJ_DOWNLOAD_TXTURL  General parameters. These two are IDENTICAL
+ELTF_YOCTO_PROJ_DOWNLOAD_URL     strings with correct Yocto version string
+                                 at the end, typically without "dot".
+                          xi:include ULINK_YOCTO_PROJECT_DOWNLOAD/1
+                          This is an <ulink url="...">...</ulink>
+                          Example:
+http://www.yoctoproject.org/downloads/core/krogoth/21
+
+_____________________________________________________________________________
+ELTF_EL_DOWNLOAD_TXTURL   General parameters. These two are IDENTICAL strings
+ELTF_EL_DOWNLOAD_URL      and shall be the http:/..... address where
+                          Enea NFV Access can be downloaded
+                          Often containing same version as in ELTF_EL_REL_VER
+                          xi:include ULINK_ENEA_LINUX_URL/1
+                          This is an <ulink url="...">...</ulink>
+                          Example:
+http://linux.enea.com/6
+
+_____________________________________________________________________________
+ELTF_PL_CLONE_W_REPO      Multiline commands to run repo to clone everything.
+                          Use the variable $MACHINE/default.xml (the text in
+                          the book will list the avaiable values of MACHINE,
+                          taken from the manifest repository)
+                          xi:include eltf-repo-cloning-enea-linux/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+mkdir enea-linux
+cd enea-linux
+repo init -u git@git.enea.com:linux/manifests/el_manifests-virtualization.git \
+    -b refs/tags/EL6 -m $MACHINE/default.xml
+repo sync
+
+_____________________________________________________________________________
+ELTF_ECLIPSE_VERSION      Optional general parameter string.
+                          NOT YET READY DEFINED
+                          Just now a release manage must manually set
+                          condition="hidden" on the Eclipse section,
+                          if Eclipse is not included in the release.
+                          ELTF just replaces ELTF_ECLIPSE_VERSION with a full
+                          string with "X.Y (name)"
+                          It includes the ID and can only be ONCE in the book.
+                          xi:include eltf-eclipse-version-row
+                          Example.
+4.5 (Mars)
+
+
+_____________________________________________________________________________
+ELTF_T_*                  All these are in each target (MACHINE) and ELTF
+                          must separately replace them with strings for
+                          each target
+                          NOTE: All (except the MANIFEST_DIR) are in rows
+                                in a table and ELTF can select to append
+                                more parameters by adding more rows
+
+_____________________________________________________________________________
+ELTF_T_MANIFEST_DIR       This happens to be in two places. Must be exactly
+ELTF_T_MANIFEST_DIR       the directory name in the manifest, e.g. same
+                          as the MACHINE names in $MACHINE/default.xml.
+                          In book: a) Part of section ID
+                                   b) Part of section title
+                          Examples:
+p2041rgb
+  or
+ls1021aiot
+  or
+qemuarm
+
+_____________________________________________________________________________
+ELTF_T_NAME               Target specific: "Target Official Name"
+                          NOT same as the target directory name in most cases.
+                          In book: An <entry> element in a row
+                          Examples:
+P2041RGB
+  or
+LS1021a-IoT
+  or
+qemuarm
+
+_____________________________________________________________________________
+ELTF_T_ARC_DESC           Target specific: "Architecture and Description"
+                          It can be a short identification string or
+                          it can be a longer descriptive sentence.
+                          In book: An <entry> element in a row
+                          Examples:
+Power, e500mc
+  or
+ARM Cortex-A7
+
+_____________________________________________________________________________
+ELTF_T_DS_TXTURL          Target specific: "Link to target datasheet. These
+ELTF_T_DS_URL             two usually are IDENTICAL strings with correct
+                          hyperlink to the target's official datasheet.
+                          In book: an <ulink url="...">...</ulink>
+                          Only if the link is VERY LONG, the text part shall
+                          instead be a descriptive string (see 2:nd example).
+                          NOTE: Also here no spaces or line-feeds!
+                          Examples:
+url="http://wiki.qemu.org">http://wiki.qemu.org
+or
+url="http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/qoriq-arm-processors/qoriq-ls1021a-iot-gateway-reference-design:LS1021A-IoT">link to NXP's datasheet
+
+_____________________________________________________________________________
+ELTF_T_POKY_VER           Target specific: "Poky version" created either
+                          from POKYVERSION in poky.ent
+                          or using a hashvalue with a leading string, in
+                          which case it may be different per target.
+                          In book: An <entry> in a row
+                          Examples:
+15.0.0
+or
+Git commit id: 75ca53211488a3e268037a44ee2a7ac5c7181bd2
+
+_____________________________________________________________________________
+ELTF_T_GCC_VER            Target specific: "GCC Version". Should be in poky
+                          but not easy to find among various parameters.
+                          ELTF would extract it from build logs building SDK
+                          and it is possibly different per target.
+                          In book: An <entry> in a row
+                          Example:
+5.3
+
+_____________________________________________________________________________
+ELTF_T_KERN_VER           Target specific: "Linux Kernel Version". Often
+                          different per target.
+                          In book: An <entry> in a row
+                          Example:
+3.12
+
+_____________________________________________________________________________
+ELTF_T_DRIVERS            Target specific: "Supported Drivers". This is a
+                          comma-separated list of driver names.
+                          ELTF should create the list in same order for each
+                          target, e.g. alphabetic migth be OK.
+                          In book: An <entry> in a row
+                          Example:
+Ethernet, I2C, SPI, PCI, USB, SD/SDHC/SDXC
+
+
+_____________________________________________________________________________
+ELTF_T_EL_RPM_TXTURL      Target specific: "Enea rpm folder for downloading
+ELTF_T_EL_RPM_URL         RPM packages for this target". These two are
+                          INDENTICAL strings with hyperlink to the web site
+                          at Enea where the customer can download RPMs
+                          Note: Often the ELFT_EL_REL_VER value and
+                                the ELTF_T_MANIFEST_DIR are used in the link.
+                          In book: an <ulink url="...">...</ulink>
+                          Example:
+url="https://linux.enea.com/6/ls1021aiot/rpm">https://linux.enea.com/6/ls1021aiot/rpm
+
+_____________________________________________________________________________
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/getting_enea_nfv_access.xml b/doc/book-enea-nfv-access-release-info-intel/doc/getting_enea_nfv_access.xml
new file mode 100644
index 0000000..2bf9c22
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/getting_enea_nfv_access.xml
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="relinfo-getting-enea-nfv-access">
+  <title>Getting Enea NFV Access</title>
+
+  <para>Enea NFV Access releases are available as binaries ready for download
+  on the <ulink
+  url="https://portal.enea.com/login/?redirect_to=https%3A%2F%2Fportal.enea.com%2F">Enea
+  Download Portal</ulink>. Updates of Enea NFV Access are also available for
+  download through the portal.</para>
+
+  <para>Log in using the credentials provided by Enea. Using the menu at the
+  top, browse to the <literal>NFV</literal> section, which will provide access
+  to a <literal>Files</literal> section and an <literal>Online
+  Documentation</literal> section. The <literal>Files</literal> section lists
+  each Enea NFV Access release version as a separate download package.
+  Clicking on any of the release packages will provide further details such as
+  the date when it was made available, the file size and the changelog. Most
+  importantly, it provides access to the download links.</para>
+
+  <para>Each archive is mirrored in several places, geographically. Choose the
+  archive in the region closest to you for better download speeds. For details
+  about the contents of the release package, please refer to <xref
+  linkend="release-content" />.</para>
+
+  <para>The <literal>Online documentation</literal> section provides quick
+  access to the documents delivered with the release. For details about the
+  books delivered and their purpose, please refer to <xref
+  linkend="relinfo-documentation" />.</para>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/jiraissues_override.xml b/doc/book-enea-nfv-access-release-info-intel/doc/jiraissues_override.xml
new file mode 100644
index 0000000..7282d0f
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/jiraissues_override.xml
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="relinfo-extracted-from-jira">
+  <title>Release-Specific Problems</title>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec colwidth="6*" colname="c1"/>
+
+      <colspec align="center" colwidth="1*" colname="c2"/>
+
+      <thead>
+        <row>
+          <entry align="center">Summary</entry>
+
+          <entry>Enea Ref</entry>
+        </row>
+      </thead>
+
+      <tbody>
+        <row>
+          <entry>Eclipse Plug-Ins for Perf and Latencytop are not functioning properly on P2041RDB target.</entry>
+
+          <entry>LXCR-6936</entry>
+        </row>
+
+        <row>
+          <entry><para>LTTng kernel tracing from Eclipse does not work due to RSE connectivity problems.</para><para>As a workaround, traces can be collected on target and visualized on Eclipse, after copying the files on the host system.</para></entry>
+
+          <entry>LXCR-7166</entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+</section>
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info-intel/doc/known_bugs_and_limitations.xml
new file mode 100644
index 0000000..67db036
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/known_bugs_and_limitations.xml
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="bugs-limitations">
+  <title>Known Problems in This Release</title>
+
+  <para>All known issues listed in this chapter will be addressed in
+  maintenance updates following the major release.<remark>INFO: The <emphasis
+  role="bold">Release-Specific Problems</emphasis> section further down is
+  generated from JIRA with gen_known_issues.py, but that script is HARDCODED
+  with affectedversion "EL7_3-virtualization" and needs to be adapted when a
+  release info for another ENFV Access version changes.</remark></para>
+
+  <section id="release-specific-limitations">
+    <title>Release-Specific Limitations</title>
+
+    <para><emphasis role="bold">Issues concerning the current
+    release</emphasis>:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>OFP and ODP are not included with the current release but they
+        will be included in a later maintenance update.<remark>FIXME,
+        requesting help from Ca</remark></para>
+      </listitem>
+    </itemizedlist>
+
+    <para><emphasis role="bold">Issues affecting
+    documentation</emphasis>:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Documents provided in this release will continue to be regularly
+        updated with additional content. </para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">PDF navigation</emphasis>: When using
+        links to open other PDFs, or jump to another place in the same PDF,
+        jumping back sometimes fails. This has been observed when opening a
+        PDF in Adobe Reader, inside a browser with PDF add-on, as well as when
+        the browser is configured to open PDF files in an external PDF reader.
+        As a workaround, open the HTML version of the
+        document.<remark>LXCR-3283</remark></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <!-- The file with a section below is autocreated by make init  -->
+
+  <!-- <xi:include href="jiraissues_generated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/main_changes.xml b/doc/book-enea-nfv-access-release-info-intel/doc/main_changes.xml
new file mode 100644
index 0000000..a0cf1c5
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/main_changes.xml
@@ -0,0 +1,114 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="relinfo-changes">
+  <title>Main Changes</title>
+
+  <para>This chapter provides information about the new features added in the
+  current release, as well as details on the provided packages and the
+  backwards compatibility with previous versions of Enea NFV Access.</para>
+
+  <section id="relinfo-changes-other">
+    <title>New Features</title>
+
+    <itemizedlist>
+      <listitem>
+        <para>Key Component updates:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>DPDK 17.08</para>
+          </listitem>
+
+          <listitem>
+            <para>OVS 2.8</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Feature Extensions:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Element ODM: FCAPS framework with NETCONF and Yang.</para>
+          </listitem>
+
+          <listitem>
+            <para>EdgeLink Netconf (beta): NETCONF based VNF lifecycle
+            Management Tool.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Extended Tools Feature Set:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>python-pip</para>
+          </listitem>
+
+          <listitem>
+            <para>dosfstools</para>
+          </listitem>
+
+          <listitem>
+            <para>htop</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Unified cross-development SDK for host and virtualized
+        environments.</para>
+      </listitem>
+
+      <listitem>
+        <para>Native toolchain support on development image.</para>
+      </listitem>
+
+      <listitem>
+        <para>USB-stick based installation</para>
+      </listitem>
+
+      <listitem>
+        <para>Product Maintenance:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Optimizations</para>
+          </listitem>
+
+          <listitem>
+            <para>Security patches</para>
+          </listitem>
+
+          <listitem>
+            <para>Bug fixes</para>
+          </listitem>
+
+          <listitem>
+            <para>Updated documentation</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="open_source">
+    <title>Open Source</title>
+
+    <para>For more information about the Open Source packages included, please
+    refer to the Enea NFV Access Open Source Reports provided with this
+    release.</para>
+  </section>
+
+  <section id="relinfo-backward-compat">
+    <title>Compatibility</title>
+
+    <para>Due to the fact that ODP and OFP are not included in this release,
+    any applications dependent on these components are not compatible with the
+    current release.</para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/system_requirements.xml b/doc/book-enea-nfv-access-release-info-intel/doc/system_requirements.xml
new file mode 100644
index 0000000..7bab63d
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/system_requirements.xml
@@ -0,0 +1,162 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="enea-nfv-access-sysreq">
+  <title>System Requirements</title>
+
+  <para>The host requirements listed below are extensive to allow for the
+  building of Linux images via the Yocto system, and not just
+  applications.</para>
+
+  <para>Please also see the system requirements in the Yocto 2.1 documents:
+  Yocto Project Start <ulink
+  url="http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html#yp-resources">
+  http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html#yp-resources</ulink>
+  and the Yocto Project Reference Manual <ulink
+  url="http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#intro-requirements">
+  http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#intro-requirements</ulink>.
+  If needed, replace the Yocto version in the link(s) provided with a more
+  recent version.</para>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec align="left" colname="1" colwidth="1*" />
+
+      <colspec align="left" colname="2" colwidth="3*" />
+
+      <spanspec nameend="2" namest="1" spanname="onetwo" />
+
+      <tbody>
+        <row>
+          <entry spanname="onetwo"><emphasis role="bold"> Build host
+          requirements<indexterm>
+              <primary>system requirements</primary>
+            </indexterm></emphasis></entry>
+        </row>
+
+        <row>
+          <entry>Linux distribution</entry>
+
+          <entry>The downloaded code shall be built on a Linux host to
+          generate images for your target or for emulation in QEMU. For
+          information about the supported hosts and targets, see the <emphasis
+          role="bold">Enea Linux Release Information</emphasis> in your Enea
+          Linux distribution.</entry>
+        </row>
+
+        <row>
+          <entry>Internet access</entry>
+
+          <entry>Internet access must be available when building an image,
+          since bitbake downloads source files from various servers during the
+          build.</entry>
+        </row>
+
+        <row>
+          <entry>Packages</entry>
+
+          <entry>Depending on the Linux distribution and version on host, some
+          packages may be required, by bitbake for example. You will install
+          any required packages while following the installation
+          instructions.</entry>
+        </row>
+
+        <row>
+          <entry>Targets</entry>
+
+          <entry>Images can be built or downloaded for any of the targets
+          supported in this release, as specified in the <emphasis
+          role="bold">Enea Linux Release Information</emphasis>.</entry>
+        </row>
+
+        <row>
+          <entry>Disk space</entry>
+
+          <entry><para>Your system should have at least 50 GB of free disk
+          space when bitbaking the basic enea-image-name kernel image.</para>
+          <para>For larger images and to allow for future package extensions
+          and variations in the build process, a minimum of 100 GB free disk
+          space is recommended.</para></entry>
+        </row>
+
+        <row>
+          <entry>Recommended RAM</entry>
+
+          <entry><para>Your system must have at least 4 GB available
+          RAM.</para> <para>It is recommended to have 8 GB RAM available for
+          parallel build jobs.</para></entry>
+        </row>
+
+        <row>
+          <entry>Java</entry>
+
+          <entry>Java <indexterm>
+              <primary>java</primary>
+            </indexterm>is required to run Eclipse. Currenly, Eclipse
+          generally recommends at least Java 6 JRE/JDK. More information
+          regarding operating environments for Eclipse, is provided in the
+          <emphasis>Eclipse Project Release Notes</emphasis> for the version
+          used. This can usually be found via
+          http://www.eclipse.org/eclipse/development/readme_eclipse_version.
+          See the <emphasis role="bold">Enea Linux Release Information
+          </emphasis>for the Eclipse Version.</entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+
+  <para>The build time depends on the capacity of the processor and other
+  hardware, available resources, speed of internet connection, load situation,
+  etc. E.g: on a fast 16 core machine with 16 GB RAM and SSD disks, a complete
+  build from source could take about two hours.</para>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec align="left" colname="1" colwidth="1*" />
+
+      <colspec align="left" colname="2" colwidth="3*" />
+
+      <spanspec nameend="2" namest="1" spanname="onetwo" />
+
+      <tbody>
+        <row>
+          <entry spanname="onetwo"><emphasis role="bold">Target
+          Requirements</emphasis></entry>
+        </row>
+
+        <row>
+          <entry>External memory</entry>
+
+          <entry>To boot a CGL<indexterm>
+              <primary>CGL</primary>
+            </indexterm> image, you need at least 16 GB on a hard-disk
+          drive<indexterm>
+              <primary>HDD</primary>
+            </indexterm> on eSATA, USB drive, or SD card.<remark>INFO: (packed
+          rootfs 4.5 GB + unpacked rootfs 1.5 GB + good
+          margins)</remark><remark>INFO: NFS does not support SELinux. In
+          order to have a security-enhanced Linux, one must take off from an
+          NFS-booted system and proceed with boot from external
+          memory.</remark></entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+
+  <section id="ensure-bash">
+    <title>System Shell Configuration</title>
+
+    <para>Before installing Enea Linux, ensure that bash is the default
+    shell.</para>
+
+    <para>If your system runs Ubuntu, you can use ls -l to ensure
+    <filename>/usr/bin</filename> is a symbolic link to bash. In case the link
+    points to dash, which is default in some Ubuntu versions, change it to
+    bash by running <emphasis role="bold">sudo dpkg-reconfigure
+    dash</emphasis> and answer <emphasis role="bold">No</emphasis> to the
+    question "Use dash as the default system shell (/bin/sh)?":</para>
+
+    <programlisting># ls -l /bin/sh
+        lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; bash</programlisting>
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/doc/system_requirements_prerequisites.xml b/doc/book-enea-nfv-access-release-info-intel/doc/system_requirements_prerequisites.xml
new file mode 100644
index 0000000..44e70af
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/doc/system_requirements_prerequisites.xml
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="sys-req-prerequisites">
+  <title>Host Requirements</title>
+
+  <para>Using Enea NFV Access or compiling applications requires certain
+  packages to be installed on your build host. The requirements listed below
+  are extensive to allow getting Enea NFV Access to be booted on target
+  machines and for building applications.</para>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec align="left" colname="1" colwidth="1*" />
+
+      <colspec align="left" colname="2" colwidth="3*" />
+
+      <spanspec nameend="2" namest="1" spanname="onetwo" />
+
+      <tbody>
+        <row>
+          <entry spanname="onetwo"><emphasis role="bold"> Build Host
+          Requirements<indexterm>
+              <primary>host requirements</primary>
+            </indexterm></emphasis></entry>
+        </row>
+
+        <row>
+          <entry>Linux distribution</entry>
+
+          <entry>The downloaded product can installed on the target machine
+          using a Linux host. For information about supported hosts and
+          targets, see <xref
+          linkend="relinfo-supported-host-environment" />.</entry>
+        </row>
+
+        <row>
+          <entry>Packages</entry>
+
+          <entry>Depending on the Linux distribution and version of the host,
+          certain packages may be required. See details on what packages are
+          needed and how to install them in the following sections.</entry>
+        </row>
+
+        <row>
+          <entry>Disk space</entry>
+
+          <entry>Your build host should have at least 50 GB of free disk space
+          for installing the SDK or cross-compiling applications.</entry>
+        </row>
+
+        <row>
+          <entry>Recommended RAM</entry>
+
+          <entry>Your build host must have at least 4 GB available
+          RAM.</entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info-intel/swcomp.mk b/doc/book-enea-nfv-access-release-info-intel/swcomp.mk
new file mode 100644
index 0000000..3ba7c8d
--- /dev/null
+++ b/doc/book-enea-nfv-access-release-info-intel/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-nfv-access-release-info
+BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) Release Information"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)