[SOLVED] Slackware in QEMU - jumping mouse cursor in X when using vmware graphics driver
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware in QEMU - jumping mouse cursor in X when using vmware graphics driver
Hi,
I installed Slackware 14.1 inside of a QEMU 2.2.0 virtual machine and when I start an X session, using vmware video card emulation, the mouse cursor is jumping around inside the QEMU window and is out of control.
Everything else seems to work fine, no problems with the keyboard and no mouse issues in the console.
I also tried Salix in QEMU and there is no such issue.
How can I get the mouse working for Slackware inside QEMU with vmware graphics?
I tried to set proto=imps and proto=bare as module option for psmouse, but that changed nothing.
[edit] Oh, I forgot to mention that I have two Slackware installations in QEMU, one 32bit and one 64bit system and the mouse issue is on both.
Last edited by slacksam; 03-25-2015 at 10:30 AM.
Reason: solved
Looks like there is no such feature but if there is one, I never used it.
On other systems I'm running in QEMU I either don't use it and there are no mouse issues (like I mentioned it in my first post).
Quote:
Originally Posted by Ztcoracat
You might want to give Virtual Box a try.
I know Virtualbox but prefer QEMU mainly because I'm already using it for years and have many other distros running on it.
Quote:
Originally Posted by veerain
Is there any particular requirement to use vmware graphics?
Yes, the reason is that I have other (graphical) issues with Cirrus or VESA (not only when running Slackware).
Please consider my question like this:
What can I do to make the X session on Slackware in QUEMU with VMWare video emulation run without the mentioned mouse issues, like other Distributions do (eg. Salix or Manjaro)?
[edit] One option to solve this issue is to use "-usbdevice mouse" as start option with QEMU,
but I'm still wondering why the other distros mentioned above do not need that option.
It would help if you posted the type of mouse you use. Also the command you are using to start qemu. I have had this problem in the past but I don't remember how I fixed it. It seems it had something to do with screen resolution or size.
Last edited by AlleyTrotter; 03-24-2015 at 08:05 AM.
But as I already mentioned, I also have installations of other Linux distros in QEMU and I'm starting them the same way, on the same machine, with the same QEMU specific hardware configurations, but most of the others don't have that mouse issue.
Try with above. It seems that in the past qemu on slackware sometimes got confused for me with the order of longer command lines. The -monitor and -vga commands may be conflicting.
Also after booting try setting your display to a different resolution. I just can't find my notes on this issue, but you are not alone.
...
Also after booting try setting your display to a different resolution.
Tried it, but no success - the mouse problem still persists.
Even changing the resolution with xrandr doesn't solve the issue.
Please note the edited part in my last post. I don't think that the problem is a wrong QEMU option or screen resolution, but some wrong/missing configurations in the X server or kernel module options.
If the mouse movement is erratic, it can be fixed by adding a graphics tablet. I use libvirt with virtual machine manager, so I am not starting qemu from the command line. It looks like the option for a tablet is the following:
works best for me.
With the option -usbdevice mouse it works, too, but there's an issue in fluxbox: When I move the mouse cursor to the bottom border of an open window, the mouse cursor jumps to the right bottom corner of the screen.
With the option -usbdevice tablet it works properly and also automatic grabbing of the mouse cursor, when moving it over the QEMU window, works.
However, I'm still wondering, why for other desktop distros I tested as guest system I don't need this option.
Please note the edited part in my last post. I don't think that the problem is a wrong QEMU option or screen resolution, but some wrong/missing configurations in the X server or kernel module options.
As it turns out it was a wrong/missing qemu option
I find that using a minimal startup command for qemu and then building from that works best for me. Usually the defaults work fine. Sorry I could not offer more.
By the way when I had the jumping cursor it was when I was trying to use libvirt/virsh. It went away when I switched back to starting qemu from the command line. Virsh just seems to complicate things. My virtualisation needs are probably simpler than most. I just use it to build/compile new software and test current.
Glad you got it fixed
John
Last edited by AlleyTrotter; 03-25-2015 at 09:05 AM.
why for other desktop distros I tested as guest system I don't need this option.
If I had to guess (notice I said guess) it might be because there is a library, binary, module or driver that already includes the functionality for the mouse automatically.
It may also be something associated with systemd which controls start and stop services and other types of initializations that occur with system functions.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.