The repository has my open-vm-tools extension, which is the open source equivalent of VMware Tools. I think that appliances are licensed in such a way that allow for VMware Tools to be included. I preferred to bypass the whole issue by packaging open-vm-tools. I just built an extension based on the 8/24 release. I will get it to Jason today.
Performance is also improved by compiling the kernel and SCSI modules with VMI support and using them with a VMware product which supports paravirtualization (like ESX/ESXi). I remastered 1.4.3, 2.2, and 2.3rc2 with this support and will be posting it very soon.
Do open-vm-tools provide the same functionality and performance as the VMware Tools? This means video support, functionality and performance, seamless mouse integration, hibernate on VM close, Resume on restart, etc? In a word, should I expect equal, high quality experience as using VMware Tools? I have not researched open-vm-tools, so pardon my question...
On VMI support/paravirtualization, I understand the current kernel does not include such support and needed to be re-compiled? I sort of mistakenly assumed all modern kernels have such support by default...
If this is the case, then would this not be beneficial to use such kernel in TC by default, which would bring this capability to all TC users?
E.g. if I am an end user, not a developer, and I want to create a TC VM, I could use a stock TC release along with vm-tools, not having to re-compile the kernel, since recompiling is not what comes to end-user's mind as realistic.
Looking forward to the TC VM posted... Thank You!