Ask Your Question

Revision history [back]

Seems like the problem is that new kernels are not added to grub menu correctly.

First, check if you have up to date kernel (4.4.8) installed correctly.

ls /boot/

And look for vmlinuz and initramfs with 4.4.8 version tag.

If they are indeed there, let grub2 update its configuration file (menu items set there)

grub2-mkconfig -o /boot/grub2/grub.cfg

(It is a good idea to backup /boot/grub2/grub.cfg first.)

You can optionally inspect the file for 4.4.8 kernel (Root privilege required.)

sudo less /boot/grub2/grub.cfg

(Use q to exit the viewer interface.)


But it seems to me Vagrant (new versions) do not require VirtualBox anymore, and it is available in Fedora's official software repo. So all you have to do is:

sudo dnf install vagrant

Seems like the problem is that new kernels are not added to grub menu correctly.

First, check if you have up to date kernel (4.4.8) installed correctly.

ls /boot/

And look for vmlinuz and initramfs with 4.4.8 version tag.

If they are indeed there, let grub2 update its configuration file (menu items set there)

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

(It is a good idea to backup /boot/grub2/grub.cfg first.)

(Root privilege required. If you do not use sudo, substitute with su -c 'your_command' and input root password)

You can optionally inspect the file for 4.4.8 kernel (Root privilege required.)kernel

sudo less /boot/grub2/grub.cfg

(Use q to exit the viewer interface.)


But it seems to me Vagrant (new versions) do not require VirtualBox anymore, and it is available in Fedora's official software repo. So all you have to do is:

sudo dnf install vagrant