You are not logged in.
After the recent VIrtualbox 6.1.12-4 (Linux) update all VMs with a virtual USB 2.0/3.0 Controller fail to start.
I interpreted the error message
"Failed to load R0 module /usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxEhciR0.r0: RTLdrGetBits failed (VERR_SYMBOL_VALUE_TOO_BIG). Failed to load ring-0 module 'VBoxEhciR0.r0' for device 'usb-ehci' (VERR_SYMBOL_VALUE_TOO_BIG)."
as: "VM failed to start because the necessary R0 driver for EHCI/XHCI from the extension pack failed to load".
Workaround 1: Remove the extension pack and start VMs with USB 1.1 only
Workaround 2: Downgrade to 6.1.12-3
Last edited by -thc (2020-08-13 07:41:26)
Offline
Same as this.
Offline
I don't think so. The TO of that thread wrote
"Thanks loqs, replacing host modules with dkms package solved the problem"
My error occurs with "virtualbox-host-dkms" already installed and included in up- and downgrades.
Offline
What version of extension pack do you have? I had issues after upgrade just like you a downgrade to 6.1.12-3 fixed it but downgraded my extension pack as well to 6.1.12-1 and everything is OK. (Basically just deferring upgrade and keeping the old packages.)
Offline
Current workaround -
Downgrade to
- virtualbox 6.1.12-3
- virtualbox-host-modules-arch 6.1.12-5
Kept Extension Pack 6.1.12r139181
Cheers
R7
Offline
After downgrading my VMs' USB controller to USB 1.1 (OHCI), they started normally so I don't have to downgrade virtualbox.
Offline
@d_fajardo: Oracle VM VirtualBox Extension Pack 6.1.12r139181
Offline
There's a new update of virtualbox-host-modules-arch as well today. I upgraded to that new version and virtualbox 6.1.12-4 but I still got module problems and VM won't run.
So I decided to downgrade back both packages and kept the old extension version for virtualbox to work.
Am I right in understanding we will need am updated kernel as well for these new modules to work? When are these updates supposed to work?
Offline
I found the source of the problem.
I looked into the details of the package virtualbox. 6.1.12-4 is a patch for the upcoming 5.8 kernel:
https://github.com/archlinux/svntogit-c … d9db127101
Right there is stated "Use the extension pack 6.1.13.139853 if required...". (This version is still a "testcase" and not easy to find)
Either use the AUR package "virtualbox-ext-oracle" or download it here:
https://www.virtualbox.org/download/tes … ox-extpack
I presume this problem will finally vanish with kernel 5.8/virtualbox 6.1.13.
Offline
Thanks -thc. I think I'll just wait for 5.8 so in the meantime I'll just give virtualbox and modules the IgnorePkg.
Offline
thank you -thc
i run this command solve this
sudo VBoxManage extpack install --replace ~/Downloads/Oracle_VM_VirtualBox_Extension_Pack-6.1.13-139853.vbox-extpack
Offline
Followed up all above steps with great success. So far, so good.
With the advent of kernel 5.8.1 a new ball is in this game: With all above measures in place + 5.8.1 kernel + starting win10 in virtualbox --> total immediate system freeze!
Beware, if you should have other open documents / files of importance.
Rolled kernel back to 5.7.12. All back to "normal".
Prefer anything that tastes like UNIX and beer.
Offline
The latest linux 5.8.1 update fixed all the virtualbox update issues.
Offline
It is not solved, I have updated my system today to kernel 5.8.1 and virtualbox 6.1.12-4 (using host-dkms), and downloaded the latest extension pack. I could start a virtual machine only if USB was disabled.
Then, while writing this message, my system completely froze and I had to hard-reset (no REISUB). After two more freezes, I downgraded to kernel 5.7.12 and for now I can get back to work.
Last edited by dixDel (2020-08-15 10:12:04)
Offline
Hi,
I'm experiencing the same issue with latest updates:
-linux 5.8.1.arch1-1
-virtualbox 6.1.12-4
-virtualbox-host-modules-arch 6.1.12
Offline
@jkleinerman Did you update your virtualbox extension as well?
Offline
I was able to "fix" this by downgrading virtualbox, virtualbox-host-modules-arch, and my linux kernel.
- virtualbox 6.1.12-3
- virtualbox-host-modules-arch 6.1.12-5
- linux 5.7.12.arch1-1
Not sure if kernel downgrade is needed, but I'm keeping all three back until I see this is resolved.
Offline
I'm not sure why some of you are still having problem with the upgrades. It's probably be a good idea to start a new thread with your specific problem since the OP has marked this thread as solved and will probably be by-passed by those who have more know-how.
Currently these package versions work for me without problem:
linux 5.8.1.arch1-1
virtualbox 6.1.12-4
virtualbox-host-modules-arch 6.1.12-9
virtualbox-ext-oracle 6.1.13.139853-1
Offline
@d_fajardo: I don't have virtualbox-ext-oracle installed.
I have never needed it and always everything works fine.
But with the latest updates all my VMs crhases when I started them
Offline
I have just tested installing virtualbox-ext-oracle and still having the same problem:
@d_fajardo take into account that this problem appears for example when your VM uses the network bridged addapter interface. Maybe it is not your sittuation.
My actual packages version:
linux 5.8.1.arch1-1
virtualbox 6.1.12-4
virtualbox-ext-oracle 6.1.13.139853-1
virtualbox-host-modules-arch 6.1.12-9
Offline
Hi,
I'm experiencing the same issue with latest updates:
-linux 5.8.1.arch1-1
-virtualbox 6.1.12-4
-virtualbox-host-modules-arch 6.1.12
I am having the same problem. I was using virtualbox 6.1.12-3 and virtualbox-host-modules-arch 6.1.12-5, as recommended earlier, and suddenly it stopped working. Tried updating, nothing.
Offline
There is a new discussion here so perhaps you can post your VM log files there so people can have a look as I said since this thread has been marked solved. It is more likely that people will look at that than this thread.
The OP there somehow traced his problem to the USB controller of the VM. So I suggest to do the same and just post your logs.
Offline
The OP there somehow traced his problem to the USB controller of the VM.
Disabling USB at all solved the no-start-issue for me, too. Its ok so far for me personally as i don't need USB at all - but others might.
Also, using USB-1.1 makes VMs starting again.
Offline
I found the source of the problem.
I looked into the details of the package virtualbox. 6.1.12-4 is a patch for the upcoming 5.8 kernel:
https://github.com/archlinux/svntogit-c … d9db127101
Right there is stated "Use the extension pack 6.1.13.139853 if required...". (This version is still a "testcase" and not easy to find)
Either use the AUR package "virtualbox-ext-oracle" or download it here:
https://www.virtualbox.org/download/tes … ox-extpackI presume this problem will finally vanish with kernel 5.8/virtualbox 6.1.13.
problem solved
thank you -thc
Last edited by zeroArch (2020-08-17 10:54:31)
Offline
I followed -thc suggestion, it worked.
Thanks
Offline