Stuck at Stopping

[citapinc]

I created a VM of Windows Server 2008 64-bit R2. I changed the network adapter to bridge mode and the VM locked up. So I executed a APIPowerDown via the VBOXManage to shut it down.

Dow the VM screen is black and the VM Desktop shows the status as Stopping but nothing is happening. I've left it this way for 6 hours now and it still shows as Stopping and the VM screen is black.

How can I properly stop this VM?

[Jeff_Mtl]

I have a similar issue with VirtualBox 3.2.10.
I have a Linux VM running on my Windows Vista host. Used this VM for a while now without any problem stopping and starting it.
Now I tried to stop the VM as usual using the "Send the shutdown signal" option but it's now stucked in the Stopping state.

Any idea how to recover from this?

Thanks,
Jeff

[Mapson.John]

*bump*

VirtualBox 3.2.12
Host: Windows server 2008 R2
Guest: CentOS 5.5

I've shut down the guest trough the KDE shutdown menu.
The Guest shuts down all the way to:

Code: Select all

Halting system...
md: stopping all md devices.
Synchronizing SCSI cache for disk sda:
sd 0:0:0:0: [sda] Stopping disk
ACPI: PCI interrupt for device 0000:00:11.0 disabled

Then the only option available in VirtualBox is "Close", wich has no effect.
- Killing the application trough task manager works.
- When restarting VirtualBox, the guest is marked as "aborted"
- Starting the guest performs a clean boot
- Shutting down after that works without a problem, so i don't know how to reproduce the issue
- Changes from the crashed state seem to be stored, so killing the application seems like a workable workaround

[rizzo]

I'm having this same problem today.

VirtualBox 4.0
Host: Win 7 64-bit
Guests: Oracle Enterprise Linux 5.5 64-bit

[rizzo]

Log is full of these at the end:

Code: Select all

03:17:14.741 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
03:17:15.756 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
03:17:16.769 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
03:17:17.783 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
03:17:18.797 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
03:17:19.811 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false

It is appending a new line like this to the vbox log every second.

[rizzo]

I've created a vbox ticket for my issue: http://www.virtualbox.org/ticket/8016

[darby]

In case anyone else encounters this issue, here's what I did to fix it (could be wrong, but it worked for me!)

• From the main VirtualBox Manager screen, right click on the OS with the 'Stopping' problem
• Choose 'Show in Finder' (or Explorer if you're on Windoze)
• Quit VirtualBox
• *Temporarily* remove the .vbox files associated with that OS (I had two, .vbox and .vbox-prev)
• I then tried loading VirtualBox, but it had some sort of failed error message by the OS....
• So quit VirtualBox
• Put the files back in the folder
• Reload VirtualBox

And it should be fixed....maybe?:)

[Shekhar]

I had same problem and I noticed that Virtual machine was still running in Windows Task Manager. I killed the process and then restarted Oracle virtual box and noticed that state showed as aborted.

Hope this helps.

[Rick47]

I had the same problem. I had to exit Virtual Box manager, and then kill the virtualbox process from task manager. Bringing it back up, it came up as aborted. Trying to restart it, it seemed to be going nowhere. I used the Manager to send a reset, that resulted in a successful reboot.
HTH.