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 it doesn't boot at all. Sometimes it prints the error "vmwgfx seems to be running on an unsupported hypervisor". Sometimes it freezes, while still consuming most of my computer's CPU. Sometimes it freezes while still consuming very little CPU. Sometimes it logs me in and gets all the way to showing the Ubuntu desktop, then immediately pops up a window with a memory error, and closes the machine when I click on that pop-up.
VB7 still runs that old Ubuntu 22.04 VM fine, with NO turtle indicating snail mode, so Hyper-V apparently? isn't running, although the 24.04 machine sometimes reports another hypervisor IS running. And I CAN run the 24.04 VM without problem if I insert the Ubuntu 24.04 live CD and boot from that. And I updated to VirtualBox 7.0.20, and still had the same symptoms. So the problem does appear to be with Ubuntu 24.04, not with VirtualBox 7. I'm very confused by the fact that the 22.04 machine runs at max speed, yet, in another window at the same time, the 24.04 reports another hypervisor is running. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2076520 Title: Ubuntu 24.04 LTS VBox VM does not boot anymore Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: New Bug description: I installed it the first time, while it was still in the development edition. After the April release the system often had boot issues, the first boot failed and the second boot succeeded. Two weeks ago all boots failed except the boots in the alternate mode. So I decided to reinstall the system. I took a copy from the up-to-date working version of Ubuntu 22.04 LTS and after the upgrade the 24.04 system booted the first time. Afterwards the system always failed to boot. I tried the 6.5 kernel of Linux, still present from 22.04 and the first boot was fine, but here also all following boots failed. I can only boot the system through recovery mode, thus in X11 mode (800x600) and I have to change the display settings manually. In Wayland it does not even reach the login screen. Sometimes e.g Ubuntu Budgie also fail on the first boot, but is OK on the second. Other other versions of Ubuntu from 16.04 ESM till 22.04 LTS work fine and so do Linux Mint 22; Zorin 17; Fedora 40; Manjaro; Debian 12 and OpenSuse Leap 15.5. Also Windows XP, 10 and 11 work fine. I tried to collect more info in recovery mode, but that fails to bring up a browser screen and so I assume that info is last, because the displayed http address did not exsist. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 10 16:01:19 2024 DistUpgraded: 2024-08-10 14:51:35,265 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-01-25 (1660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-40-generic root=UUID=f9b05146-6063-461a-97c0-dc3d4d0f2aef ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to noble on 2024-08-10 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH mtime.conffile..etc.init.d.apport: 2024-07-22T10:59:07 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
