VirtualBox

Ticket #11117 (new defect)

Opened 18 months ago

Last modified 13 months ago

Vbox 4.2.2: Solaris guest shutdown hang on Win 7 host

Reported by: rasta3 Owned by:
Priority: major Component: guest control
Version: VirtualBox 4.2.2 Keywords:
Cc: Guest type: Solaris
Host type: Windows

Description

With a Solaris 10 x64 guest on a Win 7 x64 host, guest shutdown hangs >50% of the time starting with Vbox 4.2.2. In guest as root, I click Launch > Log Out Root > Shut Down. JDS/Xorg windowing shuts down, and disks are synced, but then hang occurs. Guest process must be killed using host Task Manager.

I had done an upgrade install of 4.2.2 from 4.2.0. After these hangs, I uninstalled Vbox completely and reinstalled 4.2.2. Hang problem still occurs.

Issue did not occur with 4.2.0 on same system.

Attachments

vbox4.2.2_guest_shutdown_hang.txt Download (80.4 KB) - added by rasta3 18 months ago.
Log of guest session that experienced shutdown hang
Shutdown-Hang-VBox.log Download (195.6 KB) - added by h-w 18 months ago.
Shutdown hang, Vista 64 Host, Fedora 16 x64 client.
VBox.log Download (56.5 KB) - added by Katana__ 17 months ago.
error-during-acpi-shutdown-of-group-VBox.log Download (84.9 KB) - added by Ryan 17 months ago.
error-after-terminated-VBox.log Download (84.6 KB) - added by Ryan 17 months ago.
debian-guest-shutdown-VBox.log Download (140.0 KB) - added by BuzBox 17 months ago.
Win XP SP3 host, Debian Guest, shutdown hang
ubuntu-guest-shutdown-VBox.log Download (362.2 KB) - added by BuzBox 17 months ago.
Win XP SP3 host, Ubuntu 11.04 Guest, shutdown hang
Windows Server 2008 R2-2012-12-09-13-04-18.log Download (83.3 KB) - added by MarkCranness 17 months ago.
Similar with Server2008R2 guest on Windows7 host : repeated aRC=E_ACCESSDENIED hangs VM shutdown
rhel-6.3-x64-guest-shutdown.log Download (164.0 KB) - added by kingpin 17 months ago.
The same things happens on Windows 7 64 bit host during normal shutdown of Red Hat Enterprise Linux 6.3 x64 guest.
vbox_4.2.6_shutdown_hang.log Download (89.9 KB) - added by kaagle 16 months ago.
Host: Win7, guest: CentOS 6.3 x64, vbox 4.2.6
HIS_Bench2-2013-01-04-00-18-02.log Download (208.1 KB) - added by allein 16 months ago.

Change History

Changed 18 months ago by rasta3

Log of guest session that experienced shutdown hang

comment:1 Changed 18 months ago by mdt-bob

Don't know if this is relevant or not, but I am seeing the same issue with a Windows7 host and guest images of windows xp and windows 7.

I'm running vbox 4.2.0 r80737.

My host computer is a laptop that I have hibernated and brought back numerous times while the vbox guests were running. Not sure if that is relevant or not. During the times leading up to the shutdown of the guests, everything appeared to be operating normally - both on the guests and the host.

comment:2 Changed 18 months ago by rasta3

Same issue occurs in Vbox 4.2.4.

comment:3 Changed 18 months ago by OraBen

For scope, this happened to me on an Oracle Linux 6 u2 host when running vbox 4.2.0 when shutting down an OEL 5 guest OS.

Two things to note:

  • am using a scsi controller
  • running a vmdk disk
  • 16GB VM with 4 CPUs of 16 assigned.

Based on the other reports, I am not sure that the disk is relevant. I have only had this happen once, but found this when researching the same issue and the following error:

29:43:29.415641 VBVA: VRDP acceleration has been disabled. 29:44:29.393029 VRDP: Failed to stop the VRDP input thread rc = VERR_TIMEOUT 29:45:30.019990 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false 29:45:31.019709 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false 29:45:32.019348 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false *repeats every second*

Host OS shows 100% CPU in use for the guest

comment:4 Changed 18 months ago by wpeckham

I run Win7 Pro (HP ProBook laptop) host with a Win7 Pro guest and this happens about 66% of the time. IT does NOT happen to my Linux or ReactOS guests, only Windows!

comment:5 Changed 18 months ago by sunlover

