Hi, Whilst in the process of merging some changes into trunk (fixing bugs), I've been trying to get the latest trunk working on my Xen test rig. This has Dom0 (master) with eth0 connected to the LAN and DomUs (guests) connected. The guests have their virtual eth0 NICs connected to an internal bridge (br-xen) with Dom0 providing masquerading NAT.
I've noticed two problems with this setup. First, multicast binding to
particular device when sending UDP seems to be broken. The following
gmond.conf snippet fails:
udp_send_channel {
mcast_if = br-xen
mcast_join = 239.2.11.71
port = 8659
ttl = 1
}
udp_recv_channel {
mcast_if = br-xen
mcast_join = 239.2.11.71
port = 8659
bind = 239.2.11.71
}
with the network traffic appearing on eth0 instead of over br-xen. Running
gmond with debug switched on, I see:
udp_send_channel mcast_join=239.2.11.71 mcast_if=br-xen host=NULL port=8659
However, it seems that the udp_recv_channel binds correctly as gmond sees none
of the metrics it sends. If I switch both sending and receiving UDP
multicast to bind to eth0 (or simply comment that line out), then gmond can
see its own metrics.
The second problem is with a Xen guest host transmitting over the internal
bridge. The gmond running in Dom0 is aware of the traffic from the DomU
machine as its XML has a corresponding HOST element (with a TN that updates
as expected); however, no actual metrics are recorded.
Are these known problems?
Cheers,
Paul.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
