LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware in QEMU - jumping mouse cursor in X when using vmware graphics driver (https://www.linuxquestions.org/questions/slackware-14/slackware-in-qemu-jumping-mouse-cursor-in-x-when-using-vmware-graphics-driver-4175537658/)

slacksam 03-23-2015 07:15 PM

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.

Ztcoracat 03-23-2015 10:26 PM

Hi:

Is there a smart mouse feature in QEMU?
Maybe adjust that.

You might want to give Virtual Box a try.
It's running Arch and Mageia flawlessly for me.

http://www.linuxquestions.org/questi...al-4175500846/

veerain 03-23-2015 11:43 PM

Is there any particular requirement to use vmware graphics? You can use cirrus or plain vesa video graphics. They work good.

slacksam 03-24-2015 03:59 AM

Quote:

Originally Posted by Ztcoracat
Is there a smart mouse feature in QEMU?

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.

AlleyTrotter 03-24-2015 08:03 AM

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.

slacksam 03-24-2015 10:17 AM

Hi AlleyTrotter,

I'm using a Logitech PS/2 mouse over a Belkin LVM switch.
The starting commands für QEMU look like:
Code:

qemu-system-i386 -monitor stdio -cpu qemu32 -soundhw es1370 -k de -vga vmware -enable-kvm -m 700 -no-fd-bootchk -localtime -hda /home/sam/qemu/slackware.qcow2 -boot once=d,menu=off -net nic,vlan=0 -net user,vlan=0 -name "Slackware"
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.

AlleyTrotter 03-24-2015 02:05 PM

Code:

qemu-system-i386 -cpu qemu32 -soundhw es1370 -k de -vga vmware -enable-kvm -m 700 -localtime -hda /home/sam/qemu/slackware.qcow2
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.

slacksam 03-24-2015 03:09 PM

Quote:

Originally Posted by AlleyTrotter
Code:

qemu-system-i386 -cpu qemu32 -soundhw es1370 -k de -vga vmware -enable-kvm -m 700 -localtime -hda /home/sam/qemu/slackware.qcow2
...
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.

fdonkers 03-24-2015 07:08 PM

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:

Code:

-device usb-tablet,id=input0

slacksam 03-25-2015 02:26 AM

@fdonkers
Thanks, the option
Code:

-usbdevice tablet
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.

AlleyTrotter 03-25-2015 08:59 AM

Quote:

Originally Posted by slacksam (Post 5337135)
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

Ztcoracat 03-25-2015 10:20 PM

Quote:

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.

Weber Kai 03-13-2017 03:34 AM

Sorry to post in an old entry, but I came from google looking for these same answers to same problems, and I would like to contribute.

But I am using virt-manager, so I can't edit command line.

In both guests 14.1 and 14.2 I solved the mouse offset issue by editing file /usr/share/X11/xorg.conf.d/05-qxl.conf and removing these lines:

Code:

# Prevent udev from loading vmmouse in a vm and crashing.
Section "ServerFlags"
    Option "AutoAddDevices" "False"
EndSection

Thank you!

Ztcoracat 03-13-2017 11:26 AM

Quote:

Originally Posted by Weber Kai (Post 5682769)
Sorry to post in an old entry, but I came from google looking for these same answers to same problems, and I would like to contribute.

But I am using virt-manager, so I can't edit command line.

In both guests 14.1 and 14.2 I solved the mouse offset issue by editing file /usr/share/X11/xorg.conf.d/05-qxl.conf and removing these lines:

Code:

# Prevent udev from loading vmmouse in a vm and crashing.
Section "ServerFlags"
    Option "AutoAddDevices" "False"
EndSection

Thank you!

Thanks for posting a solution.


All times are GMT -5. The time now is 12:55 PM.