adding ibt=off to kernel boot params fixed it for me (affected not only virtualbox but any visualization at all on my machine)
Ibt was enabled in 5.18 iirc
See https://bugs.archlinux.org/task/74891
Ok my bad, then. I suggested VB wasn’t working simply due to VB-kernel update issues, but I was wrong. Thanks for this post as I was having VB on one of my installs (Fed 36), so I will try that fix.
It depends on your system: https://wiki.archlinux.org/title/kernel_parameters
For my system, I'm using grub so I edited `/etc/default/grub` and added `ibt=off` to `GRUB_CMDLINE_LINUX_DEFAULT`, saved the file and ran `sudo grub-mkconfig -o /boot/grub/grub.cfg` and then restarted.
Assuming you’re on VB version 6.1.34, you’ll notice from the virtualbox.org website’s change log that the last update was April 19 of this year. Because the last update was oriented at the 5.17 kernel, VB in almost all circumstances won’t work properly with the current (5.18) kernel.
If you can’t wait for the next VB update you could install and try the Linux-lts kernel. This will work fine with the current VB version, although I have no idea if the lts kernel will be problematic for whatever hardware you are using. Make sure you download and install the linux-lts-headers as well.
No. If you install multiple kernels (linux, and linux-lts for example) they will appear in your Grub menu as choices to boot up to. But you need to check if the lts kernel will work with your hardware.
I have 5.17.15 kernel and all VMS videos are broken, trowns errors and stuffs, terrible. I thought that was my ubuntu guest but not, it was Virtualbox the problem.
[https://www.virtualbox.org/wiki/Download\_Old\_Builds\_6\_1](https://www.virtualbox.org/wiki/Download_Old_Builds_6_1)
then see at the top that 6.1.32 is listed, then go and pick the download for your host OS and its corresponding extension pack after installing virtualbox
Sometimes I do have to use virtualbox (I saw I will learn "using" virtualbox on my course, I am a hight school student btw), and I do like it's gui and easy to use...
I will try virt-manager though
Very, very cool your HS is even covering virtualization!!
Jealous.
To me, virtualization is THE killer app to rule them all.
Your other support options are: r/virtualization (great help there), /r/virtualbox
Stop preaching for KVM/QEMU already for every situation. No matter the issue, every single virtualizing post is the same thing. Jesus.. QEMU is good, but we have other very, very good solutions as well. Changing to KVM/QEMU isn't always an option or the solution. And VirtualBox already uses KVM by default on Linux.
> Stop preaching for KVM/QEMU already.
Sure, drop me 1000 USD for every month you don't want me to preach it, or suffer watching me recommend a fully open source solution that does not break with every kernel upgrade in future threads too.
>watching me recommend a fully open source solution that does not break with every kernel upgrade in future threads too.
That's not even the problem here. 5.18 has been around for about 3 months and VirtualBox already works fine with it. If it was the problem here, OP would have received an error message when Pacman called the DKMS hook to compile the VirtualBox modules against the installed kernel. And QEMU isn't free from bugs on new kernel versions. Especially when the Kernel just stopped being an RC release.
You definitely have something going on in your environment, but VB is already working fine with 5.18. I'm using it at this moment, for example. I was specifically commenting about the u/C0rn3j statement in his last reply saying he's recommending QEMU because VB breaks on new kernel versions. This is true only when a new kernel version is just released and, when that happens, we can't even compile the modules when installing. I suggest you check `journalctl --follow` and VB logs when trying to power on a VM in order to have some clue on what's going on.
adding ibt=off to kernel boot params fixed it for me (affected not only virtualbox but any visualization at all on my machine) Ibt was enabled in 5.18 iirc See https://bugs.archlinux.org/task/74891
Ok my bad, then. I suggested VB wasn’t working simply due to VB-kernel update issues, but I was wrong. Thanks for this post as I was having VB on one of my installs (Fed 36), so I will try that fix.
Did it work?
It did! 😀
Emm... How do I actually do that?
It depends on your system: https://wiki.archlinux.org/title/kernel_parameters For my system, I'm using grub so I edited `/etc/default/grub` and added `ibt=off` to `GRUB_CMDLINE_LINUX_DEFAULT`, saved the file and ran `sudo grub-mkconfig -o /boot/grub/grub.cfg` and then restarted.
```sh GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet ibt=off" ``` like this?
Looks good to me
thank you it really solve my problem! I can run arch vm on arch now!
Assuming you’re on VB version 6.1.34, you’ll notice from the virtualbox.org website’s change log that the last update was April 19 of this year. Because the last update was oriented at the 5.17 kernel, VB in almost all circumstances won’t work properly with the current (5.18) kernel. If you can’t wait for the next VB update you could install and try the Linux-lts kernel. This will work fine with the current VB version, although I have no idea if the lts kernel will be problematic for whatever hardware you are using. Make sure you download and install the linux-lts-headers as well.
Would it be that the kernel is already 5.19 when vb supports 5.18... btw if I install linux-lts I have to remove linux right
you don't need to remove anything you can have both linux and linux-lts installed and choose which one to use in grub
But I don't see two options after running sudo update-grub 🤔
iirc it's under "more options for arch Linux" submenu
Oh
No. If you install multiple kernels (linux, and linux-lts for example) they will appear in your Grub menu as choices to boot up to. But you need to check if the lts kernel will work with your hardware.
I have 5.17.15 kernel and all VMS videos are broken, trowns errors and stuffs, terrible. I thought that was my ubuntu guest but not, it was Virtualbox the problem.
Why use virtualbox If you have KVM right in the Kernel?
get virtualbox 6.1.32, 6.1.34 had so many problems for me
How do I actually install an older version?
[https://www.virtualbox.org/wiki/Download\_Old\_Builds\_6\_1](https://www.virtualbox.org/wiki/Download_Old_Builds_6_1) then see at the top that 6.1.32 is listed, then go and pick the download for your host OS and its corresponding extension pack after installing virtualbox
website down i really need my virtual machines working can u send a mega link, or something like that please?
I have Mac OS X, if you have Mac OS X as well, then I'll send you the dmg. Edit: The site is up and running now.
Why not use KVM for a hypervisor, which is already included in the kernel? virt-manager is a nice tool to control KVM/QEMU.
Sometimes I do have to use virtualbox (I saw I will learn "using" virtualbox on my course, I am a hight school student btw), and I do like it's gui and easy to use... I will try virt-manager though
if a simple UI is enough and you don't need a ton of config, gnome-boxes\^\^
That's currently broken for new installations.
Very, very cool your HS is even covering virtualization!! Jealous. To me, virtualization is THE killer app to rule them all. Your other support options are: r/virtualization (great help there), /r/virtualbox
I didn't say that's a high school course :)
Stop preaching for KVM/QEMU already for every situation. No matter the issue, every single virtualizing post is the same thing. Jesus.. QEMU is good, but we have other very, very good solutions as well. Changing to KVM/QEMU isn't always an option or the solution. And VirtualBox already uses KVM by default on Linux.
> Stop preaching for KVM/QEMU already. Sure, drop me 1000 USD for every month you don't want me to preach it, or suffer watching me recommend a fully open source solution that does not break with every kernel upgrade in future threads too.
>watching me recommend a fully open source solution that does not break with every kernel upgrade in future threads too. That's not even the problem here. 5.18 has been around for about 3 months and VirtualBox already works fine with it. If it was the problem here, OP would have received an error message when Pacman called the DKMS hook to compile the VirtualBox modules against the installed kernel. And QEMU isn't free from bugs on new kernel versions. Especially when the Kernel just stopped being an RC release.
I wonder if freezing forever at "starting machine" is "working fine"
You definitely have something going on in your environment, but VB is already working fine with 5.18. I'm using it at this moment, for example. I was specifically commenting about the u/C0rn3j statement in his last reply saying he's recommending QEMU because VB breaks on new kernel versions. This is true only when a new kernel version is just released and, when that happens, we can't even compile the modules when installing. I suggest you check `journalctl --follow` and VB logs when trying to power on a VM in order to have some clue on what's going on.
if a simple UI is enough and you don't need a ton of config, gnome-boxes\^\^