Mouse in a VMware virtual machine
Solved
vivi
-
Bruno -
Bruno -
Hello,
For testing, I sometimes use virtual machines installed under VMware (VMware Server 2).
The mouse works well sometimes and sometimes (notably after switching to another machine in between) the pointer is misaligned. Basically, you have to click in one part of the screen for the click to register somewhere else...
I have reinstalled the VMware Tools though!
Any idea?
For testing, I sometimes use virtual machines installed under VMware (VMware Server 2).
The mouse works well sometimes and sometimes (notably after switching to another machine in between) the pointer is misaligned. Basically, you have to click in one part of the screen for the click to register somewhere else...
I have reinstalled the VMware Tools though!
Any idea?
9 réponses
Hello again,
I understand you well, but my problem isn't with Linux.
I use VMware server on a 64-bit Vista, and I'm having this issue with XP virtual machines.
On Redhat, I often used VirtualBox; the times I used VMware were indeed on a server, and I accessed the virtual machine from a remote workstation (after all, VMware server is somewhat designed for that), but unlike today, I hadn’t encountered this problem before.
That's another topic...
I understand you well, but my problem isn't with Linux.
I use VMware server on a 64-bit Vista, and I'm having this issue with XP virtual machines.
On Redhat, I often used VirtualBox; the times I used VMware were indeed on a server, and I accessed the virtual machine from a remote workstation (after all, VMware server is somewhat designed for that), but unlike today, I hadn’t encountered this problem before.
That's another topic...
Thank you, yes it's a solution,
That's what I usually do. But now I'm trying to set up a domain server with Debian on it, and I can't get my machines into the domain from VirtualBox (probably a hardware or network configuration issue).
So I have no choice but to use VMware for my machines.
But under VirtualBox, I have to clone the disks if I want to do tests with multiple machines running (whereas with VMware, I just need to copy it).
Otherwise, you're right, I still prefer VirtualBox, especially in the latest versions...
But I will still look into doing it from VirtualBox. It might be worth spending a bit of time on it (in addition, it could be instructive) instead of being bothered with a problem that could simply be a hardware conflict...
Thank you,
That's what I usually do. But now I'm trying to set up a domain server with Debian on it, and I can't get my machines into the domain from VirtualBox (probably a hardware or network configuration issue).
So I have no choice but to use VMware for my machines.
But under VirtualBox, I have to clone the disks if I want to do tests with multiple machines running (whereas with VMware, I just need to copy it).
Otherwise, you're right, I still prefer VirtualBox, especially in the latest versions...
But I will still look into doing it from VirtualBox. It might be worth spending a bit of time on it (in addition, it could be instructive) instead of being bothered with a problem that could simply be a hardware conflict...
Thank you,
Hello,
On VMware, for optimal management of the screen and mouse, you need to install VMware Tools. These are specialized drivers. (e.g. on Ubuntu: https://www.commentcamarche.net/faq/31411-vmware-installer-les-additions-invite-dans-ubuntu )
Afterwards, on a Linux system, you could try to connect not through the system console, but with an X display, for example with Xming. This way, you won’t have issues with a "local" mouse.
VMware Server 2 is a rather heavy (it installs Apache) and outdated solution. VMware Player 3.1 is a newer and lighter solution.
Best regards
A foreigner is a friend we haven't met yet.
On VMware, for optimal management of the screen and mouse, you need to install VMware Tools. These are specialized drivers. (e.g. on Ubuntu: https://www.commentcamarche.net/faq/31411-vmware-installer-les-additions-invite-dans-ubuntu )
Afterwards, on a Linux system, you could try to connect not through the system console, but with an X display, for example with Xming. This way, you won’t have issues with a "local" mouse.
VMware Server 2 is a rather heavy (it installs Apache) and outdated solution. VMware Player 3.1 is a newer and lighter solution.
Best regards
A foreigner is a friend we haven't met yet.
Thank you,
But actually the tools (vmware tools) are installed, I even reinstalled them.
I have already experienced other issues on Linux (such as being unable to resize the screen), but not of this type.
I remain hopeful of finding a solution.
As for the heaviness of the version... yes, that's true, but I have a good machine, with enough memory, that handles it well.
But actually the tools (vmware tools) are installed, I even reinstalled them.
I have already experienced other issues on Linux (such as being unable to resize the screen), but not of this type.
I remain hopeful of finding a solution.
As for the heaviness of the version... yes, that's true, but I have a good machine, with enough memory, that handles it well.
I understood that the issue was under Linux.
But, well, the VMware server (1 or 2) locally in console mode is not the best.
That's why I was advising you to use VMware Player 3.1.
On XP, if it's a professional version, you can also use remote desktop, just like in X under Linux, it no longer uses the screen and mouse managed locally by VMware.
--
A stranger is just a friend you haven't met yet.
But, well, the VMware server (1 or 2) locally in console mode is not the best.
That's why I was advising you to use VMware Player 3.1.
On XP, if it's a professional version, you can also use remote desktop, just like in X under Linux, it no longer uses the screen and mouse managed locally by VMware.
--
A stranger is just a friend you haven't met yet.
Thank you very much, for what I have to do this will be enough.
I've already used the remote desktop instead of VNC... which just reminded me of this solution as well.
I'll test it right now and I'll come back to give the information.
I've already used the remote desktop instead of VNC... which just reminded me of this solution as well.
I'll test it right now and I'll come back to give the information.
RE-
I confirm that VNC solved my problem, so instead of going through the VMware backend, I'm using VNC.
There may be a hardware incompatibility (I have a laser mouse), so since it works through the software, it's all good like this.
I confirm that VNC solved my problem, so instead of going through the VMware backend, I'm using VNC.
There may be a hardware incompatibility (I have a laser mouse), so since it works through the software, it's all good like this.