OraBen, please attach a complete VBox.log with this problem.

Changed 18 months ago by h-w

Shutdown hang, Vista 64 Host, Fedora 16 x64 client.

comment:6 Changed 18 months ago by h-w

Same issue on in Vbox 4.2.4. r81684 installed on Vista x64 Home Premium SP2 and various clients, most recently Fedora 16 (x86_64). Log (Shutdown-Hang-VBox.log) attached.

Changed 17 months ago by Katana__

comment:7 Changed 17 months ago by Katana__

Arch Linux host, Arch linux guest. Vbox 4.2.4, same issue, 100% CPU on shutdown. Attaching VBox.log.

Oddity for my situation: I'm using vmdk storage.

edit: I wonder if the others that are having this issue are also using vmdk storage over vdi...?

Last edited 17 months ago by Katana__ (previous) (diff)

comment:8 Changed 17 months ago by rasta3

When the error occurs on guest shutdown, I get 100% CPU usage also. With 4.2.4, I get the hang on guest shutdown >90% of the time. After killing the VirtualBox.exe process, the guest state is "Aborted" in the vbox GUI.

Last edited 17 months ago by rasta3 (previous) (diff)

comment:9 Changed 17 months ago by Ryan

I have also been experiencing shutdown issues lately. It's on a new machine, so I can't be certain it started with 4.2. I'm using Debian 6.0.6 with kernel 2.6.32-5-amd64 as the host. I have two logs to attach.

Edit: I have to apologize. I think I may have gotten my logs mixed up. I think the first log I have attached to this ticket is from a similar situation to the second, but while I was issuing commands manually. It was accompanied by the following error on the console.

VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "COMGETTER(MonitorCount)(&u32)" at line 689 of file VBoxManageInfo.cpp

The second is from a scripted shutdown (error-after-terminated-VBox.log). The guest was shutdown via ACPI. While waiting for shutdown, the script queries for vminfo every second to check if the state has changed to poweroff. The script ran successfully the previous two nights and nothing changed on the host in between.

I don't think I kept logs from an error I believe was similar to this ticket. I descibe it  in the forum. When I manually killed the VBoxHeadless process that was hanging, I got several errors in the GUI (6-12 dialogs). Unfortunately, I didn't think to screenshot them.

I can't seem to get any consistency, but I've seen enough errors now that I'm starting to think it has to do with querying for vminfo while VMState is being changed.

Last edited 17 months ago by Ryan (previous) (diff)

Changed 17 months ago by Ryan

Changed 17 months ago by Ryan

comment:10 Changed 17 months ago by BuzBox

i encouter the same problem every time i shutdown my guest(guest shutdown functionnality, not shutdown from vbox menu).
On both vmdk and vdi machines.
I run a debian squeeze and an ubuntu Natty Narwhal guests, on Windows XP SP3. Intel Core i5 M560@2.67GHz, VBox 4.2.4 r81684

Changed 17 months ago by BuzBox

Win XP SP3 host, Debian Guest, shutdown hang

Changed 17 months ago by BuzBox

Win XP SP3 host, Ubuntu 11.04 Guest, shutdown hang

Changed 17 months ago by MarkCranness

Similar with Server2008R2 guest on Windows7 host : repeated aRC=E_ACCESSDENIED hangs VM shutdown

Changed 17 months ago by kingpin

The same things happens on Windows 7 64 bit host during normal shutdown of Red Hat Enterprise Linux 6.3 x64 guest.

comment:11 Changed 16 months ago by hgohel

Win7 host and VMs with Win7, WinXP - same "hang" after issuing shutdown. Log shows repeated aRC=E_ACCESSDENIED messages as others have posted.

On some occasions I can click on the "x" button in the window frame and VirtualBox will allow me to close the machine down; in that situation VBox shows the machine as powered off. On other occasions it's a hard hang and I have to kill it; on those occasions VBox shows the machine state as "Aborted"

comment:12 Changed 16 months ago by rasta3

Using Vbox 4.2.6, two shutdowns of the Solaris guest have had no hang. Looking good. Was this bug fixed?

comment:13 Changed 16 months ago by frank

Right, there were shutdown fixes with 4.2.6 as well so it indeed might be that your bug was fixed.

comment:14 Changed 16 months ago by CharlesB

Happens to me on Mac Os X host, VB 4.2.4, and Win7 guest, but only when VDI files resides on a network share. If the VDI file is on host's local drive shutdown is OK.

