virtualbox.org

VB v4.1.18.

I've got a number of Windows XP guests on a Windows 7 x64 host.

At random times they hang on shutting down. A common listing in the log is below. If the error line is after the changing line, then it hangs.

00:02:29.547 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
00:02:29.596 Changing the VM state from 'DESTROYING' to 'TERMINATED'.

Any ideas?

The error line you highlight is common and AFAIK harmless. We would need the complete log, as a zipped attachment please.

I've had that happen sporadically for as long as I can remember (v3 and up). I also believe that it is harmless - except you get "Aborted" with a scary icon in VirtualBox GUI on the crashed VM. Will remember to bring some logs with me next time

I've attached the Log as requested.

Hmm. I'm not sure I'm intepreting the log correctly, but it looks to me as if you hit the "Close" button on the VM window when the VM was already in the process of closing down, and had in fact just changed the VM state to "off" something like a microsecond before. This may have triggered some confusion (e.g. that long series of errors) as the VM attempted to shut down an already shut down process.

I would suggest that next time you just leave it a bit longer to do its own thing, and see if you continue to have problems.

Unfortunately that isn't the case. The process goes as follows:
1) I tell the XP guest to perform a shut down.
2) It performs the shutdown to the point where the guest screen goes black.
3) The VB window has a status of Shutting Down.
4) I wait from anything from a minute to 10 minutes one time.
5) I then select it and try all sorts of things, like even pressing the close button and right clicking the window to see if I can close it any other way.
6) I have to reboot the host to forcefully shut down the process.

When the host reboots, the guest reports a failed shut down. (Aborted I think the message is)

The good news is that I've not corrupted the XP guest (as of yet!), but I expect that might only be a matter of time until the bug is fixed.

I just had 2 VM's hang on shutdown and the Manager also. I had to reboot the host to get control back. I've attached the logs of both VM's so you can see a bad shutdown vs the last good shutdown.

In the case of the Build VM, until I went back to the Manager (before it hung) I didn't know it had not finished shutting down. I also tried changing the number of CPU's assigned on this VM but no difference.

It was the Main XP VM that had the non-closed "Shutting Down" window, which I was waiting for. I went to the Manager and saw the Build VM still Running status, then when I clicked the Main VM again, there was no response from either window after that.

One more thing, this time, after the reboot, both VN's report "Powered Off", instead of the normal error.