WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] dedicated interface

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] dedicated interface
From: <bwang@xxxxxxxxxx>
Date: Fri, 21 Oct 2011 00:10:02 -0400
Delivery-date: Thu, 20 Oct 2011 21:12:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Is there anyway to bind to a dedicated interface without modifying the pci 
hardware stuff?  Right now I have :
eth1 -> vif1.1 -> breth1 -> peth1.   Is it possible to eliminate the pass 
through vif1.1 and breth1 directly to peth1?  Reason I can't use the pci work 
around is that the peth1 is a modified tuntap interface and does not exist as a 
pci hardware device.

Thanks,
Ben Wang
DRS Defense Solutions
bwang@xxxxxxxxxx

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>