On Monday, December 2, 2024, Ian Laurie via test <test@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
On 2/12/24 10:37, Scott Dowdle via test wrote:
versa... but it isn't that difficult for a VirtualBox user to hold back
on a kernel update until VirtualBox gets updated. You'll get used to it.
This is a lot more serious that the *routine* host kernel compatibility
problems that happen in new kernel streams (that I am well used to).
Those get fixed very promptly.
I would be surprised if this gets fixed any time soon.
Well, there is a workaround which restores the old behavior and the suggestion from the upstream thread of adding a modprobe snippet to the virtual box rpm also sounds reasonable.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
--
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct /
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxx oraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
