Package 'linux-headers-5.15.0-67-generic' has no installation candidate m linux-headers-5.15.0-67-generic

lukasz-gorski · June 2, 2023, 7:46am

Hi.

After Update Mac to 13.4, Vagrant to v2.3.6 (latest version), Parallels 18.3.0 (latest version) I’m not able to start existing ubuntu 22.04 projects. Also trellis new throws the same error.

==> default: Checking for Parallels Tools installed on the VM…
==> default: Parallels Tools installed on this VM are outdated! In most cases
==> default: this is fine but in rare cases it can cause things such as shared
==> default: folders to not work properly. If you see shared folder errors,
==> default: please update Parallels Tools within the virtual machine and
==> default: reload your VM.
==> default: Installing the proper version of Parallels Tools. This may take a few minutes…
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ptiagent-cmd --install

Stdout from the command:

ptiagent-cmd progress 3
ptiagent-cmd progress 15
Started installation of Parallels Guest Tools version ‘18.3.0.53606’
…
Running kernel seems to be up-to-date.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
E: Package ‘linux-headers-5.15.0-67-generic’ has no installation candidate
m linux-headers-5.15.0-67-generic
o dkms
o libelf-dev
Error: failed to install mandatory packages.
Error: failed to install or upgrade Parallels Guest Tools!
Stderr from the command:
exit status 1

Has anyone faced that issue to and is there any possible fix?

Thank you.

strarsis · June 3, 2023, 5:05pm

So I can summarize the issue like this:

macOS 13.4 with Parallels 18.3.0, controlled by Vagrant 2.3.6, starting an existing Ubuntu 22.04 inside a VM.
Vagrant script detects that the Parallel Tools (Guest Additions/Tools) on that Ubuntu system inside the VM is outdated, tries updating it.
The Parallel Tools use kernel modules, those have to be build (compiled) for the given Linux kernel used by Ubuntu 22.04.
For building those kernel modules, the Linux header files are needed (for ABI compatibility and so on).
Those Linux header files are usually provided by an Ubuntu package, using the naming scheme linux-headers-<version+variant>, 5.15.0-67-generic for this Ubuntu system.
apt can not find an Ubuntu package under that name on that system, hence the Parallel Tools update step fails.

That Linux headers package is available for Ubuntu jammy (which codename is for Ubuntu 22.04 LTS):

The package is under security, so the sources on that Ubuntu system should contain the security repository. Here is the list of repositories for Ubuntu 22.04:
https://wiki.ubuntuusers.de/sources.list/#Ubuntu-22-04

deb http://de.archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverse

So you can manually SSH into the Vagrant box with that issue and check for yourself whether that source is in there and is picked up by apt.

Alternatively, you could try to skip the Parallels Tool update step until the underlying issue has been addressed, it may still work fine.

Edit: Trellis (recent v121.0) uses arm64 arch for Apple Silicon:
https://github.com/roots/trellis/blob/02cfc360911c545611d624c01ce4d97f197c6d00/Vagrantfile#L26
The linux-headers-5.15.0-73-generic package is only listed for arch amd64, this may be the underlying issue.

There are Linux header packages for more than only this particular Linux kernel version (https://packages.ubuntu.com/jammy/devel/).
The linux-headers-5.15.0-25-generic (so for kernel version 5.15.0-73, not for kernel version 5.15.0-73 the Ubuntu system in your setup is using right now) package is also available for arm64:
https://packages.ubuntu.com/jammy/devel/linux-headers-5.15.0-25-generic

Can you update the kernel in your Ubuntu VM to 5.15.0-73, does it work then?
This, of course, is based on the assumption that you are using macOS on Apple Silicon (as M1 or M2 hardware). macOS 13.4 can also run on non-Apple Silicon (Intel) as by the official compatible hardware list.

MWDelaney · June 8, 2023, 1:57pm

If it’s interesting, I’m having this issue on new Trellis installs on an M1 Mac as well. For now I’m bumping this line down to 20.04 to get around it.

github.com

roots/trellis/blob/5642f8658dc8463a8b2aa6c65fdb7f2bb427cbe0/vagrant.default.yml#L5


      
          ---
          vagrant_ip: '192.168.56.5'
          vagrant_cpus: 1
          vagrant_memory: 1024 # in MB
          vagrant_box: 'bento/ubuntu-22.04'
          vagrant_box_version: '>= 0'
          vagrant_box_auto_arch: true
          vagrant_ansible_version: '2.10.7'
          vagrant_skip_galaxy: false
          vagrant_mount_type: 'nfs'
          vagrant_nfs_udp: false
          vagrant_require_version: '>= 2.1.0'
          
          
vagrant_install_plugins: true
          vagrant_plugins:

artshostak · June 23, 2023, 7:21pm

Having the same issue, would love to see what workarounds we have for 22.04 but for now just using the same tactic as @MWDelaney to use 20.04 instead.

ben · June 24, 2023, 7:35pm

Tracking the bug here: https://github.com/roots/trellis/issues/1495

swalkinshaw · June 25, 2023, 7:56pm

Can someone try changing this line to false and see if it avoids the issue?

github.com

roots/trellis/blob/c9f4dd918cb0a708b298c506785b09c7e0e80e3a/Vagrantfile#L195


      
              vmw.vmx['numvcpus'] = vconfig.fetch('vagrant_cpus')
              vmw.vmx['memsize'] = vconfig.fetch('vagrant_memory')
            end
          end
          
          
# Parallels settings
          config.vm.provider 'parallels' do |prl|
            prl.name = config.vm.hostname
            prl.cpus = vconfig.fetch('vagrant_cpus')
            prl.memory = vconfig.fetch('vagrant_memory')
            prl.update_guest_tools = true
          
          
  # Parallels handles DNS resolution itself when used in conjunction with landrush
            if Vagrant.has_plugin?('landrush') && trellis_config.multisite_subdomains?
              config.landrush.guest_redirect_dns = false
            end
          end
          
          
# Hyper-V settings
          config.vm.provider 'hyperv' do |h|
            h.vmname = config.vm.hostname

If it does “work”, I’m not sure what the downside is to having outdated guest tools.

Twansparant · July 10, 2023, 6:53pm

Setting update_guest_tools to false fixes it for me!