LAVA Project

Merge lp:~terceiro/lava-project/kvm-further-networking-optimization into lp:lava-project

  1. kvm-further-networking-optimization
  2. Merge into production
Proposed by Antonio Terceiro
Status: Merged
Merged at revision: 61
Proposed branch: lp:~terceiro/lava-project/kvm-further-networking-optimization
Merge into: lp:lava-project
Diff against target: 41 lines (+32/-0)
1 file modified
doc/kvm-deploy.rst (+32/-0)
To merge this branch: bzr merge lp:~terceiro/lava-project/kvm-further-networking-optimization
Reviewer Review Type Date Requested Status
Linaro Validation Team Pending
Review via email: mp+173938@code.launchpad.net

Description of the change

document extra optimization for kvm networking setup

To post a comment you must log in.
Revision history for this message
Matthew Hart (matthew-hart) wrote :

I've been playing around with the KVM image and I noticed that by default it was setup to use NAT networking (assigned a 10.X address) and this would mean it is not visible by other devices on the internal network.

Does using this bridge setup solve this problem?

Revision history for this message
Antonio Terceiro (terceiro) wrote :

On Wed, Jul 10, 2013 at 01:59:00PM -0000, Matthew Hart wrote:
> I've been playing around with the KVM image and I noticed that by default it was setup to use NAT networking (assigned a 10.X address) and this would mean it is not visible by other devices on the internal network.
>
> Does using this bridge setup solve this problem?

Yes - the VM will be connected to the same network as the host.

--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/kvm-deploy.rst'
2--- doc/kvm-deploy.rst 2013-06-14 14:44:48 +0000
3+++ doc/kvm-deploy.rst 2013-07-10 13:18:32 +0000
4@@ -63,6 +63,38 @@
5 . /srv/lava/instances/<INST>/bin/activate
6 lava-dispatch /tmp/kvm.json
7
8+Optional: networking speed optimization
9+---------------------------------------
10+
11+By default, LAVA ``kvm`` devices will use ``virtio`` networking, which is a lot
12+faster than the QEMU default at the time of writing this.
13+
14+If you want to make networking even faster, you can re-define the
15+kvm_networking_options settings in the device configuration file to use
16+a TAP device. This requires some extra configuration, and that's why it's not the default.
17+
18+Device configuration file(``kvmXX.conf``)::
19+
20+ device_type = kvm
21+ root_part = 1
22+ kvm_networking_options = -net nic,model=e1000 -net tap,ifname=tap0
23+
24+Then add a bridge interface to the networking configuration
25+(``/etc/network/interfaces``). Example::
26+
27+ auto eth0
28+ iface eth0 inet dhcp
29+
30+ auto br0
31+ iface br0 inet dhcp
32+ bridge_ports eth0
33+ bridge_stp off
34+ bridge_fd 0
35+ bridge_maxwait 0
36+
37+Please note the above are examples. Make sure you consult the QEMU
38+documentation to create a proper TAP interface setup.
39+
40 Configuring the scheduler
41 -------------------------
42

Subscribers

People subscribed via source and target branches