F5F Stay Refreshed Software Operating Systems Issue with VirtualBox 7.1.2 launching not responding

Issue with VirtualBox 7.1.2 launching not responding

Issue with VirtualBox 7.1.2 launching not responding

B
beschteLars
Member
221
08-15-2023, 03:52 PM
#1
I attempted to launch VirtualBox but encountered an error. Please check the setup and try again. Your system specs are listed, and you're using Zorin OS 17.2 with BIOS features enabled—consider verifying compatibility or updating drivers.
B
beschteLars
08-15-2023, 03:52 PM #1

I attempted to launch VirtualBox but encountered an error. Please check the setup and try again. Your system specs are listed, and you're using Zorin OS 17.2 with BIOS features enabled—consider verifying compatibility or updating drivers.

S
squidthekidRC
Member
64
08-18-2023, 04:12 AM
#2
No, I haven't tried it.
S
squidthekidRC
08-18-2023, 04:12 AM #2

No, I haven't tried it.

S
Sly202001
Member
169
08-18-2023, 07:10 AM
#3
yes i did
S
Sly202001
08-18-2023, 07:10 AM #3

yes i did

I
IvyTheCat
Member
208
08-22-2023, 03:41 AM
#4
The logs in /var/log/vbox-setup.log record system events, errors, and activities related to the vbox setup process. They typically detail installation steps, configuration changes, and any issues encountered during deployment.
I
IvyTheCat
08-22-2023, 03:41 AM #4

The logs in /var/log/vbox-setup.log record system events, errors, and activities related to the vbox setup process. They typically detail installation steps, configuration changes, and any issues encountered during deployment.

V
VortexAh
Member
160
08-22-2023, 08:27 AM
#5
Your file is ready, and the BIOS is set to disable TPM. The log file has been recorded.
V
VortexAh
08-22-2023, 08:27 AM #5

Your file is ready, and the BIOS is set to disable TPM. The log file has been recorded.

T
Taillowbird
Member
158
08-23-2023, 12:10 PM
#6
I confirmed it functions correctly at the provided link. The solution involved updating the GCC version using the specified steps.
T
Taillowbird
08-23-2023, 12:10 PM #6

I confirmed it functions correctly at the provided link. The solution involved updating the GCC version using the specified steps.