Closed mpdude closed 1 year ago
When I set prl.update_guest_tools = off
, the inital boot works. But, as soon as the updated kernel gets installed, the next reboot will be stuck since the prl_fs
filesystem type is unknown (no matching kernel module for new kernel version?). I cannot even use a provisioning script to re-build the tools, since the boot process aborts before that is run.
When I set prl.update_guest_tools = on
, the initial boot fails since there is no linux-headers
package matching the kernel version used by the base image.
@mpdude This image seems to be running a very old version of the QEMU hypervisor, you could try to build your own vagrant box using this packer recipe found here https://github.com/Parallels/packer-examples/tree/main
We are in the process of creating our own vagrant images in VagrantCould, meanwhile, you can also join our Discord Server to discuss any doubts or check when this will be released
Hey there,
I have a problem to bring up a box with the following Vagrantfile:
The
box_version
is given for stability/reproducibility. It's this one.Here is the abbreviated result from
vagrant up
:This is the kernel currently running in the VM:
Also, a manual install attempt fails:
My guess is that this base image was built with a kernel version that is not the one of the original Ubuntu 22.04 distribution, but rather from an intermediate (security?) update. However, the
linux-headers
package is no longer available in a matching version. I don't know for sure, but maybe the Ubuntu "security" APT repositories provide only current versions of updated packages?When I run a full
apt-get -y dist-upgrade
, the5.15.0-79-generic
kernel version will be installed, the current security version as of today. And uponvagrant reload
, the installation of Parallels Tools will proceed.The problem is that there is no clean
vagrant up
way of bringing up this box: Before installing Parallels Tools, we'd need to install the latest updated kernel package and reboot – and that would be necessary as part of the initial bootstrap process.Is there anything we can do about this from the
vagrant-parallels
side of things?Is this something that needs to be addressed by the box providers, e. g. bento? Would they need to provide a base image with a (possibly very outdated) kernel version that always has a
linux-headers
version available?