-
Notifications
You must be signed in to change notification settings - Fork 22
/
INSTALL.KVM
83 lines (57 loc) · 2.53 KB
/
INSTALL.KVM
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
How to Use Open vSwitch with KVM
=================================
This document describes how to use Open vSwitch with the Kernel-based
Virtual Machine (KVM). This document assumes that you have read and
followed INSTALL to get Open vSwitch setup on your Linux system.
Setup
-----
First, follow the setup instructions in INSTALL to get a working
Open vSwitch installation.
KVM uses tunctl to handle various bridging modes, which you can
install with the Debian/Ubuntu package uml-utilities.
% apt-get install uml-utilities
Next, you will need to modify or create custom versions of the qemu-ifup
and qemu-ifdown scripts. In this guide, we'll create custom versions
that make use of example open vSwitch bridges that we'll describe in this
guide.
Create the following two files and store them in known locations.
For example /etc/ovs-ifup and /etc/ovs-ifdown
/etc/ovs-ifup
--------------------------------------------------------------------
#!/bin/sh
switch='br0'
/sbin/ifconfig $1 0.0.0.0 up
ovs-vsctl add-port ${switch} $1
--------------------------------------------------------------------
/etc/ovs-ifdown
--------------------------------------------------------------------
#!/bin/sh
switch='br0'
/sbin/ifconfig $1 0.0.0.0 down
ovs-vsctl del-port ${switch} $1
--------------------------------------------------------------------
At the end of INSTALL, it describes basic usage of creating
bridges and ports. If you haven't already, create a bridge named
br0 with the following command:
% ovs-vsctl add-br br0
Then, add a port to the bridge for the NIC that you want your guests
to communicate over (e.g. eth0):
% ovs-vsctl add-port br0 eth0
Please refer to ovs-vsctl(8) for more details.
Next, we'll start a guest that will use our ifup and ifdown scripts.
% kvm -m 512 -net nic,macaddr=00:11:22:EE:EE:EE -net \
tap,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdown -drive \
file=/path/to/disk-image,boot=on
This will start the guest and associate a tap device with it. The
ovs-ifup script will add a port on the br0 bridge so that the
guest will be able to communicate over that bridge.
To get some more information and for debugging you can use Open
vSwitch utilities such as ovs-dpctl and ovs-ofctl, For example:
% ovs-dpctl show br0
% ovs-ofctl show br0
You should see tap devices for each KVM guest added as ports to
the bridge (e.g. tap0)
Please refer to ovs-dpctl(8) and ovs-ofctl(8) for more details.
Bug Reporting
-------------
Please report problems to [email protected].