Ubuntu Repo's

[Bushido]

I got

Code: Select all

Get:7 https://virtualbox.org:443/virtualbox/debian jammy InRelease [16,8 kB]
Err:7 https://virtualbox.org:443/virtualbox/debian jammy InRelease
  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
Reading package lists... Done        
E: Failed to fetch http://virtualbox.org/virtualbox/debian/dists/jammy/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'http://virtualbox.org/virtualbox/debian jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
when I executed

sudo apt-get update

in Terminal when I tried to do step 4 of method 2 at https://www.redswitches.com/blog/instal ... on-ubuntu/. I am running Ubuntu 22.04 LTS 64-bit.

[scottgus1]

Please tell us exactly what you're trying to do.

[Bushido]

I am trying to fix the error "Kernel driver not installed (rc=1908" after Ubuntu updated kernel by adding a Virtualbox repository to a sources list file with the details from https://www.virtualbox.org/wiki/Linux_Downloads.

I am getting a new error after I added the relevant line to the sources list file:

Code: Select all

Ign:12 https://download.virtualbox.org/virtualbox/debian/dists jammy InRelease
Hit:13 https://download.virtualbox.org/virtualbox/debian jammy InRelease
Err:14 https://download.virtualbox.org/virtualbox/debian/dists jammy Release
  404  Not Found [IP: 184.50.200.91 443]
Reading package lists... Done
N: Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository 'https://download.virtualbox.org/virtualbox/debian jammy InRelease' doesn't support architecture 'i386'
E: The repository 'https://download.virtualbox.org/virtualbox/debian/dists jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[scottgus1]

Thanks! To the best of my knowledge, that error is not fixed by adding the Oracle Repo to your Linux lists.

If I recall correctly, the error comes from having a mix of different versions of Virtualbox installed, and that doesn't work well.

You need to purge the Virtualbox installation from your host (except for the VMs) from your host, then decide if you want the Linux distro's fork or Official Virtualbox from Virtualbox.org.

If you decide to use Official, then adding the Oracle repo can keep you strictly on Official in the future. Also note that Official has prerequisites needed before doing the Official installation https://www.virtualbox.org/manual/ch02. ... nux-prereq

FWIW we only support Official here. The forks get supported on their Linux distro forums.

[Bushido]

...a mix of different versions of Virtualbox installed...

I thought that I need to re-install Virtualbox every time Ubuntu updates Kernel automatically.

I want the official Virtualbox from Virtualbox.org. Where can I install or check if I have already installed the latest Qt and SDL?

Where is step-by-step guide?

By purge, do you mean

Code: Select all

sudo apt-get remove --purge virtualbox 

which preserves virtual machines?

[scottgus1]

Disclaimer: I'm no Linux guru. Here's what I've read so far in the forums:

I thought that I need to re-install Virtualbox every time Ubuntu updates Kernel automatically.

Yes. A new kernel means a new Virtualbox. Virtualbox is often not compatible with kernels released after the version of Virtualbox was released.

Where can I install or check if I have already installed the latest Qt and SDL?

Good question. Presumably these come from the distro, and are merely the things on top of which Official Virtualbox rests. FWIW I think Virtualbox still uses Qt5.

Where is step-by-step guide?

The best we have is the Prerequisites link, which is admittedly vague, because it is written to cover all Linux distros, and there are too many with their own uniquenesses for a comprehensive how-to.

By purge, do you mean...

A reliable, restorable host backup image and other such backups, especially of the VMs' folders, would be a good idea if that's not the correct command.

Hopefully a forum Linux guru can clarify these ideas.

[Bushido]

Yes. A new kernel means a new Virtualbox. Virtualbox is often not compatible with kernels released after the version of Virtualbox was released.

I have now installed VirtualBox 7.0.14 r161095, the software center still suggests me to upgrade to 6.1.48-dfsg-1~ubuntu1.22.04.1.

Code: Select all

virtualbox-dkms/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64 [upgradable from: 6.1.38-dfsg-3~ubuntu1.22.04.1]

Shouldn't it suggest an upgrade to for example 7.0.14-dfsg-1~1.22.04.1?

Good question. Presumably these come from the distro, and are merely the things on top of which Official Virtualbox rests. FWIW I think Virtualbox still uses Qt5.

By installing the latest official one, I managed to get all the dependencies automatically via Ubuntu's package manager or whatever it is called.

[fth0]

I have now installed VirtualBox 7.0.14 r161095, the software center still suggests me to upgrade to 6.1.48-dfsg-1~ubuntu1.22.04.1.

This perhaps indicates that you still have packages from the Ubuntu-provided VirtualBox installed, but I'm not sure. Therefore, use apt search virtualbox and/or dpkg --list virtualbox* to see which packages are currently installed.

