Mouse & Keyboard completely unresponsive when starting a VM

[Enigma]

Could be virt-manager or gnome-shell related.

I was passing through 1 USB device that wasn't my main mouse or keyboard. Otherwise pretty normal configuration that I've used before.

After the VM's bios screen, the whole system froze except the clock in the desktop menu bar/panel.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
Uname: Linux 4.15.1-041501-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 23:47:02 2018
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-27 (112 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Gustavo Silva (gsilvapt)]

Which VM software are you using? It could be an upstream issue instead of Ubuntu's.

[Enigma (enigma0)]

:~$ virt-manager --version
1.4.0

[Daniel van Vugt (vanvugt)]

Your VM's logs mention a lot about finding Razer input devices, but also:
"No input driver specified, ignoring this device."

So this might be a bug in package 'xserver-xorg-input-libinput'. Can you install xserver-xorg-input-evdev in the VM by some means?

[Enigma (enigma0)]

I'm not sure but can try. The issue is that the system freezes when trying to start the VM at all so it doesn't get far enough.

Are you sure you don't mean to install the -evdev package in the host?

[Daniel van Vugt (vanvugt)]

I'm talking about changing the driver in the guest, on the assumption this bug was reported from the guest (which is what we need). However now that you mention it, you probably reported this from the host so the above logs would be misleading and probably irrelevant...

If that's correct then unfortunately we'll need to leave the status as Incomplete until someone can figure out how to get some useful information out of the VM/guest itself.

[Enigma (enigma0)]

Yeah 'guest' for me means VM running on a host. That VM system is unable to start so I wouldn't be able to gather or report anything from there.

[Daniel van Vugt (vanvugt)]

If you can boot up the VM, reproduce the problem and then remove the offending input devices you might be able to interact with the VM and report this bug from within it.

[Launchpad Janitor (janitor)]

[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]