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-devel] vif limitation to 1500 bytes (no vlan ?)

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] vif limitation to 1500 bytes (no vlan ?)
From: Yann Dupont <Yann.Dupont@xxxxxxxxxxxxxx>
Date: Fri, 22 Jul 2005 12:37:39 +0200
Delivery-date: Fri, 22 Jul 2005 10:36:14 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: CRIUN
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050404)
Hello, this is a follow up of a post on xen-users
I realize this post will probably be more adequate on this list.

I have a small problem; Is there a known limitation on vif code -
Network-device backend or frontend - which prohibits the usage of tagged
(802.1q) frames inside a domU ?

In dom0 I have a bridge with eth0 (epro1000) wich is connected to a
802.1q port
this same bridge has also a vif connected, corresponding to a domU.

Inside this domU , I can use vconfig to have numerous interfaces derived
from the vif, one by vlan,
BUT can only safely use a MTU of 1496. If I use the default MTU I have

For the moment I have solved the problem by using the physicall
interface INSIDE the domU. But I'd like to know if this problem is known ?

Yann Dupont, Cri de l'université de Nantes
Tel: - Fax: - Yann.Dupont@xxxxxxxxxxxxxx

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>