Kernel log when running on the 6.8.0-31-generic Ubuntu kernel:
https://dpaste.com/969L98QN2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
Ubuntu 24.04 LTS VBox VM does not boot anym
I noticed that the guest additions features are still functional in the
6.8.0-31-generic version of the Ubuntu kernel, but are no longer
available after upgrading to 6.8.0-47-generic.
If we bisect these two versions we may be able to locate the kernel
version that introduces the regression.
Note
A known workaround is to install the guest additions provided by the
upstream application, at least with 7.0.22 upstream version it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
** Summary changed:
- Ubuntu 24.04 LTS VBox VM does not boot anymore
+ Ubuntu 24.04 LTS VBox VM does not boot anymore ["vmwgfx seems to be running
on an unsupported hypervisor"]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Once the boot process also failed on my Xubuntu 24.04 VM. I happened
after more than a week without an issue. The second boot was OK.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076520/+attachment/5809034/+files/prevboot.txt
--
You received this
The info about the BIOS
$ sudo dmidecode
[sudo] password for bertadmin:
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 2.5 present.
10 structures occupying 456 bytes.
Table at 0x000E1000.
Handle 0x, DMI type 0, 20 bytes
BIOS Information
Vendor: innotek GmbH
Version: V
That's the version of the VM's BIOS, not of the hypervisor, I assume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
Ubuntu 24.04 LTS VBox VM does not boot anymore
To manage notific
OP's bug report says:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
VirtualBox 1.2? That can't be right. That was in 2007.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
Ub
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/2076520
Title:
I have a very similar problem: I created a virtual machine using VirtualBox 6
and installed Ubuntu 22.04 on it. Recently, I installed VirtualBox 7.0.18 and
created a virtual machine with Ubuntu 24.04. This VM installed Ubuntu
correctly, but after that would never work properly again.
Sometimes
** Attachment removed: "VBox.log"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2076520/+attachment/5806184/+files/VBox.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
** Also affects: virtualbox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
Ubuntu 24.04 LTS VBox VM does not boot anymore
To man
Oops!
** Attachment added: "VBox.log.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076520/+attachment/5806185/+files/VBox.log.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Ti
Hello,
ElTouco72 (eltouco72) wrote:
"I have exactly the same problem on ubuntu 22.04 LTS since the kernel was
updated to 6.8
VMs don"t start now
I use virtualbox 6.1 (the version that is in ubuntu repo)"
+1
I had to restart on kernel 6.5.0-45 to use VMs.
Virtualbox version: 6.1.50-dfsg-1~ubu
** Attachment added: "VBox.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076520/+attachment/5806184/+files/VBox.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
Ubun
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
Ubuntu 24.04 LTS VBox VM does not boot anymore
To manage notifications about this bug go to:
https:/
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/2076520
Title:
Ubun
I have exactly the same problem on ubuntu 22.04 LTS since the kernel was
updated to 6.8
VMs don"t start now
I use virtualbox 6.1 (the version that is in ubuntu repo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I don't know the design, so I can't add much information. But I expect
it is a timing issue between the kernel and one of the virtualbox kernel
modules. They do things in 2 threads (one from the kernel and one from
virtualbox) and they are not properly synched. So in some systems it
will work alway
Sounds like a bug in the guest driver (vmwgfx) in that case. Although
some quick googling for:
"vmwgfx seems to be running on an unsupported hypervisor"
reveals it can be storage related too. I guess because the hypervisor
uses similar mechanisms for sharing storage as it does for communicating
There is only one graphics controller you can select for Linux: VMSVGA
and you can use it with or without 3D acceleration, but it has the same
result. And basically that is the first thing I try in case of any
potential display issue. All my other Linux and older Ubuntu VMs run
fine with this graph
There are several kernel crashes there. And separately vmwgfx seems to
be failing, complaining "*ERROR* vmwgfx seems to be running on an
unsupported hypervisor". So it's possible the fix here is to choose a
different virtual graphics card in VirtualBox.
--
You received this bug notification becau
I had a problem, getting the system to run in recovery mode, so I copied
the whole journalctl file, but I deleted manually all older boots. The
first boot of "ago 12" is the one that went wrong and the one you
requested. I let the VM run for 3 minutes and then I VBox-powered-off.
My normal boot tim
Thanks for the bug report.
We will need to see a boot log that's not in recovery mode. Please
reproduce the bug again, then reboot into recovery mode and run:
journalctl -b-1 > prevboot.txt
And attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: u
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076520
Title:
Ubuntu 24.04 LTS VBox VM does not boot anymore
To manage notifications about this bug go t
25 matches
Mail list logo
