Hi Sergey, Sergey Grechin wrote: > The question is - where are backdoor interface specs published? Are > they open? I mean how VMWare let us know > how we have to communicate with virtualware?
There are no published specs - since implementing the backend of a backdoor call requires modifications to non-open-source VMware code (i.e., the binaries that run on the host OS), I don't think VMware has thought about opening that up as a public API. The addition of the VMCI device and VMCI sockets module (vsock) is one way we're trying to change this, but currently VMware Tools themselves still use the backdoor. > Okay, now for some reason > this magic asm stuff with those magic constants work, but who can > guarantee that it will remain to be compatible with newer VMWare > versions? Changing these things would break backwards compatibility with existing VMware product releases (since the same values are used in the binaries running on the host OS), and cause us tremendous headaches. :-) So it's very, very improbable that they will change. -- - Marcelo ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
