Suse 8.2 mouse problem on kvm

Having a ‘back to the roots fun project’. I’m running my very first Linux on a vm but Mouse doesn’t work at all.
Any idea how to fix?

Likely a kernel support issue with using such an old distro. You may be better off trying a type 2 VM such as VirtualBox perhaps. (In particular VB supports PS/2 mouse emulation which may be more compatible with such an old OS.)

KVM is a type 2 hypervisor based virtualizaion.

Is this an PpenSuSE 8.2 or a SUSE 8.2 (paid support at the time or not)?

You shouldn’t have any problem as long as it’s an x86 distribution.
When you say you have mouse problems, what about your other input, particularly keyboard?
Is your screen resolution set to 640x480?.. I imagine releases at the time didn’t support anything better

Is your keyboard and mouse working fine on your HostOS?


I don’t think there ever was an “openSUSE 8.2”. As far as I know, openSUSE started with 10.2 or 10.3.

that’s correct

You may have to grab the cursor manually. IIRC I saw that when I did a similar experiment some years ago.

Actually not so.

10.x were the first versions of the completely re-built OS by Novell.


Don’t know about openSuse/10.x but 8.2 was “Suse”.

And, just from memory: Did sax2 exist in 8.2 ? IIRC I had to run it to get some X stuff running at the time. It would create an xorg.conf.


That’s debatable (depending on the definition used) IMO. Many references describe the kernel virtual module as a type 1 hypervisor because systems-level virtualization services are provided as part of the running kernel. This module provides allows the Linux kernel to act as type 1 bare-metal hypervisor, (while the overall system from a host OS perspective might be seen as type 2 with other VM’s treated as standard Linux processes from its perspective). In any case, it would be interesting to see if another VM environment would better support the legacy guest OS.

Good point - quite likely that some manual configuration would be needed. This version is before my time - I was still playing with RH back around then. :slight_smile:

There is no debate and there should really be no lack of clarity.

Your first link contains an accurate description of the difference between a Type1 and a Type2, but then in his own words “blathers” on spouting nonsense. Why didn’t he just stick to what he quoted, or maybe he didn’t understand it?

The second reference is just plain nonsense.
He quotes Oracle Sparc, which is indeed a close cousin of Xen (and Oracle virtualization also natively supports Xen likely because of their similarity), but ESXi, Hyper-V and KVM are clearly Type 2…
You can’t install ESXi without VMware’s custom *NIX stub.
You can’t install Hyper-V without Windows Server Core.
You can’t install KVM without a HostOS, most often Linux but has been ported to other platforms. But no matter what version of KVM you might install, you can’t install it without first installing a HostOS and using Linux kernel components.

The clearest way to identify a Type1 hypervisor is to simply look at an architectural picture, if you see a Dom0 or its equivalent running as its own completely isolated environment, then it’s a Type1. Type2 hypervisors implement as part of a HostOS, not fully isolated in the same way that a Dom0 is from DomU VMs.

View the following and see the difference, the Type2 hypervisor does not have a Dom0 or anything that could even remotely be equivalent.
The important thing to know and remember is that Xen is practically alone as a Type1 hypervisor, every other popular hypervisor does not have a Dom0 and are close cousins as Type2 hypervisors… So, essentially if you learn one Type2 hypervisor, you’ll find that if you find yourself using any other hypervisor except for Xen, things will look very similar.


I’m already familiar with VMs in general without the lecture thanks (unless you’re just sharing for the benefit from others). I’d still be interested in seeing how running the legacy guest in a VirtualBox environment might go.

Took a short look at this, possibly most relevant reference to install SUSE Linux 8.2 is in the following post

It seems that it is an i386, which means it <may> run in an x86 (32-bit) VM, and if not then in a QEMU i386 VM.

IMO the big question though should start with whether everything else works… ie keyboard, display, disks.
I find it hard to believe that mouse input has changed at all since the beginning of time.