[SOLVED] Debian bullseye VM - noVNC mouse not working

[djgraff209]

I'm having difficulty with Debian VMs running bullseye with either GDM3 or lightdm installed.

I have posted screen shots of the hardware, options, and console below.

I can manipulate the screen through keyboard interaction with the console but am unable to get the mouse to respond.

The VM is as plain as it can get using just the task selection for the desktop environment.

I have tried this with Windows 10 Chrome (98.0.4758.102) and Edge (98.0.1108.56) with no success.

UPDATE 14:55 ET - I have configured the VM for a spice display. The VM boots up fine and I can get to the spice session using virt-viewer however when the viewer captures the mouse it doesn't move. I have keyboard input but no mouse movement.

Any help or suggestions are greatly appreciated!

Hardware:


Options:


Console:

 

[djgraff209]

FOUND IT!!!

OK - so this is a bit dumb and in hind sight makes total sense.

So my debian image was built with a script

RELEASE=bullseye

build-openstack-debian-image \
        -r ${RELEASE} \
        --output debian-${RELEASE}-amd64 \
        --architecture amd64 \
        --extra-packages "qemu-guest-agent,tmux,bash-completion" \
        --image-size 8

In the clone of the template from this image I installed the desktop using the task-gnome-desktop. This image utilizes the linux-image-X.Y.Z-zz-cloud-amd64 kernel which does not include the USB drivers. As a result the USB tablet device used as the mouse input cannot be detected.

After fouling up my configuration a number of times and nuking about 5 different VMs (they're disposable so yay me!) I started finding the pattern of the missing input device and after chasing down the usbutils, pciutils, and input-utils packages I started to get the picture sorted out.

I installed the latest kernel image (non cloud) linux-image-X.Y.Z-zz-amd64 which includes all of the necessary kernel modules, got it booted and voila it worked!

In short, if you install from an ISO rather than a "cloud" image, you most likely will have the full kernel and not have these tribulations.

I hope that other users who have encountered this can benefit from my naivety!

POSTSCRIPT

I looked back at the build-openstack-debian-image. It has an option --no-cloud-kernel which will install the full kernel rather than the more minimal cloud kernel.