I'll answer my own question. I created a clean XenServer CentOS 5.4 guest, made a backup copy of it, and installed XenServer Tools on it, and then compared it to the backup and found that the following files had changed:
/etc/rc.d/init.d/xe-linux-distribution
/etc/rc.d/rc0.d/K86xe-linux-distribution -> ../init.d/xe-linux-distribution
/etc/rc.d/rc1.d/K86xe-linux-distribution -> ../init.d/xe-linux-distribution
/etc/rc.d/rc2.d/S14xe-linux-distribution -> ../init.d/xe-linux-distribution
/etc/rc.d/rc3.d/S14xe-linux-distribution -> ../init.d/xe-linux-distribution
/etc/rc.d/rc4.d/S14xe-linux-distribution -> ../init.d/xe-linux-distribution
/etc/rc.d/rc5.d/S14xe-linux-distribution -> ../init.d/xe-linux-distribution
/etc/rc.d/rc6.d/K86xe-linux-distribution -> ../init.d/xe-linux-distribution
/etc/udev/rules.d/z10-xen-vbd-cdrom.rules
/etc/udev/rules.d/z10-xen-vcpu-hotplug.rules
/etc/yum.repos.d/Citrix.repo
/lib/udev/xen-vbd-device-type
/usr/bin/xenstore
/usr/bin/xenstore-chmod
/usr/bin/xenstore-exists
/usr/bin/xenstore-list
/usr/bin/xenstore-ls
/usr/bin/xenstore-read
/usr/bin/xenstore-rm
/usr/bin/xenstore-write
/usr/sbin/xe-daemon
/usr/sbin/xe-linux-distribution
/usr/sbin/xe-update-guest-attrs
/usr/share/doc/xe-guest-utilities-5.5.0/
/usr/share/doc/xe-guest-utilities-5.5.0/COPYING
/usr/share/doc/xe-guest-utilities-5.5.0/COPYING.LGPL
/usr/share/doc/xe-guest-utilities-5.5.0/examples/
/usr/share/doc/xe-guest-utilities-5.5.0/examples/Citrix.repo
/var/cache/xe-linux-distribution
/var/cache/xenstore/
/var/cache/xenstore/unique-domain-id
/var/cache/xenstore/attr/
/var/cache/xenstore/attr/PVAddons/
/var/cache/xenstore/attr/PVAddons/BuildVersion
/var/cache/xenstore/attr/PVAddons/Installed
/var/cache/xenstore/attr/PVAddons/MajorVersion
/var/cache/xenstore/attr/PVAddons/MicroVersion
/var/cache/xenstore/attr/PVAddons/MinorVersion
/var/cache/xenstore/attr/eth0/
/var/cache/xenstore/attr/eth0/ip
/var/cache/xenstore/data/
/var/cache/xenstore/data/meminfo_free
/var/cache/xenstore/data/meminfo_total
/var/cache/xenstore/data/os_distro
/var/cache/xenstore/data/os_majorver
/var/cache/xenstore/data/os_minorver
/var/cache/xenstore/data/os_name
/var/cache/xenstore/data/os_uname
/var/cache/xenstore/data/updated
So... I suppose to totally clean XenServer Tools off the container would require deleting all of the above. However, based on what I'm seeing, the easiest/safest thing to do would be to simply run this:
chkconfig xe-linux-distribution off
...of course, it appears that it wasn't running anyway (the daemon probably was unable to start inside an OpenVZ container), so this is mostly to reduce potential errors on start-up.
Curtis
