Version
7.2.8
Host OS Type
Solaris
Host OS name + version
Oracle Solaris 11.4 Common Build Environment 11.4.90
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
SystemRescue 13.00
Component
Other
What happened?
My host is currently running Solaris 11.4.90, but I experienced the same problem with Solaris 11.4.81.
I've tried VirtualBox 7.2.4, 7.2.6 and 7.2.8. All have the same issue which makes VirtualBox unusable.
The /opt/VirtualBox/amd64/VirtualBox and /opt/VirtualBox/amd64/VirtualBoxVM processes never exit after powering off the VM and closing the GUI and need to be killed manually.
The /opt/VirtualBox/amd64/VBoxHeadless processes exit, though.
I have been using VirtualBox 7.1.x for a long time and there is no such problem.
The CPU on the host is Intel Xeon E5-1620 v4.
I performed a test on a different computer with an AMD Ryzen CPU inside a VMware Workstation VM using nested virtualization.
I performed a clean installation of Solaris 11.4.90, installed the solaris-desktop package and then installed VirtualBox 7.2.8.
I found exactly the same issue as on my server: VirtualBox and VirtualBoxVM never exit.
I am attaching a log file from SystemRescue 13.00 guest running inside VMware with nested virtualization, but it really doesn't matter what is the guest OS.
VBox.log
I doubt that the log will be useful, though, because it ends the same way as the log of VirtualBox 7.1, which exists normally.
How can we reproduce this?
Install VirtualBox 7.2.8 on Solaris 11.4 host. Start the GUI and close it. You should find the /opt/VirtualBox/amd64/VirtualBox process still running.
Create a VM and start it normally (not headless). Shut down the guest OS and observe the /opt/VirtualBox/amd64/VirtualBoxVM process still running.
Did you upload all of your necessary log files, screenshots, etc.?
Version
7.2.8
Host OS Type
Solaris
Host OS name + version
Oracle Solaris 11.4 Common Build Environment 11.4.90
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
SystemRescue 13.00
Component
Other
What happened?
My host is currently running Solaris 11.4.90, but I experienced the same problem with Solaris 11.4.81.
I've tried VirtualBox 7.2.4, 7.2.6 and 7.2.8. All have the same issue which makes VirtualBox unusable.
The /opt/VirtualBox/amd64/VirtualBox and /opt/VirtualBox/amd64/VirtualBoxVM processes never exit after powering off the VM and closing the GUI and need to be killed manually.
The /opt/VirtualBox/amd64/VBoxHeadless processes exit, though.
I have been using VirtualBox 7.1.x for a long time and there is no such problem.
The CPU on the host is Intel Xeon E5-1620 v4.
I performed a test on a different computer with an AMD Ryzen CPU inside a VMware Workstation VM using nested virtualization.
I performed a clean installation of Solaris 11.4.90, installed the solaris-desktop package and then installed VirtualBox 7.2.8.
I found exactly the same issue as on my server: VirtualBox and VirtualBoxVM never exit.
I am attaching a log file from SystemRescue 13.00 guest running inside VMware with nested virtualization, but it really doesn't matter what is the guest OS.
VBox.log
I doubt that the log will be useful, though, because it ends the same way as the log of VirtualBox 7.1, which exists normally.
How can we reproduce this?
Install VirtualBox 7.2.8 on Solaris 11.4 host. Start the GUI and close it. You should find the /opt/VirtualBox/amd64/VirtualBox process still running.
Create a VM and start it normally (not headless). Shut down the guest OS and observe the /opt/VirtualBox/amd64/VirtualBoxVM process still running.
Did you upload all of your necessary log files, screenshots, etc.?