virt-manager does not support ovs bridge
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virt-manager (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Summary: if eth0 is bridged to a unix bridge br0, virt-manager can create
a vm connected through that bridge. However if eth0 is bridged to a openvswitch
bridge ovsbr1, then virt-manager cannot create a vm connected through that
bridge (fails when starting up). It needs to be taught to add the
<virtualport type='openvswitch'> tag into the <interface> section.
=======
Original description:
=======
Hello!
* Hypervisor is daily / latest Ubuntu 14.04 and guest is Ubuntu 12.04 and 14.04
-
KVM 1.7.0+dfsg-3ubuntu1
openvswitch-switch 2.0.1+git201401
libvirt0 1.2.1-0ubuntu5
-
When I create a KVM Virtual Machine with Virt-Manager, my guests have the following content:
---
<interface type='direct'>
<mac address=
<source dev='ovsbr1' mode='bridge'/>
<virtualport type='openvswitch'>
<parameters interfaceid=
<
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
---
IPv4 works as expected but IPv6 doesn't.
Then, if I edit the guest XML file with "virsh edit guest-1", and change <interface> like this:
---
<interface type='bridge'>
<mac address=
<source bridge='ovsbr1'/>
<virtualport type='openvswitch'>
<parameters interfaceid=
<
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
---
The both IPv4 and IPv6 works!
So, I guess that there is something wrong with libvirt...
The OVS bridges was created at the host with:
--
ovs-vsctl add-br ovsbr1
ovs-vsctl add-port ovsbr1 eth1
--
* The OpenvSwitch bridges are Okay *
Thanks!
Thiago
description: | updated |
Changed in virt-manager (Ubuntu): | |
importance: | Wishlist → Medium |
Changed in libvirt (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
summary: |
- IPv6 fails when "<interface type='direct'>", on top of OVS + virt-manager does not support ovs bridge |
description: | updated |
Changed in virt-manager (Ubuntu): | |
status: | Confirmed → Fix Released |
Thanks for submitting this bug.
It appears to me that 'interface type='direct'' works only for macvlan devices. This would require you to use a real physical NIC, as in:
<interface type='direct'>
<source dev='eth0' mode='vepa'/>
For instance see http:// libvirt. org/formatdomai n.html.
So if there is a bug it would seem to me to be in virt-manager, not libvirt. I'm not sure virt-manager has been taught about ovs at all so this would be more of a missing feature than a bug.
I'll mark thsi bug as affecting virt-manager, and mark it as a feature request ('confirmed/ wishlist' ).
Could you please give some more details about the precise options you chose when creating the VM in virt-manager?