RE: [Xen-cim] [Patch] XenHostedNetworkPort

To:	"Jim Fehlig" <jfehlig@xxxxxxxxxx>
Subject:	RE: [Xen-cim] [Patch] XenHostedNetworkPort
From:	"Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Date:	Tue, 30 Jan 2007 12:05:07 -0500
Cc:	xen-cim@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Tue, 30 Jan 2007 09:04:39 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<45BF78FC.1070202@xxxxxxxxxx>
List-help:	<mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id:	xen-cim mailing list <xen-cim.lists.xensource.com>
List-post:	<mailto:xen-cim@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcdEkAQBnuzJgrshS7SMFdZa890CqAAAK7Xg
Thread-topic:	[Xen-cim] [Patch] XenHostedNetworkPort

> Hmm, I think we should just disable this association for now 
> - similar to Xen_HostedProcessor.  It is supposed to show an 
> association between virtual port and host port and we don't 
> have any host port instrumentation.  vifs seem rather 
> synthetic and thus don't need the relationship anyway.
> 
> We can revisit as the networking model evolves in SVPC.  In 
> the meantime a patch that disables mof import and building of 
> the provider would be useful :-)  Looks like we currently 
> disable Xen_HostedProcessor.mof but not building of 
> libXen_HostedProcessor.la.
Cool. I will get the patches to you. 
Raj

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim

WARNING - OLD ARCHIVES

xen-cim

RE: [Xen-cim] [Patch] XenHostedNetworkPort