Version
7.2.10
Host OS Type
Linux
Host OS name + version
Kubuntu 26.04 LTS
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Kubuntu 26.04 LTS
Component
GUI
What happened?
When attempting to create a new VM with an ISO built by Cubic (Custom Ubuntu ISO Creator), VBoxSVC crashes and all running VMs are forcibly terminated. This occurs on both release and development builds of VirtualBox, and has been occurring for quite some time.
Logs from journalctl related to the crash:
vbox-crash-logs.txt
How can we reproduce this?
Steps to reproduce:
- Install the latest test build of VirtualBox from https://www.virtualbox.org/wiki/Testbuilds.
- Obtain an Ubuntu ISO built with Cubic. You can generate this yourself (steps are included below), or you can use the Kubuntu Focus OEM image which is a Kubuntu ISO rebuilt with Cubic to include Kubuntu Focus tools on it.
- Open VirtualBox.
- In the top bar, click "New".
- Set the VM name to
cubic-test.
- Click the ISO Image drop-down, then click "Other".
- Navigate to the location of the Cubic-built ISO, and double-click it.
Expected result: VirtualBox should show the ISO name in the "ISO Image" field, and should attempt (not necessarily succeed but at least attempt) to autodetect the OS within the ISO.
Actual result: VBoxSVC crashes. A "VirtualBox - Error" window appears stating "Failed to set the global VirtualBox extra data for key GUI/RecentFolderCD to value {/path/to/dir/containing/iso}." The "Details" drop-down reveals "Callee RC: NS_ERROR_ABORT (0x80004004). If any VMs were running, "critical error" popups will appear and the VMs will be forcibly terminated.
To generate an ISO that can be used to reproduce this:
- Download the latest Kubuntu 24.04 LTS ISO from here.
- Install Cubic from here.
- Click the "Select a project directory" button next to the drop-down field on the first page, then create a new directory with your desired name, then click "Select".
- Click "Next".
- Click the button next to the "Filename" field, then navigate to and select the Kubuntu ISO downloaded earlier.
- Click "Next".
- Wait for the "Customize" page to appear.
- Click "Next" again without making any changes to the ISO.
- On the "Select packages to be automatically removed..." screen, click "Next".
- On the "Make changes to advanced options..." screen, click "Next".
- On the "Select the compression for the Linux file system" screen, click "Next".
- Wait for the ISO build to finish.
The built ISO can be used in the above reproduction steps to crash VBoxSVC.
Did you upload all of your necessary log files, screenshots, etc.?
Version
7.2.10
Host OS Type
Linux
Host OS name + version
Kubuntu 26.04 LTS
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Kubuntu 26.04 LTS
Component
GUI
What happened?
When attempting to create a new VM with an ISO built by Cubic (Custom Ubuntu ISO Creator), VBoxSVC crashes and all running VMs are forcibly terminated. This occurs on both release and development builds of VirtualBox, and has been occurring for quite some time.
Logs from journalctl related to the crash:
vbox-crash-logs.txt
How can we reproduce this?
Steps to reproduce:
cubic-test.Expected result: VirtualBox should show the ISO name in the "ISO Image" field, and should attempt (not necessarily succeed but at least attempt) to autodetect the OS within the ISO.
Actual result: VBoxSVC crashes. A "VirtualBox - Error" window appears stating "Failed to set the global VirtualBox extra data for key GUI/RecentFolderCD to value {/path/to/dir/containing/iso}." The "Details" drop-down reveals "Callee RC: NS_ERROR_ABORT (0x80004004). If any VMs were running, "critical error" popups will appear and the VMs will be forcibly terminated.
To generate an ISO that can be used to reproduce this:
The built ISO can be used in the above reproduction steps to crash VBoxSVC.
Did you upload all of your necessary log files, screenshots, etc.?