Upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=219107
** Bug watch added: Linux Kernel Bug Tracker #219107
https://bugzilla.kernel.org/show_bug.cgi?id=219107
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
> Quoting @mapengyu: "VirtualBox 6.1.x is no longer supported! Which is
announced by virtualbox.org. So it's a bit hard to push kernel changes
for an unsupported application."
That is what I was alluding to in comment #14.
Thus, the real question might be if there is a way to facilitate/expedite t
Confirmed to be a problem with kernel 5.15.117 installed via unattended-
upgrades. 5.15.116 does not work. Virtualbox previously worked. Trying
to revert to 5.15.107.
This is on Kubuntu 22.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Hi all,
1, This issue is caused by the following 2 commits in upstream kernel:
9c573cd31343 randomize_kstack: Improve entropy diffusion
ef40d28f17bd randomize_kstack: Remove non-functional per-arch entropy filtering
But only virtualbox 6.1.50 will crash.
VirtualBox 6.1.x is no longer supported!
I would love to test the recent kernel of linux-image-5.15.0-117-generic
(version: 5.15.0-117.127~20.04.1 (focal updates).
But unfortunately I am not even getting to the graphical user interface (i.e.
login screen) with that kernel version. And in the TTY that I _can_ access,
there doesn't seem
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-03-26 (857 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
Nonfre
> Quoting comment #40: "In the Dublicate Bug 2074095 one of the Kernel
Developers asked für help to debug. See comment #3."
Adjusting the apport-collect command for this bug report corresponds to:
apport-collect 2073267
The crash happens in any guest virtual machine (not only Ubuntu), which becom
Note that the URL is irrelevant. The bug is listed for all indicated
packages; see: https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-5.15/+bug/2073267
To my understanding, the HWE stack is the default for kernel installations in
Ubuntu. Its is upstream of any Ubuntu-signed kernel image
In the Dublicate Bug 2074095 one of the Kernel Developers asked für help
to debug. See comment #3.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074095/comments/3
I am using Linux Mint so I can't help him. Maybe someone from this
thread is able to provide him the nessesary informations.
I think the question is what is the correct kernel package to list it
against. "linux-signed-hwe-5.15" is a hardware enablement kernel
package but the issue is not specific to that build of the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Primary package for this bug should be linux-signed-hwe-5.15. VirtualBox
is affected, but it's not the root cause.
I am judging by the bug URL, currently it contains "virtualbox", so it
may look like a VirtualBox bug. If that's not a big deal and Linux
kernel maintainers are properly notified abou
> Quoting comment 36: "This bug is reported against wrong package."
The bug report is currently filed against the packages "linux-signed-
hwe-5.15 (Ubuntu)" and "virtualbox (Ubuntu)". Would you mind to
elaborate on why think that this is not appropriate?
--
You received this bug notification bec
** Changed in: virtualbox (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Guru meditation on VM start
To manage notifications about this b
This bug is reported against wrong package. Is it possible to change it
somehow? Maybe that's the reason this bug has so little attention.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Yes, the problem's still there for me with kernel 5.15.0-117 on 22.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Guru meditation on VM start
To manage notifications about this bu
Can sadly but unsurprisingly confirm that the new 5.15.0-117 kernel
doesn't resolve this on 22.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Guru meditation on VM start
To manage
Don't think this will be fixed any time soon. Has someone a way to get
in touch with the upstream kernel developers..?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Guru meditation on
@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
Does this mean the uninstall-upgrade-reinstall dance has to be done
anyway on any major upgrade of virtualbox (e.g. when upgrading Ubuntu
past jammy)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073
I have the same setup as Andy (comment #22).
Ubuntu 22.04.4 LTS
VirtualBox is version installed from Ubuntu repo:
virtualbox/jammy-updates,now 6.1.50-dfsg-1~ubuntu1.22.04.1 amd64 [installed]
Problem with no longer being able to start any guest OS in VirtualBox first
appeared after system update
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Guru meditation on VM start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
With regard to "but I don't see enough information here to isolate it to
specific versions of packages that Ubuntu shipped" above, perhaps this
will help:
On an Ubuntu 22.04 LTS system, "apt search virtualbox | grep installed"
finds:
libvirt-bin/now 4.0.0-1ubuntu8.21 amd64 [installed,local]
libv
FWIW I had a situation a lot like that reported by @unhammer in #24, but
(maybe because I am using a physical disk for the Windows, maybe because
it's a different Windows version) I didn't have clear error messages
about drivers. However, the fix suggested by @davidstreicher123 in #25
worked: Boot
I think that pretty clearly shows that upgrading the VirtualBox version
to 7 in the Ubuntu repos for 20.04 and 22.04 is not going to be the
solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20732
@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
Upgrading to virtualbox 7 let the vm start booting, but windows crashes
on boot with a message about an issue with the driver vboxwddm.sys , I'm
guessing because guest additions installed from ubuntu package conflict
with those from the ppa? So that workaround doesn't solve all cases
either.
--
Y
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
I have the issue on Kubuntu 22.04 LTS.
VirtualBox package: virtualbox
version: 6.1.50-dfsg-1~ubuntu1.22.04.1 (jammy-updates)
Kernel package: linux-image-5.15.0-116-generic
version: 5.15.0-116.126 (jammy-updates)
The above combination has the problem. VirtualBox cannot start VMs.
This started wh
Specified the affected package / kernel branch for clarity.
** Also affects: linux-signed-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-signed-hwe-5.15 (Ubuntu)
Status: New => Confirmed
** No longer affects: linux-signed-hwe-5.15 (Ubuntu)
** Package c
In support of Vasya's observation, the issue appeared for me on Ubuntu 20.04.6
LTS on Ubuntu-shipped VirtualBox (package: virtualbox, version:
6.1.50-dfsg-1~ubuntu1.20.04.1) following a kernel update from
linux-image-5.15.0-113-generic to linux-image-5.15.0-116-generic .
Reverting back to the pr
Also, I reported this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-5.15/+bug/2073691 against specific package version and no third
party software.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
The problem appeared in the package linux-image-5.15.0-116-generic in
all Ubuntu releases that ship VirtualBox version 6.x, particular version
of VirtualBox package doesn't matter. Rolling back to linux-
image-5.15.0-113-generic fixes the issue.
--
You received this bug notification because you a
Somebody appeared on IRC asking for help with this bug but disappeared
again before I could reply.
It's clear that there is an issue, but I don't see enough information
here to isolate it to specific versions of packages that Ubuntu shipped.
People seem to be reporting versions either not publishe
At the moment it's unclear if anyone who can do anything about this is
even aware of it. On any list of bugs I look at, this one is buried
under hundreds of others that are sometimes a decade or more old. I'm
not sure how anyone would become aware of it.
Reading about bug handling processes on w
> finally switch to VirtualBox version 7
While it's totally fine, I do not agree that it should be a fix for this
problem. Kernel upgrades within the same minor version should not break
existing software. This is clearly a bug (major change) in the kernel
package and this is where it should be add
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Guru meditation on VM start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
Same issue on Ubuntu 20.04 (kernel version 5.15.0-116-generic;
virtualbox version 6.1.50).
Considering the Linux world was hit with a few major security flaws in
the last few months, I strongly advice against the use of older kernel
versions.
Furthermore, this issue should not (!) be fixed in ker
Just tested the "focal-proposed" kernel version 5.15.0-118 (with "Pre-
released updates" enabled) on Ubuntu 20.04 with VBox 6.1.50.
Unfortunately the VM didn't work at all with exactly the same symptoms
as with "stable" kernel version 5.15.0-116. Was unable to find any
workaround so I had to downgr
Same issue here with Ubuntu Mate 22.04. It worked with kernel
5.15.0-112.
The log file says:
ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057)
aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap}
aText={Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)},
prese
Upgrading to virtualbox 7.0.20 fixed my system. I'm back on 5.15.0-116
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Guru meditation on VM start
To manage notifications abou
I have the same error with Linux Mint 21.2 Cinnamon with kernel
5.15.0-116-generic and VirtualBox installed from Ubuntu repo (version
6.1.50-dfsg-1~ubuntu1.22.04.1).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I've had all sorts of issues with Kernels after -107. First my
keyboard was unresponsive after a sleep/suspend. Then it was not being
able to suspend (it would just immediately wake).
Adding entries in grub fixed the first issue for while and got fixed
about 112 or 113. Now they toss this issu
Same story for me with Linux Mint 21.3 Cinnamon and VirtualBox 6.1 on
Thinkpad T495 (AMD Ryzen):
5.15.0-116 fails
5.15.0-113 fails (doesn't even manage to boot Linux Mint, why did they
push this to updates?!)
5.15.0-112 fails (manages to get a line of text out on the console
before the VM crashe
I have the same problem, solved by uninstalling the version from Ubuntu repo,
and installing instead the version 7 from virtualbox web site:
https://www.virtualbox.org/wiki/Linux_Downloads
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Here is a ticket for the same issue on virtualbox.org, for what it's worth:
https://www.virtualbox.org/ticket/22115
But support for VirtualBox 6.1 ended in January this year so we can't expect
any fix to be forthcoming from Oracle.
** Bug watch added: Virtualbox Trac #22115
http://www.virtualb
I can confirm this bug an add the following information:
Kernel 5.15.0-116-generic: VBox 6.1.50 is not working at all
Kernel 5.15.0-112-generic and 5.15.0-113-generic: VBox 6.1.50 is working
with boot workaround amg_iommu=off due to the bug in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
** Tags added: jammy regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Guru meditation on VM start
To manage notifications about this bug go to:
https://bugs.launchpad.
Same problem here, on several machines, all Ubuntu 22.04 after updating
the kernel to version 5.15.0-116.
All hosts and guests are x86_64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
Hey,
I have exactly the same issue on Linux Mint 21.3 (based on Ubuntu 22.04)
with the kernel 5.15.0-116 and Virtualbox installed from Ubuntu repo
(version 6.1.50-dfsg-1~ubuntu1.22.04.1).
After trying to go back to previous kernel version 5.15.0-113, all my VM
worked again. So, it seems the last
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073267
Title:
** Description changed:
It worked yesterday, but today I get a Guru Meditation trying to start
some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru
Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may
have started due to a Linux kernel upgrade I install
53 matches
Mail list logo
