FWIW: It's possible in xen (open source xen anyway) to actually name the interfaces. But libvirt seems to not like that.
Otherwise this or something similar is necessary to collect consistent interface information about the network from a cluster of xen servers. On Mon, Jan 25, 2010 at 4:47 AM, Gianni Tedesco <gia...@brightbox.co.uk> wrote: > Hi, > > Xen domain ID's are not stable across guest reboots. This means that > interface statistics aren't properly grouped together. The following > patch strips the domain ID from the interface names so that statistics > for a singles guests interfaces are always grouped together. > > Xen interface names default to the format "vifXX.Y" where XX is the > domain ID and Y is the interface ID. The patch works by stripping the > "vifXX." from the interface name iff it conforms to the described naming > convention. > > The patch assumes the interface naming scheme so not sure how portable > it is. Perhaps a better fix would be to use interface MAC addresses. It > appears that libvirt has no suitable interface for determining the > interface ID... > > Please advise > > Thanks > > _______________________________________________ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd > > -- Edward Muller Sr. Systems Engineer Engine Yard Inc. : Support, Scalability, Reliability +1.866.518.9273 x209 - Mobile: +1.417.844.2435 IRC: edwardam - XMPP/GTalk: emul...@engineyard.com Pacific/US _______________________________________________ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
