You are not logged in.
Pages: 1
Hi there,
I upgrade kernel to 5.18, and found Windows 10 installed in virtualbox crashes all the time.
In other words, virtualbox can start up without problem, but when I startup virtual operating system installed in virtualbox the OS crashes.
I also tried install a Windows OS fresh new, unfortunatelly the install procedure also crashed ...
Down grade to linux-5.17.8.arch1-1 && virtualbox-host-modules-arch 6.1.34-8 resolved problem.
I saw there is a comment `Replaces virtualbox-guest-modules-arch, wireguard-arch` at this page: https://archlinux.org/packages/core/x86_64/linux/, maybe there is some problem with these modules ...
Is there a known issue to linux-5.18 ?
Last edited by Hacksign (2022-05-30 04:56:11)
Offline
Probably related: https://bugs.archlinux.org/task/74900
Offline
Probably related: https://bugs.archlinux.org/task/74900
Seems the same bug as I met ...
So current method to avoid this bug is one of:
* So wait for virtualbox-6.1.35-151573
* Or down grade linux & virtualbox-host-modules-arch to the proper version
Offline
> So current method to avoid this bug is one of:
FYI, I've asked about another option at that bug report
Offline
I'm affected by the same problem and due to this I have avoided upgrading to kernel 5.18 till now. Today I have seen that virtualbox 6.1.36 is finally available, so I upgraded
linux (5.18.13.arch1-1 => 5.17.9.arch1-1)
linux-headers (5.18.13.arch1-1 => 5.17.9.arch1-1)
virtualbox (6.1.36-1 => 6.1.34-3)
virtualbox-host-modules-arch (6.1.36-2 => 6.1.34-8)
and the same problem occurred, nothing worked anymore until I reverted the upgrade.
So what am I missing here?
I thought virtualbox > 6.1.34 should solve the issue?
Offline
So no clue or no solution?
I have no problems sticking to kernel 5.17.9 for the time being, as long as everything works, but the hope for a resolution by virtualbox >= 6.1.35 wasn't fruitful, so what to wait for now for not having to try and revert again and again?
Offline
I'm affected by the same problem and due to this I have avoided upgrading to kernel 5.18 till now. Today I have seen that virtualbox 6.1.36 is finally available, so I upgraded
linux (5.18.13.arch1-1 => 5.17.9.arch1-1)
linux-headers (5.18.13.arch1-1 => 5.17.9.arch1-1)
virtualbox (6.1.36-1 => 6.1.34-3)
virtualbox-host-modules-arch (6.1.36-2 => 6.1.34-8)and the same problem occurred, nothing worked anymore until I reverted the upgrade.
So what am I missing here?
I thought virtualbox > 6.1.34 should solve the issue?
Same thing with kernel 5.19.5-arch1-1. Despite the patch given above in https://bugs.archlinux.org/task/74900 is included in virtualbox-6.1.36
Offline
Same thing with kernel 5.19.5-arch1-1. Despite the patch given above in https://bugs.archlinux.org/task/74900 is included in virtualbox-6.1.36
So confirmed as still not working and no solution is sight?
Is nobody using VirtualBox anymore nowadays?
Offline
Louson wrote:Same thing with kernel 5.19.5-arch1-1. Despite the patch given above in https://bugs.archlinux.org/task/74900 is included in virtualbox-6.1.36
So confirmed as still not working and no solution is sight?
Is nobody using VirtualBox anymore nowadays?
I use downgrade to install
linux 5.17.8.arch1-1
linux-headers 5.17.8.arch1-1
virtualbox 6.1.36-1and it works.
Offline
No one has posted the kernel messages from the virtualbox crash. So how do you know you have the same issue as each other and how are others supposed to help?
Offline
I use downgrade to install and it works.
Me to, though that's not a solution but only a workaround.
No one has posted the kernel messages from the virtualbox crash. So how do you know you have the same issue as each other and how are others supposed to help?
Because it's the exact same error?
Offline
loqs wrote:No one has posted the kernel messages from the virtualbox crash. So how do you know you have the same issue as each other and how are others supposed to help?
Because it's the exact same error?
Offline
Pages: 1