Current status: - primary goal: to have one guest agent all downstreams can use, in all guests (with Linux and FreeBSD already supported), as efficient as possible (with Netlink already supported on Linux) - developed at https://gitlab.com/xen-project/xen-guest-agent (till now using gitlab PRs) - works fine as a replacement for the Xenserver xe-guest-utilities
Some points raised during the community call: - we likely want first to agree on a core set of collected information - could be made more configurable (eg. define a xenstore schema at runtime, we don't want specific schemas needs to cause forks) -> it could be the agent requesting a specific xenstore schema - what should be the criteria to advertise it as official Xenproject guest agent ? Yann Dirson | Vates Platform Developer XCP-ng & Xen Orchestra - Vates solutions web: https://vates.tech
