Daniel Pocock
2013-Mar-05 12:49 UTC
[Pkg-xen-devel] Bug#702337: xen-xapi / Open vSwitch not really working
Package: xcp-xapi Version: 1.3.2-14 Severity: important I chose the Open vSwitch (ovs) networking mode when I installed XCP # cat /etc/xcp/network.conf openvswitch Whenever I boot a VM, I notice that the vif interface is created (e.g. vif1.0) on dom0, and the vif is added to the ovs bridge (I can see it in the output of ovs-vsctl show) However, there is no connectivity, I can't ping the domU I manually add the vif to a regular Linux bridge: brctl addif xenbr0 vif1.0 and then I can ping the domU successfully. Here is a sample of the ovs-vsctl show output: # ovs-vsctl show <UUID removed> Bridge "xenbr1" fail_mode: standalone Port "eth1" Interface "eth1" Port "xenbr1" Interface "xenbr1" type: internal Bridge xenapi Port xenapi Interface xenapi type: internal Port "vif7.1" Interface "vif7.1" Bridge "xapi0" Port "xapi0" Interface "xapi0" type: internal Bridge "xenbr0" fail_mode: standalone Port "vif3.0" Interface "vif3.0" Port "vif2.0" Interface "vif2.0" Port "xenbr0" Interface "xenbr0" type: internal Port "vif10.0" Interface "vif10.0" Port "eth0" Interface "eth0" Port "vif11.0" Interface "vif11.0" Port "vif1.0" Interface "vif1.0" Port "vif9.0" Interface "vif9.0" Port "vif7.0" Interface "vif7.0" Port "vif4.0" Interface "vif4.0" ovs_version: "1.4.2"
Debian Bug Tracking System
2013-Apr-16 18:06 UTC
[Pkg-xen-devel] Bug#702337: marked as done (xen-xapi / Open vSwitch not really working)
Your message dated Tue, 16 Apr 2013 18:02:55 +0000 with message-id <E1USADX-0001jg-Dw at franck.debian.org> and subject line Bug#702337: fixed in xen-api 1.3.2-15 has caused the Debian Bug report #702337, regarding xen-xapi / Open vSwitch not really working to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 702337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Daniel Pocock <daniel at pocock.com.au> Subject: xen-xapi / Open vSwitch not really working Date: Tue, 05 Mar 2013 13:49:57 +0100 Size: 3453 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20130416/49af0379/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Thomas Goirand <zigo at debian.org> Subject: Bug#702337: fixed in xen-api 1.3.2-15 Date: Tue, 16 Apr 2013 18:02:55 +0000 Size: 6591 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20130416/49af0379/attachment-0001.mht>
Maybe Matching Threads
- is_physical bug in xapi
- Bug#678723: i got same and found the reson
- received packet with own address as source address
- High iowait in dom0 after creating a new guest, with file-based domU disk on GFS
- Bug#678723: xcp-xapi: vif-interfaces added to database as PIF's