Hi, everyone,
I need to use Kubernetes, but can't start minikube due to a viturlbox issue. I had an old version of vitualbox installed a few years ago. After removing the old one, I can't install the latest version. The followings are the output with the installation.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
oem@oem-Vostro-270s ~ $ sudo apt-get install virtualbox
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libgsoap8 libvncserver1 virtualbox-dkms
Suggested packages:
vde2 virtualbox-guest-additions-iso
Recommended packages:
virtualbox-qt
The following NEW packages will be installed:
libgsoap8 libvncserver1 virtualbox virtualbox-dkms
0 upgraded, 4 newly installed, 0 to remove and 64 not upgraded.
Need to get 16.8 MB of archives.
After this operation, 79.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 libgsoap8 amd64 2.8.28-1 [216 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libvncserver1 amd64 0.9.10+dfsg-3ubuntu0.16.04.3 [122 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 virtualbox-dkms all 5.1.38-dfsg-0ubuntu1.16.04.3 [651 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 virtualbox amd64 5.1.38-dfsg-0ubuntu1.16.04.3 [15.8 MB]
Fetched 16.8 MB in 3s (5,548 kB/s)
Selecting previously unselected package libgsoap8:amd64.
(Reading database ... 428844 files and directories currently installed.)
Preparing to unpack .../libgsoap8_2.8.28-1_amd64.deb ...
Unpacking libgsoap8:amd64 (2.8.28-1) ...
Selecting previously unselected package libvncserver1:amd64.
Preparing to unpack .../libvncserver1_0.9.10+dfsg-3ubuntu0.16.04.3_amd64.deb ...
Unpacking libvncserver1:amd64 (0.9.10+dfsg-3ubuntu0.16.04.3) ...
Selecting previously unselected package virtualbox-dkms.
Preparing to unpack .../virtualbox-dkms_5.1.38-dfsg-0ubuntu1.16.04.3_all.deb ...
Unpacking virtualbox-dkms (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Selecting previously unselected package virtualbox.
Preparing to unpack .../virtualbox_5.1.38-dfsg-0ubuntu1.16.04.3_amd64.deb ...
Unpacking virtualbox (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (229-4ubuntu21.23) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libgsoap8:amd64 (2.8.28-1) ...
Setting up libvncserver1:amd64 (0.9.10+dfsg-3ubuntu0.16.04.3) ...
Setting up virtualbox-dkms (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Loading new virtualbox-5.1.38 DKMS files...
First Installation: checking all kernels...
Building only for 4.4.0-173-generic
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Setting up virtualbox (5.1.38-dfsg-0ubuntu1.16.04.3) ...
vboxweb.service is a disabled or a static unit, not starting it.
Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2020-02-29 09:30:11 PST; 6ms ago
Docs: man:systemd-sysv-generator(8)
Process: 11650 ExecStop=/etc/init.d/virtualbox stop (code=exited, status=0/SUCCESS)
Process: 11665 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: * Loading VirtualBox kernel modules...
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: * No suitable module for running kernel found
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: ...fail!
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Control process exited, code=exited...us=1
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Unit entered failed state.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
Processing triggers for systemd (229-4ubuntu21.23) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libgsoap8 libvncserver1 virtualbox-dkms
Suggested packages:
vde2 virtualbox-guest-additions-iso
Recommended packages:
virtualbox-qt
The following NEW packages will be installed:
libgsoap8 libvncserver1 virtualbox virtualbox-dkms
0 upgraded, 4 newly installed, 0 to remove and 64 not upgraded.
Need to get 16.8 MB of archives.
After this operation, 79.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 libgsoap8 amd64 2.8.28-1 [216 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libvncserver1 amd64 0.9.10+dfsg-3ubuntu0.16.04.3 [122 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 virtualbox-dkms all 5.1.38-dfsg-0ubuntu1.16.04.3 [651 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 virtualbox amd64 5.1.38-dfsg-0ubuntu1.16.04.3 [15.8 MB]
Fetched 16.8 MB in 3s (5,548 kB/s)
Selecting previously unselected package libgsoap8:amd64.
(Reading database ... 428844 files and directories currently installed.)
Preparing to unpack .../libgsoap8_2.8.28-1_amd64.deb ...
Unpacking libgsoap8:amd64 (2.8.28-1) ...
Selecting previously unselected package libvncserver1:amd64.
Preparing to unpack .../libvncserver1_0.9.10+dfsg-3ubuntu0.16.04.3_amd64.deb ...
Unpacking libvncserver1:amd64 (0.9.10+dfsg-3ubuntu0.16.04.3) ...
Selecting previously unselected package virtualbox-dkms.
Preparing to unpack .../virtualbox-dkms_5.1.38-dfsg-0ubuntu1.16.04.3_all.deb ...
Unpacking virtualbox-dkms (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Selecting previously unselected package virtualbox.
Preparing to unpack .../virtualbox_5.1.38-dfsg-0ubuntu1.16.04.3_amd64.deb ...
Unpacking virtualbox (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (229-4ubuntu21.23) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libgsoap8:amd64 (2.8.28-1) ...
Setting up libvncserver1:amd64 (0.9.10+dfsg-3ubuntu0.16.04.3) ...
Setting up virtualbox-dkms (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Loading new virtualbox-5.1.38 DKMS files...
First Installation: checking all kernels...
Building only for 4.4.0-173-generic
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Setting up virtualbox (5.1.38-dfsg-0ubuntu1.16.04.3) ...
vboxweb.service is a disabled or a static unit, not starting it.
Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2020-02-29 09:30:11 PST; 6ms ago
Docs: man:systemd-sysv-generator(8)
Process: 11650 ExecStop=/etc/init.d/virtualbox stop (code=exited, status=0/SUCCESS)
Process: 11665 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: * Loading VirtualBox kernel modules...
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: * No suitable module for running kernel found
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: ...fail!
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Control process exited, code=exited...us=1
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Unit entered failed state.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
Processing triggers for systemd (229-4ubuntu21.23) ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
And the followins are the output of the command "journalctl -xe":
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ $ journalctl -xe
--
-- The start-up result is done.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Stopping LSB: VirtualBox Linux kernel module...
-- Subject: Unit virtualbox.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualbox.service has begun shutting down.
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11650]: * Unloading VirtualBox kernel modules...
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11650]: ...done.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Stopped LSB: VirtualBox Linux kernel module.
-- Subject: Unit virtualbox.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualbox.service has finished shutting down.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Unit entered failed state.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Starting LSB: VirtualBox Linux kernel module...
-- Subject: Unit virtualbox.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualbox.service has begun starting up.
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: * Loading VirtualBox kernel modules...
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: * No suitable module for running kernel found
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: ...fail!
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Control process exited, code=exited status
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
-- Subject: Unit virtualbox.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualbox.service has failed.
--
-- The result is failed.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Unit entered failed state.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Feb 29 09:30:12 oem-Vostro-270s systemd[1]: Reloading.
Feb 29 09:30:12 oem-Vostro-270s systemd[1]: Started ACPI event daemon.
-- Subject: Unit acpid.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit acpid.service has finished starting up.
--
-- The start-up result is done.
Feb 29 09:30:12 oem-Vostro-270s systemd[1]: Started CUPS Scheduler.
-- Subject: Unit cups.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cups.service has finished starting up.
--
-- The start-up result is done.
Feb 29 09:30:13 oem-Vostro-270s sudo[10767]: pam_unix(sudo:session): session closed for user root
Feb 29 09:31:26 oem-Vostro-270s sudo[11731]: oem : TTY=pts/0 ; PWD=/home/oem ; USER=root ; COMMAND=/b
Feb 29 09:31:26 oem-Vostro-270s sudo[11731]: pam_unix(sudo:session): session opened for user root by (uid=
Feb 29 09:31:26 oem-Vostro-270s sudo[11731]: pam_unix(sudo:session): session closed for user root
lines 2081-2139/2139 (END)
--
-- The start-up result is done.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Stopping LSB: VirtualBox Linux kernel module...
-- Subject: Unit virtualbox.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualbox.service has begun shutting down.
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11650]: * Unloading VirtualBox kernel modules...
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11650]: ...done.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Stopped LSB: VirtualBox Linux kernel module.
-- Subject: Unit virtualbox.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualbox.service has finished shutting down.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Unit entered failed state.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Starting LSB: VirtualBox Linux kernel module...
-- Subject: Unit virtualbox.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualbox.service has begun starting up.
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: * Loading VirtualBox kernel modules...
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: * No suitable module for running kernel found
Feb 29 09:30:11 oem-Vostro-270s virtualbox[11665]: ...fail!
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Control process exited, code=exited status
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
-- Subject: Unit virtualbox.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit virtualbox.service has failed.
--
-- The result is failed.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Unit entered failed state.
Feb 29 09:30:11 oem-Vostro-270s systemd[1]: virtualbox.service: Failed with result 'exit-code'.
Feb 29 09:30:12 oem-Vostro-270s systemd[1]: Reloading.
Feb 29 09:30:12 oem-Vostro-270s systemd[1]: Started ACPI event daemon.
-- Subject: Unit acpid.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit acpid.service has finished starting up.
--
-- The start-up result is done.
Feb 29 09:30:12 oem-Vostro-270s systemd[1]: Started CUPS Scheduler.
-- Subject: Unit cups.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cups.service has finished starting up.
--
-- The start-up result is done.
Feb 29 09:30:13 oem-Vostro-270s sudo[10767]: pam_unix(sudo:session): session closed for user root
Feb 29 09:31:26 oem-Vostro-270s sudo[11731]: oem : TTY=pts/0 ; PWD=/home/oem ; USER=root ; COMMAND=/b
Feb 29 09:31:26 oem-Vostro-270s sudo[11731]: pam_unix(sudo:session): session opened for user root by (uid=
Feb 29 09:31:26 oem-Vostro-270s sudo[11731]: pam_unix(sudo:session): session closed for user root
lines 2081-2139/2139 (END)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks for all your help in advance.
- v
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