Changed 16 months ago by kaagle

Host: Win7, guest: CentOS 6.3 x64, vbox 4.2.6

Changed 16 months ago by allein

comment:15 Changed 16 months ago by allein

Same here. Host: Win7, guests ubuntu-12.04.1-desktop-i386 fresh installation.

Version 0, edited 16 months ago by allein (next)

comment:16 Changed 14 months ago by olli

Freezing at 100% save state happening to me too.

Virtualbox 4.2.6 r82870
Win7 64bit host
Kubuntu 12.04 64bit guest.

Lot of this error in the VB log:

222:38:29.422054 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

comment:17 Changed 13 months ago by Pantechnic

Me too.

VB 4.2.8 r83876

Windows 8 x64 host

Windows 7 x64 guest

Log ends with 1700 occurrences (so far) of

01:14:37.010956 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

This entry is repeating once per second.

Has happened twice since I installed - both of the times I started it.

Could this be related to use of a USB external hard drive in the guest and not detaching it before shutting down?

On the previous occasion the log looks like this:

<SNIP>
16:44:07.732159 Guest requests the VM to be turned off
16:44:07.742334 Changing the VM state from 'RUNNING' to 'POWERING_OFF'.
16:44:07.742372 ****************** Guest state at power off ******************
<SNIP>
16:44:07.762771 ************** End of Guest state at power off ***************
16:44:07.816434 PDMR3PowerOff: 53 581 011 ns run time
16:44:07.816455 Changing the VM state from 'POWERING_OFF' to 'OFF'.
16:44:07.840554 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
16:44:08.356349 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
16:44:09.363630 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
<SNIP 1,311 occurrences>
17:06:01.356437 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
17:06:02.357207 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
17:06:02.677166 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000a300000 w=1920 h=1200 bpp=32 cbLine=0x1E00, flags=0x1
17:06:02.677215 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000a300000 w=1920 h=1200 bpp=32 cbLine=0x1E00, flags=0x1
17:06:02.856187 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
17:06:02.931148 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000a300000 w=1920 h=1200 bpp=32 cbLine=0x1E00, flags=0x1
17:06:02.934958 VMMDev::SetVideoModeHint: got a video mode hint (1920x1106x0) at 0
17:06:03.039036 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
17:06:03.356473 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
17:06:04.356738 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
17:06:05.357014 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
17:06:06.207412 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is already running or busy (machine state: Stopping)}, preserve=false
17:06:06.278912 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000a300000 w=1920 h=1200 bpp=32 cbLine=0x1E00, flags=0x1
17:06:06.278959 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000a300000 w=1920 h=1200 bpp=32 cbLine=0x1E00, flags=0x1
17:06:06.278967 Display::handleDisplayResize(): Warning: resize postponed.
17:06:06.283589 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000a300000 w=1920 h=1200 bpp=32 cbLine=0x1E00, flags=0x1
17:06:06.356282 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false
17:06:07.357028 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false
<SNIP 21,149 occurrences>
22:58:37.357135 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false
22:58:38.356415 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false
22:58:38.730205 Changing the VM state from 'OFF' to 'DESTROYING'.
22:58:38.730235 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false
22:58:38.730292 ************************* Statistics *************************
<SNIP>
22:58:38.731950 ********************* End of statistics **********************
22:58:38.831426 NAT: zone(nm:mbuf_cluster, used:0)
22:58:38.832013 NAT: zone(nm:mbuf_packet, used:0)
22:58:38.832029 NAT: zone(nm:mbuf, used:1)
22:58:38.832052 NAT: zone(nm:mbuf_jumbo_pagesize, used:0)
22:58:38.832651 NAT: zone(nm:mbuf_jumbo_9k, used:0)
22:58:38.832898 NAT: zone(nm:mbuf_jumbo_16k, used:0)
22:58:38.833029 NAT: zone(nm:mbuf_ext_refcnt, used:0)
22:58:39.149694 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
22:58:39.149727 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false
22:58:39.356673 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false
22:58:39.476243 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false
22:58:40.364968 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The object is not ready}, preserve=false

Note the additional 4 occurrences logged at the very end of this session's log.

The section near the top of this log, involving screen resize failing was me trying to fiddle with the VM window, seeing if I could get it to shutdown gracefully.

It did appear to shutdown gracefully eventually, and this seemed to occur when I returned to it hours later and once again fiddled with the window, though I suppose that could have been a coincidence.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use