On Monday, December 2, 2024, Ian Laurie via test <
test@lists.fedoraproject.org> 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
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 kern
On Sunday, December 1st, 2024 at 4:28 PM, Ian Laurie via test
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/zwqjusole6swa...@google.com/T
On 30/11/24 18:50, Ian Laurie via test wrote:
Is this expected behavior with 6.12 or is it somehow specific to me?
Can't we have the module unloaded *by default* and have QEMU/KVM load it
as required? Then unload it when the last VM exits? Seems useless
having it loaded all the time, especially
Helping out a bit today, and will help out as much as i can during the week
thats coming
Den lör 30 nov. 2024 kl 14:12 skrev Sumantro Mukherjee :
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 6.12
> Test week is happening from 2024-12-01 to 2024-12-08. It's
> fairl
