VirtualBox

Ticket #8060 (closed defect: fixed)

Opened 3 years ago

Last modified 13 months ago

Sometimes Windows Server 2003 R2 (guest) cannot shutdown

Reported by: nim Owned by:
Priority: critical Component: other
Version: VirtualBox 4.0.0 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description (last modified by frank) (diff)

I installed a Windows Server 2003 R2 inside Virtual Box. I had observed several times that this guest OS could not shutdown properly - it stayed with a blank screen.

I'm 99% sure that it's a problem of Virtual Box because I have never had such a problem with other VMs (VPC, VMWare).

Attachments

Logs.7z Download (22.7 KB) - added by nim 3 years ago.
VBox.log Download (92.5 KB) - added by nim 3 years ago.
VBox.2.log Download (143.8 KB) - added by nim 3 years ago.
Have to power off the VM
VBox.3.log Download (67.4 KB) - added by nim 3 years ago.
Changing the VM state from 'DESTROYING' to 'TERMINATED'

Change History

Changed 3 years ago by nim

comment:1 Changed 3 years ago by frank

Unfortunately all 4 logs you attached show that the machine was shut down cleanly.

comment:2 Changed 3 years ago by nim

No actually.

If you look at the most recent VBox.log, you will find the last 2 lines:

16:08:30.579 Changing the VM state from 'DESTROYING' to 'TERMINATED'. 16:08:32.647 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console} aText={The virtual machine is not powered up}, preserve=false

I think it's a very simple mistake in logic. The VM was indeed shutdown, but when it was changed from 'DESTROYING' to 'TERMINATED', program logic somehow thinks the VM is not powered up, which is true since it was destroying. But this should not be an error, instead program logic should consider 'DESTROYING' to 'TERMINATED' is valid.

comment:3 Changed 3 years ago by frank

Moment. The line Changing the VM state from 'DESTROYING' to 'TERMINATED'. is independent from the next line and there is no sign that the VM was not properly terminated. But ok, in the description you say that the guest window stayed with a black screen. So it's definitely something wrong.

comment:4 Changed 3 years ago by nim

I was installing the latest 4.0.4 addition in this guest OS and rebooting, and it seems the VM is dead. By examining the log file I see it's constantly appending the following same line to the log file:

00:27:44.756 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_TRY_AGAIN)}, preserve=fals

Changed 3 years ago by nim

comment:5 Changed 3 years ago by nim

And, again the guest window stayed with a blank (not black) screen - it's the screen just before powering off.

Changed 3 years ago by nim

Have to power off the VM

Changed 3 years ago by nim

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

comment:6 Changed 3 years ago by nim

Attaching a new log file.

The log shows the VM was shutdown correctly, but the UI window stayed blank.

comment:7 Changed 13 months ago by nim

It's an old issue. Please close it.

comment:8 Changed 13 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
  • Description modified (diff)

Thanks!

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use