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


RE: [Xen-devel] VF as default interface on dom0

To: Simon Horman <horms@xxxxxxxxxxxx>, Satish Chowdhury <satish.chowdhury@xxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] VF as default interface on dom0
From: "Rose, Gregory V" <gregory.v.rose@xxxxxxxxx>
Date: Mon, 16 Nov 2009 09:20:06 -0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 16 Nov 2009 09:20:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091110193738.GF2782@xxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <be5d34890911051705j756f304fj4a331879eacdf8cc@xxxxxxxxxxxxxx> <20091107220940.GA2751@xxxxxxxxxxxx> <20091109111112.GA13304@xxxxxxxxxxxx> <be5d34890911092349i37b17e78t1c804c4e6ec5c143@xxxxxxxxxxxxxx> <20091110193738.GF2782@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpiPUyp/JImoRpvQjmfnOmhEsV7owEo4q5w
Thread-topic: [Xen-devel] VF as default interface on dom0
>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
>bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Simon Horman
>Sent: Tuesday, November 10, 2009 11:38 AM
>To: Satish Chowdhury
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] VF as default interface on dom0
>On Tue, Nov 10, 2009 at 01:19:51PM +0530, Satish Chowdhury wrote:
>> Hi Simon,
>> Thanks for the reply and reproducing the problem.
>> I didn't tried with pv_ops kernel yet.
>> I guess the issue is not with the driver.  As I understand, the
>behavior is
>> because of the L2 filtering done by 82576 NIC.
>> The NIC filters frames based on MAC address that are assigned to VFs.
>In my
>> experiment, the arp reply that reaches the NIC, has mac address of
>> on VM(domU). NIC's filtering based on VF MAC address fail. So, packet
>is not
>> queued to VF interface.  On dom0 a bridge is created, with VF and
>> virtual interfaces (no PF).
>> If we group PF interface also into this bridge, because of bridge
>> functionality, the packet get routed to the virtual interface and
>finally to
>> VM.
>> I am not 100% sure about above understanding of mine. Please, me know
>if you
>> think i am wrong.
>I suspect you are right, though I was hoping that its a problem
>that could be fixed by the driver configuring the card slightly
>It would probably be good to post your problem report to the
>e1000-devel and/or netdev lists to get some more eye's on it.
[Rose, Gregory V] 

I must have missed some previous email on this subject but from the context 
here I'm guessing that you're trying to put the PF driver on a bridge so that 
you can support some emulated connections in some VMs and some VFs in other VMs?

Is that the case?

- Greg

Xen-devel mailing list