Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
hypervisor:ovs1404 [2015/09/17 10:44]
giancarlo |
hypervisor:ovs1404 [2015/09/17 11:48]
giancarlo |
| </WRAP> | </WRAP> |
| |
| * Enable OVS network for VM | * Define OVS networks for KVM |
| | I.e. em2 network has untagged and tagged VLANs and we need one network for untagged VLAN and one network for tag 33 VLAN\\ |
| | <WRAP prewrap center> |
| | <code> |
| | # nano -w ovs-network-V0.xml |
| | </code> |
| | </WRAP> |
| | <WRAP prewrap center> |
| | <code xml> |
| | <network> |
| | <name>ovs-network-V0</name> |
| | <forward mode='bridge'/> |
| | <bridge name='br0'/> |
| | <virtualport type='openvswitch'/> |
| | </network> |
| | </code> |
| | </WRAP> |
| | <WRAP prewrap center> |
| | <code> |
| | # nano -w ovs-network-V33.xml |
| | </code> |
| | </WRAP> |
| | <WRAP prewrap center> |
| | <code xml> |
| | <network> |
| | <name>ovs-network-V33</name> |
| | <forward mode='bridge'/> |
| | <bridge name='br0'/> |
| | <virtualport type='openvswitch'/> |
| | <vlan> |
| | <tag id='33'/> |
| | </vlan> |
| | </network> |
| | </code> |
| | </WRAP> |
| | * Enable networks for KVM VMs |
| | <WRAP prewrap center> |
| | <code> |
| | # virsh net-define ovs-network-V0.xml |
| | # virsh net-start ovs-network-V0 |
| | # virsh net-autostart ovs-network-V0 |
| | |
| | # virsh net-define ovs-network-V33.xml |
| | # virsh net-start ovs-network-V33 |
| | # virsh net-autostart ovs-network-V33 |
| | </code> |
| | </WRAP> |
| | <WRAP prewrap center> |
| | <code> |
| | # virsh net-list |
| | |
| | Name State Autostart Persistent |
| | ---------------------------------------------------------- |
| | ovs-network-V0 active yes yes |
| | ovs-network-V33 active yes yes |
| | |
| | </code> |
| | </WRAP> |
| | You can use these networks in VM configuration from "Virtual Machine Manager" GUI. |
| |
