Your message dated Tue, 18 Nov 2014 23:45:43 +0100 with message-id <[email protected]> and subject line Re: Bug#769967: virtualbox-guest-utils: Starting VirtualBox Additions No suitable module for running kernel found ... failed! has caused the Debian Bug report #769967, regarding virtualbox-guest-utils: Starting VirtualBox Additions No suitable module for running kernel found ... failed! to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 769967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769967 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: virtualbox-guest-utils Version: 4.3.18-dfsg-1 Severity: grave Justification: renders package unusable I have two Debian installations running as guests in a VirtualBox installation. One is stable, the other one testing. Both have virtual-guest-utils and virtual-guest-dkms packages installed. In stable the host time sync works, in testing it does not. Here is what can be found in the system log after an attempt to start the virtual-guest-utils service: // log extract begins nov 10 01:36:47 debian-systemd sudo[1429]: tomfa : TTY=pts/0 ; PWD=/home/tomfa ; USER=root ; COMMAND=/usr/sbin/service virtualbox-guest-utils start nov 10 01:36:47 debian-systemd sudo[1429]: pam_unix(sudo:session): session opened for user root by tomfa(uid=0) nov 10 01:36:47 debian-systemd virtualbox-guest-utils[1447]: Starting VirtualBox AdditionsNo suitable module for running kernel found ... failed! nov 10 01:36:47 debian-systemd virtualbox-guest-utils[1447]: failed! nov 10 01:36:47 debian-systemd sudo[1429]: pam_unix(sudo:session): session closed for user root nov 10 01:36:47 debian-systemd systemd[1]: virtualbox-guest-utils.service: control process exited, code=exited status=1 nov 10 01:36:47 debian-systemd systemd[1]: Failed to start LSB: VirtualBox Linux Additions. // log extract ends It seems like the vboxguest kernel module is not loading correctly. Please give advice on possible workaround or if you need further details. Thank you for providing these packages. Looking forward to a solution. Tomas Fasth -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/1 CPU core) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox-guest-utils depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.21 ii libc6 2.19-12 ii libpam0g 1.1.8-3.1 ii pciutils 1:3.2.1-3 Versions of packages virtualbox-guest-utils recommends: ii virtualbox-guest-dkms 4.3.18-dfsg-1 ii virtualbox-guest-x11 4.3.18-dfsg-1 virtualbox-guest-utils suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Gianfranco, Gianfranco Costamagna skrev 2014-11-18 08:06: > Hi Tomas, > > did you upgrade your virtualbox extension pack? did virtualbox run the > vboxdrv setup? did you change your kernel? > > I see in your log a "no suitable kernel module found" Yeah, I followed up on the last one, and found the following: tomfa@debian-systemd:~$ sudo aptitude search linux-headers v linux-headers v linux-headers-2.6 i linux-headers-3.16 p linux-headers-3.16.0-4-all p linux-headers-3.16.0-4-all-amd64 p linux-headers-3.16.0-4-amd64 p linux-headers-3.16.0-4-common p linux-headers-amd64 After purging linux-headers-3.16, doing an "aptitude update/upgrade" and installing linux-headers-amd64 it now looks like this: tomfa@debian-systemd:~$ sudo aptitude search linux-headers p linux-headers-3.16.0-4-all p linux-headers-3.16.0-4-all-amd64 i A linux-headers-3.16.0-4-amd64 i A linux-headers-3.16.0-4-common i linux-headers-amd64 And when reinstalling virtualbox-guest-dkms it looks better: vboxguest: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-4-amd64/updates/dkms/ After reboot, the service is now running: tomfa@debian-systemd:~$ sudo systemctl status virtualbox-guest-utils.service ● virtualbox-guest-utils.service - LSB: VirtualBox Linux Additions Loaded: loaded (/etc/init.d/virtualbox-guest-utils) Active: active (running) since tis 2014-11-18 13:25:41 CET; 9h ago Process: 420 ExecStart=/etc/init.d/virtualbox-guest-utils start (code=exited, status=0/SUCCESS) CGroup: /system.slice/virtualbox-guest-utils.service └─439 /usr/sbin/VBoxService The linux-headers-3.16 package seem now to have been dropped from testing, which indicates that my system was left in a broken state due to some package transition mishap. Anyway, problem solved, moving on. Thank you for a nice packaging of virtualbox. - -- Tomas Fasth <[email protected]> -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlRrzBcACgkQwYdzVZ/o1QTglwCZAev49z4dL7pa3pCLwlMU7GbO MbIAnRlmVrqgNyD+o581HK5gTfFWji3J =hZJJ -----END PGP SIGNATURE-----
--- End Message ---
