Re: kernel-6.12.1 breaks VirtualBox hosts by default
Scott Dowdle via test <[email protected]>
| Newsgroups | gmane.linux.redhat.fedora.testers |
|---|---|
| Message-ID | <ZWyvV7IMXh-T6f8LUeoYACoTIBIfT2PB8_q_9CTCneX_gE0AMMCQlLSE74yIRPqcAP52B8knAcXdPAOvST9FpTM5w-pE08gLmc4-Jwl3dMQ=@montanalinux.org> |
On Sunday, December 1st, 2024 at 4:28 PM, Ian Laurie via test <[email protected]> wrote: > On 30/11/24 18:50, Ian Laurie via test wrote: > Not just me. > > Upstream bug: > > https://www.virtualbox.org/ticket/22248 > > Worth reading the kernel thread: > > https://lore.kernel.org/kvm/[email protected]/T/ > > This just makes life more difficult for a regular user. > > -- > Ian Laurie > FAS: nixuser | IRC: nixuser > TZ: Australia/Sydney It isn't uncommon for a new kernel to break VirtualBox, requiring it to need to be updated. Should Fedora hold back a newer kernel for third-party software they don't ship? I don't think so. I use the native hypervisor that has been part of the Linux kernel since 2007 which doesn't break because of kernel updates. I realize VirtualBox has some features that KVM doesn't have and vice 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. -- TYL,Scott Dowdle (406) 750-3319 [cell] (406) 994-3931 [work] -- _______________________________________________ test mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue