Opened 13 years ago

Closed 13 years ago

#8008 closed defect (fixed)

UI Frozen on pause

Reported by: Edward Yang Owned by:
Component: GUI Version: VirtualBox 4.0.0
Keywords: Cc:
Guest type: Linux Host type: Windows


It's quite annoying. I did 'yum update' in guest Fedora. There was much disk activities while yum was installing updates.

I selected Pause from File menu and the UI froze that turned to a all-white window.

And it seemed the guest os was dead too because I saw no disk activities then.

Attachments (1)

Logs.7z (22.8 KB ) - added by Edward Yang 13 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 by Frank Mehnert, 13 years ago

Is there a VBox.log file from such a session available?

comment:2 by Edward Yang, 13 years ago

Note - I have encountered about 5-8 crashes and frozen condition for the last one year of using VirtualBox.

That's not bad.

But compared to commercial VMware and Microsoft Virtual PC, 5 times is bad - far from commercial quality.

BTW, I had 0 crashes on VMware and less than 3 crashes on VPC, for a period of more than 3 years.

comment:3 by Frank Mehnert, 13 years ago

Yes, but complaining does not help us identifying the bug. I still don't see the information I requested.

comment:4 by Edward Yang, 13 years ago

After I aborted the session, restarted and did 'yum update', I want to save the session. But the window froze again, completely unexpected because there was little activities inside the guest os.

comment:5 by Frank Mehnert, 13 years ago

I still would like to see the VBox.log file.

by Edward Yang, 13 years ago

Attachment: Logs.7z added

comment:6 by Edward Yang, 13 years ago

Get a frozen UI again.

Last line of log: 00:37:27.235 Changing the VM state from 'RUNNING' to 'SUSPENDING'.

comment:7 by Frank Mehnert, 13 years ago

In that case the guest most likely entered an ACPI sleep state. Disabling the guest power management will fix this issue. You can also prevent this behavior by doing the following:

VBoxManage setextradata VM_NAME \
  VBoxInternal/Devices/acpi/0/Config/ PowerS1Enabled 0

VBoxManage setextradata VM_NAME \
  VBoxInternal/Devices/acpi/0/Config/ PowerS4Enabled 0

The was a change in behavior with VBox 4.0.0 which will be reverted in the next maintenance release.

comment:8 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: newclosed

The old 3.2.12 behavior should be back with VBox 4.0.4.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use