Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are these tools supposed to work on ESXi server.... #6

Open
os2zombie opened this issue Feb 21, 2023 · 3 comments
Open

Are these tools supposed to work on ESXi server.... #6

os2zombie opened this issue Feb 21, 2023 · 3 comments

Comments

@os2zombie
Copy link

Hello,

The addon works on VMware workstation. But they do not work under ESXi server. Is this a known issue are they not supposed to work under ESXi server ? I tried this under ESXi server 7.0.

Thank you,

Roderick

@wwiv
Copy link
Owner

wwiv commented Feb 22, 2023

Hey Roderick,

Thanks for the issue.

It's not a known issue, but I also don't have a ESXi to test on, nor really know much about how all of this was supposed to work. I looked at the openvm-tools repo and saw what calls it made, and did the same. I used the oldest (and easiest) protocol, so would have expected them to work on esxi.

I can update the readme that they don't work on esxi, but it's kinda surprising that it does not.

@os2zombie
Copy link
Author

os2zombie commented Feb 22, 2023

I started vmtoolsd under ESXi server 7.0, then moved the pointer around. It was locked inside the guest window. I hit the host key to return the host, moved the pointer on and off the VM window, then clicked back in the guest to get the pointer back. I tried copying something to the clipboard, then returned to the host to see if it worked, but the host clipboard was empty.

The log seems to detect the pointer is moving around only if the guest has it captured. It also seems to say it can't access the host clipboard. I use VMware Remote Console to access the guest.

vmtoolsd.log

@wwiv
Copy link
Owner

wwiv commented Sep 3, 2023

Just double checking, to start these did you use "start /PM vmtoolsd.exe" from startup.cmd

I don't know enough about how OS/2 running apps works to know why, but in my testing this was the only way to start it that consistently worked well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants