Mouse and keyboard not working after upgrade of virtualbox and guest additions on Debian guest

[LorenzoM]

I'm using the Debian Jessie 8.2 guest on virtualbox from Windows 10 host. Today I updgraded virtualbox to 5.0.20 version, and everything worked fine on the Debian guest. I downloaded the VBoxGuestAdditions version 5.0.16, installed the linux guest addition on the Debian Jessie guest and on the following boot of the virtualmachine the mouse and keyboard don't work. I tried to re-capture the mouse many times but nothing happened. I also tried to apply the solution of writing dconf write /org/gnome/settings-daemon/plugins/cursor/active false in the command line of the recovery session of linux but it didn't help anyway.
I should be able to resume the correct use of my debian jessie guest as I saved so many configurations there.

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

As well as the following:

From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

[LorenzoM]

Here it is the guest log file as an attachment, while the response to the vminfo is the following:

Code: Select all

"Name:            Debian 8.2 Jessie
Groups:          /
Guest OS:        Debian (64-bit)
UUID:            4b6c8b8d-438e-40e3-aa2c-0abfd68ea277
Config file:     C:\Users\loren\VirtualBox VMs\Debian 8.2 Jessie\Debian 8.2 Jessie.vbox
Snapshot folder: C:\Users\loren\VirtualBox VMs\Debian 8.2 Jessie\Snapshots
Log folder:      C:\Users\loren\VirtualBox VMs\Debian 8.2 Jessie\Logs
Hardware UUID:   4b6c8b8d-438e-40e3-aa2c-0abfd68ea277
Memory size:     8192MB
Page Fusion:     off
VRAM size:       64MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
State:           powered off (since 2016-06-11T20:01:16.748000000)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
IDE (1, 0): C:\Program Files\Oracle\VirtualBox/VBoxGuestAdditions.iso (UUID: 32863984-e9db-411f-8070-762497c3f421)
SATA (0, 0): C:\VB_Images\Debian 8.2 (64bit).vdi (UUID: 9b1640f9-793c-43cb-9eb7-81eadb08a0c9)
NIC 1:           MAC: 080027BFCF44, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: DSOUND, Controller: AC97, Codec: AD1980)
Clipboard Mode:  Bidirectional
Drag and drop Mode: disabled
VRDE:            disabled
USB:             disabled
EHCI:            disabled
XHCI:            enabled

USB Device Filters:

Index:            0
Active:           yes
Name:             Nuovo filtro 1
VendorId:
ProductId:
Revision:
Manufacturer:
Product:
Remote:
Serial Number:

Bandwidth groups:  <none>

Shared folders:

Name: 'share', Host path: 'C:\VB_Images\share' (machine mapping), writable

Video capturing:    not active
Capture screens:    0
Capture file:       C:\Users\loren\VirtualBox VMs\Debian 8.2 Jessie\Debian 8.2 Jessie.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB"

[Perryg]

The log shows you have mounted the guest additions in the virtual CD/DVD but does not show that they are actually installed. Can you use the host+F1 hot key to drop to a tty window? If not then can you boot to recovery, and does the keyboard work there?

[LorenzoM]

On the recovery boot of linux I can write with the keyboard to the bash with root access.

[Perryg]

OK so the keyboard does work in recovery mode. Doest Host+F1 work or not?

Also what is the "Nuovo filtro 1" USB device you have a filter for?

[LorenzoM]

Host+F1 doesn't work. "Nuovo filtro USB" is a USB filter I created some weeks ago for passing USB devices to the guest because I couldn't see a hard drive in the guest Linux. Don't know if it's useless but it didn't create any problem during its permanence.

[Perryg]

The thing is the guest additions have no effect on the keyboard. It might cause eradicate mouse behaviour but the keyboard should still work.

Try disabling the USB filter and see if that helps. Also think about what else might have changed around the same time this all started.

[LorenzoM]

I also tried to uninstall the guest additions before posting the issue in this forum, from command line in recovery mode, this could be why you can't see them as installed.

[LorenzoM]

Some more information. When Linux is starting some FAIL messages appear during the boot of the system, e.g., "failed to start vboxadd.service" and another one "failed to start load kernel modules". Anyway Linux can start, the main login screen appears, but I'm not able to capture the mouse. I actually don't know if the keyboard is working or not, but nothing happens for any pushed button. I'm sure it's working only in recovery mode.

[Perryg]

You need to boot into recovery and then enable the shell to work on the guest. Then try mounting the cd and manually install the guest additions.
mount /dev/sr0 /mnt
then run
sh ./VBoxLinuxAdditions.run
from the folder

[LorenzoM]

I have no sr0 element in /dev

[Perryg]

That is a zero, just in case you though it was a cap O. Anyway it was a shot to see if it would help. Like I said the additions would not have anything to do with the keyboard.

Did you disable the USB filter?

[LorenzoM]

Yes, I know it is a zero : ).
Yes, I removed the USB filter.

[Perryg]

Every Debian based OS I have ever had there was a /dev/sr0 which is the cd, Something is definitely wrong with the guest but I can't work on it remotely. Try creating another guest and see if it responds the same. You need to find out what actually is causing this since I have not seen any other reports of weird behaviour like this that was not self inflicted.