Changing the VM state from 'DESTROYING' to 'TERMINATED'

[Rickye]

Hello techies..!!

I'm using Ubuntu and VirtualBox for many years but recently I'm facing a new error while trying to install "Windows 10" inside VirtualBox.

The last few lines of the log stating that (Changing the VM state from 'DESTROYING' to 'TERMINATED') for an unknown reason.

Unable to install "Windows 10" VirtualBox for around a week and tried uninstalling current version 7.x.x, reinstalling, installing previous version 6.x.x but nothing works for me.

Could anyone kindly help me with this?

I'm using Ubuntu 22.04.2 LTS, trying to use VirtualBox 7.x.x

Note:- Log file is 362kb but the form is allowing less than 128 kb. so I attached the log file compressed, thanks..

[mpack]

ALL log files end in termination, that is not an error.

Your VM ends because it hit a "Guru Meditation" error.

00:00:02.727287 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:02.727348 Console: Machine state changed to 'Stuck'
00:00:02.729069 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:02.729071 !!
00:00:02.729072 !! VCPU0: Guru Meditation -37 (VERR_NOT_SUPPORTED)
00:00:02.729080 !!
00:00:02.729099 !!

Make sure you don't have another VM platform running, e.g. KVM or Docker. Installed is OK, running is not.

[Rickye]

Thanks a ton @mpack. Yes, recently I installed and ran Docker.

Please let me know how can I stop the Docker service and enable the Docker service when required.

So that I can use both as well as per requirement (VirtualBox and Docker service) any one service at a time.

The below are the output when I ran "ps" command.

rick@rick-Lenovo-Product:~$ ps -ef | grep docker
rick 28646 28472 0 21:23 pts/0 00:00:00 grep --color=auto docker
rick@rick-Lenovo-Product:~$

[Rickye]

I've tried the below command to stop the Docker and Docker service, it's shows inactive or dead

Please find the attached image..

rick@rick-Lenovo-Product:~$ sudo systemctl status docker
[sudo] password for rick:
○ docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
Active: inactive (dead)
TriggeredBy: ● docker.socket

rick@rick-Lenovo-Product:~$ sudo service docker status
○ docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
Active: inactive (dead)
TriggeredBy: ● docker.socket

rick@rick-Lenovo-Product:~$ sudo systemctl stop docker
Warning: Stopping docker.service, but it can still be activated by:
docker.socket
rick@rick-Lenovo-Product:~$ sudo service docker stop
Warning: Stopping docker.service, but it can still be activated by:
docker.socket
rick@rick-Lenovo-Product:~$

[Rickye]

Please let me know that the docker service have been stoped? (please refer the attached terminal image in previous post) or how can I stop any command please?

[scottgus1]

FWIW, you'd really have to ask Docker how to stop their services. We grok Virtualbox here, they'd handle Docker better.

[fth0]

With lsmod | grep kvm you can find out if the KVM kernel module is in use, and with lsof /dev/kvm you can find out who is using the KVM kernel device. Please show the output of these commands.

[Rickye]

Thanks for your inputs fth0, this is the output I'm getting

rick@rick-Lenovo-Product:~$ lsmod | grep kvm
kvm_intel 434176 2
kvm 1130496 1 kvm_intel
rick@rick-Lenovo-Product:~$ lsof /dev/kvm
rick@rick-Lenovo-Product:~$

[Rickye]

Dear fth0/ all, this morning (an hour before) I've tried installing "Windows 10 Guest" inside the VirtualBox and experienced the same error.

I've attached the recent log file for your view, please check it out. please guide me on how to get VirtualBox to work fine?

FYI, it is important to me to have a "Windows 10" for some of my office files to be edited in "MS Office", but unfortunately I am stuck here.

[fth0]

rick@rick-Lenovo-Product:~$ lsmod | grep kvm
kvm_intel 434176 2
kvm 1130496 1 kvm_intel

This shows that the kvm_intel module, which uses the kvm module, was in use while the lsmod command was executed. If the use count (2 here) is greater than 0, at least one process is using KVM, and any VirtualBox VM will crash with the Guru Meditation.

rick@rick-Lenovo-Product:~$ lsof /dev/kvm
rick@rick-Lenovo-Product:~$

Unfortunately, listing the current users of the kvm device is not a sure way to identify the current users of the kvm module, as you can see here. If you start a QEMU/KVM VM for a test (e.g. qemu-system-x86_64 -enable-kvm), you should see the qemu-system-x86_64 process in the lsof output. An additional idea is to search the dmesg output for kvm.

I don't know a failsafe method for identifying the user of a Linux kernel module (kvm_intel here). In your case, since Docker is a candidate, you could uninstall Docker for a test, reboot the host and check again with lsmod if Docker is the culprit.

[Rickye]

okay, guess uninstalling Docker will do works VirtualBox, my plan is also the same though

Once I'll get done I'll post here that VirtualBox is ok and get to work installing Windows Guest.