The Oracle-provided VirtualBox packages (e.g. virtualbox-6.1, virtualbox-7.0) and the Ubuntu-provided VirtualBox packages (e.g. virtualbox, virtualbox-[a-z]*) do not get along, so you must ensure that you only have VirtualBox packages from one provider installed. Uninstall all currently installed VirtualBox packages (purge isn't necessary) and reboot the host. Then install the VirtualBox packages from one provider only.

[Bushido]

Therefore, use apt search virtualbox and/or dpkg --list virtualbox* to see which packages are currently installed.

apt search virtualbox:

Code: Select all

Sorting... Done
Full Text Search... Done
boinc-virtualbox/jammy 7.18.1+dfsg-4 amd64
  metapackage for virtualbox-savvy projects

fence-agents-extra/jammy-updates 4.7.1-1ubuntu8.1 amd64
  Fence Agents for Red Hat Cluster

imvirt/jammy,jammy 0.9.6-9 all
  detects several virtualizations

imvirt-helper/jammy 0.9.6-9 amd64
  helper programs to detect several virtualizations

libimvirt-perl/jammy,jammy 0.9.6-9 all
  Perl module for detecting several virtualizations

libnss-libvirt/jammy-updates 8.0.0-1ubuntu7.8 amd64
  nss plugins providing IP address resolution for virtual machines

libvirt-clients/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Programs for the libvirt library

libvirt-daemon/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon

libvirt-daemon-config-network/jammy-updates,jammy-updates 8.0.0-1ubuntu7.8 all
  Libvirt daemon configuration files (default network)

libvirt-daemon-config-nwfilter/jammy-updates,jammy-updates 8.0.0-1ubuntu7.8 all
  Libvirt daemon configuration files (default network filters)

libvirt-daemon-driver-lxc/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon LXC connection driver

libvirt-daemon-driver-qemu/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon QEMU connection driver

libvirt-daemon-driver-storage-gluster/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon glusterfs storage driver

libvirt-daemon-driver-storage-iscsi-direct/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon iSCSI (libiscsi) storage driver

libvirt-daemon-driver-storage-rbd/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon RBD storage driver

libvirt-daemon-driver-storage-zfs/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon ZFS storage driver

libvirt-daemon-driver-vbox/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon VirtualBox connection driver

libvirt-daemon-driver-xen/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Virtualization daemon Xen connection driver

libvirt-daemon-system/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Libvirt daemon configuration files

libvirt-daemon-system-systemd/jammy-updates,jammy-updates 8.0.0-1ubuntu7.8 all
  Libvirt daemon configuration files (systemd)

libvirt-daemon-system-sysv/jammy-updates,jammy-updates 8.0.0-1ubuntu7.8 all
  Libvirt daemon configuration files (sysv)

libvirt-dbus/jammy 1.4.1-1ubuntu1 amd64
  libvirt D-Bus API bindings

libvirt-dev/jammy-updates 8.0.0-1ubuntu7.8 amd64
  development files for the libvirt library

libvirt-doc/jammy-updates,jammy-updates 8.0.0-1ubuntu7.8 all
  documentation for the libvirt library

libvirt-login-shell/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Isolate user sessions using LXC containers

libvirt-sanlock/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Sanlock plugin for virtlockd

libvirt-wireshark/jammy-updates 8.0.0-1ubuntu7.8 amd64
  Wireshark dissector for the libvirt protocol

libvirt0/jammy-updates 8.0.0-1ubuntu7.8 amd64
  library for interfacing with different virtualization systems

packer/jammy-updates,jammy-security 1.6.6+ds1-4ubuntu0.22.04.2 amd64
  tool for creating machine images for multiple platforms

python3-libvirt/jammy 8.0.0-1build1 amd64
  libvirt Python 3 bindings

unity-scope-virtualbox/jammy,jammy 0.1+13.10.20130723-0ubuntu3 all
  VirtualBox scope for Unity

vagrant/jammy,jammy 2.2.19+dfsg-1ubuntu1 all
  Tool for building and distributing virtualized development environments

vagrant-lxc/jammy,jammy 1.4.3-2 all
  Linux Containers provider for Vagrant

vagrant-mutate/jammy,jammy 1.2.0-4.1 all
  convert vagrant boxes to work with different providers

vagrant-sshfs/jammy,jammy 1.3.6-1 all
  vagrant plugin that adds synced folder support with sshfs

virtualbox/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64
  x86 virtualization solution - base binaries

virtualbox-7.0/now 7.0.14-161095~Ubuntu~jammy amd64 [installed,local]
  Oracle VM VirtualBox

virtualbox-dkms/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64 [upgradable from: 6.1.38-dfsg-3~ubuntu1.22.04.1]
  x86 virtualization solution - kernel module sources for dkms

virtualbox-ext-pack/jammy-updates,jammy-updates 6.1.48-1~ubuntu1.22.04.1 all
  extra capabilities for VirtualBox, downloader.

virtualbox-guest-additions-iso/jammy-updates,jammy-updates 6.1.48-1~ubuntu1.22.04.1 all
  guest additions iso image for VirtualBox

virtualbox-guest-utils/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64
  x86 virtualization solution - non-X11 guest utilities

virtualbox-guest-utils-hwe/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64
  x86 virtualization solution - non-X11 guest utilities

virtualbox-guest-x11/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64
  x86 virtualization solution - X11 guest utilities

virtualbox-guest-x11-hwe/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64
  x86 virtualization solution - X11 guest utilities

virtualbox-qt/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64
  x86 virtualization solution - Qt based user interface

virtualbox-source/jammy-updates 6.1.48-dfsg-1~ubuntu1.22.04.1 amd64
  x86 virtualization solution - kernel module source

xmount/jammy 0.7.6-3 amd64
  tool for crossmounting between disk image formats

dpkg --list virtualbox*:

Code: Select all

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Nimi                           Versioon                      Architecture Kirjeldus
+++-==============================-=============================-============-============================================================
un  virtualbox                     <none>                        <none>       (kirjeldus pole saadaval)
ii  virtualbox-7.0                 7.0.14-161095~Ubuntu~jammy    amd64        Oracle VM VirtualBox
ii  virtualbox-dkms                6.1.38-dfsg-3~ubuntu1.22.04.1 amd64        x86 virtualization solution - kernel module sources for dkms
un  virtualbox-guest-additions-iso <none>                        <none>       (kirjeldus pole saadaval)
un  virtualbox-guest-modules       <none>                        <none>       (kirjeldus pole saadaval)
un  virtualbox-modules             <none>                        <none>       (kirjeldus pole saadaval)
un  virtualbox-ose                 <none>                        <none>       (kirjeldus pole saadaval)
un  virtualbox-qt                  <none>                        <none>       (kirjeldus pole saadaval)

You mean I have to reinstall the whole thing again, except find somewhere the commands which remove all the packages so that virtual machines created are being untouched?

[fth0]

It should suffice to uninstall the virtualbox-dkms package with sudo apt remove virtualbox-dkms and to reboot the host.

[Bushido]

It should suffice to uninstall the virtualbox-dkms package with sudo apt remove virtualbox-dkms and to reboot the host.

Is the result fine?

Code: Select all

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libgsoap-2.8.117 liblzf1 libsdl1.2debian
Use 'sudo apt autoremove' to remove them.
EEMALDATAKSE järgnevad paketid:
  virtualbox-dkms
0 uuendatud, 0 värskelt paigaldatud, 1 eemaldada ja 7 uuendamata.
Pärast seda tegevust vabaneb 5 725 kB kettaruumi.
Kas sa tahad jätkata? [J/e] J
(Andmebaasi lugemine ... 327487 files and directories currently installed.)
Removing virtualbox-dkms (6.1.38-dfsg-3~ubuntu1.22.04.1) ...
Module virtualbox-6.1.38 for kernel 6.2.0-39-generic (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.2.0-39-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetadp.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.2.0-39-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetflt.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.2.0-39-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod..............
Deleting module virtualbox-6.1.38 completely from the DKMS tree.

Now I am not being prompted to update old DKMS and I have the latest official DKMS for 7.0?

[fth0]

The virtualbox-dkms package belongs only to the Ubuntu-provided VirtualBox and naturally conflicts with the Oracle-provided VirtualBox packages. Especially, you could see that uninstalling this package also uninstalled VirtualBox kernel modules (e.g. vboxdrv.ko) that were your main problem.

The Oracle-provided VirtualBox package virtualbox-7.0 contains everything that's needed, except for general Ubuntu packages like build-essential. In consequence, it brings and builds its own VirtualBox kernel modules (e.g. vboxdrv.ko).

[Bushido]

A new kernel means a new Virtualbox.

If I decide to opt-in for LTS Enablement Stack i.e. HWE in Ubuntu or use the method described in https://ubuntuhandbook.org/index.php/20 ... epository/ and as a result a new kernel is installed, must I have to do something with Virtualbox even if I use the latest official Virtualbox from you?

[scottgus1]

I don't know about all the LTS stuff, but if a new kernel gets installed, you may need a new version of Virtualbox.

FWIW the new version of Virtualbox comes out after the new kernel, so you may be waiting for a while for the new Virtualbox version to come out to support the new kernel. Production hosts with VMs that need to keep running should not get new kernels until a test host confirms that the new kernel and newest Virtualbox available when the kernel came out work well together. We have had reports of Linux users getting the latest kernel then having to wait weeks for a compatible Virtualbox version to be released. Price of being on the bleeding edge, I guess. "If it ain't broke don't fix it" is a decent paradigm to follow.

[fth0]

if a new kernel gets installed, you may need a new version of Virtualbox.

To elaborate a bit on that:

When the Linux kernel gets updated, the installed VirtualBox automatically tries to rebuild its kernel drivers. In the case of Linux kernel patch updates (e.g. 6.3.1 to 6.3.2), this works without problems most of the time. But in the case of Linux kernel major/minor updates (e.g. 6.3.x to 6.4.y), often some Linux kernel interfaces change, and the installed VirtualBox version cannot foresee that, so you need a newer VirtualBox version in that case.