<html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> Now that open-vm-tools is in main, the obvious question is whether or not we should include open-vm-tools on the default installation media. While open-vm-tools is not explicitly required anymore for a VM to run properly, it does offer hypervisor integration: <ul> <li> vmtoolsd: service responsible for the virtual machine status report. </li> <li> vmware-check-vm: tool to check whether a utility has been started on a physical or virtual machine. </li> <li> vmware-xferlogs: Dumps logging/debugging information to the virtual machine logfile. </li> <li> vmware-toolbox-cmd: tool to obtain virtual machine information of the host such as statistics</li> <li> vmware-user-suid-wrapper: tool to enable clipboard sharing (copy/paste) between host and virtual machine. </li> </ul> Most users who run a VMware hypervisor want to run some sort of VMware tooling. VMware is now recommending open-vm-tools over the priority tools and several distributions (SuSE/SLES, Fedora/RHEL 7) are now installing these tools by default. I would like to propose that we ship the open-vm-tools on the desktop and server media and install by default on VMware targets. ~Ben <pre class="moz-signature" cols="72">-- Ben Howard <a class="moz-txt-link-abbreviated" href="mailto:ben.howard@canonical.com">ben.howard@canonical.com</a> Canonical GPG ID 0x5406A866 </pre> </body> </html>