[libvirt-users] openvswitch port with no ip

Laine Stump laine at laine.org
Wed Jan 21 18:11:58 UTC 2015


On 01/21/2015 12:38 PM, Yaron Illouz wrote:
>
>  
>
> I used openvswitch with virt-intall
>
>  
>
> I defined a network
>
>  
>
>     <network>
>
>       <name>private</name>
>
>       <bridge name='virbr0'/>
>
>               <forward mode='bridge'/>
>
>       <virtualport type='openvswitch'/>
>
>     </network>
>
>  
>
> But get no ip for the ovs port when I launch the instance. Is this
> correct?
>
>  
>
>     ci-info: +++++++++++++++++++++++++Net device
> info++++++++++++++++++++++++++
>
>     ci-info:
> +--------+------+--------------+-------------+-------------------+
>
>     ci-info: | Device |  Up  |   Address    |     Mask    |    
> Hw-Address    |
>
>     ci-info:
> +--------+------+--------------+-------------+-------------------+
>
>     ci-info: |   lo   | True |  127.0.0.1   |  255.0.0.0  |        
> .         |
>
>     ci-info: |  eth1  | True |      .       |      .      |
> 52:54:00:24:16:29 |
>
>     ci-info: |  eth0  | True | 172.16.5.136 | 255.255.0.0 |
> 52:54:00:44:01:28 |
>
>  
>
>  
>
> In the bridge port vnet1 get assigned to virbr0
>
>  
>
>     Bridge "virbr0"
>
>         Port "virbr0"
>
>             Interface "virbr0"
>
>                 type: internal
>
>         Port "vnet1"
>
>             Interface "vnet1"
>

Are you certain you have a dhcp server that is listening on the network
segment connected to your ovs bridge named "virbr0"? (note that you must
have created that bridge outside of libvirt, as a libvirt network can
only reference an already-existing OVS bridge; it doesn't know how to
create them. It also won't run a dhcp server for an ovs bridge, you'll
have to do that separately too).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20150121/225c2373/attachment.htm>


More information about the libvirt-users mailing list