For what its worth:
I have the same issue with Ubuntu 22.04.4 LTS (Desktop).
Working kernel (i.e. VM in Virtualbox 6.1 boots): Linux 5.15.0-1061-gke
Broken kernel (i.e. VM no longer boots): Linux 5.15.0-1062-gke
Workaround: Installed Virtualbox 7 from the Oracle PPA repository and
migrated VM wi
@Kevin you need to remove (uninstall) the guest additions from the VM before
upgrading to virtualbox 7.
(This is true when migrating any VM between major virtualbox versions - even if
both work correctly with the same kernel version on the Host).
Shortly:
1. Boot Windows Guest VM with Virtualbo
@Kevin you need to remove (uninstall) the guest additions from the VM before
upgrading to virtualbox 7.
(This is true when migrating any VM between major virtualbox versions - even if
both work correctly with the same kernel version on the Host).
Shortly:
1. Boot Windows Guest VM with Virtualbo
@Kevin yes. It really depends on the extent of changes between major
versions of virtualbox as to whether it will _always_ be required, but
it is at least necessary in the 6.1 -> 7 migration case.
AFAICT Oracle never released an official VM migration guide with the
release of virtualbox 7, but bas
@mruffell Perhaps I'm missing something, but the kernel discussion
thread you linked specifically ends with "The CVE has now been rejected,
thanks for the review!".
Surely that means that the Ubuntu team can revert the commit then?
(unless you are of the opinion that the security vulnerability the
@kees Thanks for jumping on this thread!
From a technical perspective I agree with you, but I would reason that
it's not really a change one would want end-users of the Ubuntu LTS
kernel to implement.
It comes back to the reasoning mentioned by @Andy in #70 and @Gustav in
#73: a kernel update on
