This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] Re: openvswitch problem with XCP 1.0 RC3

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Re: openvswitch problem with XCP 1.0 RC3
From: blp@xxxxxxxxxxxxxxx (Ben Pfaff)
Date: Mon, 28 Feb 2011 07:36:02 -0800
Cancel-lock: sha1:pGshT3/9UV4MA88jAaMjA1CHsdc=
Delivery-date: Mon, 28 Feb 2011 07:36:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <EBDA14578E54D94191DD90533575FDFBF5EB3816@xxxxxxxxxxxxxxxxxxxxx> <87pqqfidg1.fsf@xxxxxxxxxxxxxxxx> <201102280952.09558.christian.fischer@xxxxxxxxxxxxxxxxxxx>
Reply-to: blp@xxxxxxxxxxxxxxx
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
Christian Fischer

> On Saturday 26 February 2011 06:15:26 Ben Pfaff wrote:
>> Adrian Costin <adrian@xxxxxxxxxxx> writes:
>> > When using the openvswitch backend (which is the default) on XCP 1.0 RC3
>> > network traffic for VLANs doesn’t reach the virtual machine.
>> > 
>> > Switching to bridge works without problems.
>> Some kernel network drivers, including igb, have VLAN-related
>> bugs that affect OVS but not the Linux bridge.  At Nicira we're
>> working on a workaround for this.  It will likely be ready next
>> week.
> A simple ping should always work.
> There are two problems with igb/e1000e/e1000.
> http://patchwork.ozlabs.org/patch/24670/
> You must patch the drivers to avoid chksum errors like
> e1000_tx_csum: checksum_partial proto=81!
> http://openvswitch.org/pipermail/discuss_openvswitch.org/2010-
> November/001143.html
> You must set the external port MTU to 1518 or VMs MTU to 1492
> We have no problems at all since we've applied the patches and adjusted the 
> external port MTU settings. All Networks are VLAN tagged, including the 
> Control network. All externel switch ports are vlan trunks tagged with the 
> appropriate VLAN IDs.

Fixing the bugs in the drivers is always a better solution.  If
your drivers work, then that's so much the better for you.
Ben Pfaff 

xen-api mailing list