Ticket #8230 (closed defect: obsolete)

Opened 7 years ago

Last modified 4 years ago

Ubuntu guest isn't stable under MacOS host

Reported by: yurivict Owned by:
Priority: major Component: other
Version: VirtualBox 4.0.0 Keywords:
Cc: Guest type: Linux
Host type: Mac OS X

Description (last modified by frank) (diff)

version 4.0.0.r69151 i386 on Darwin 10.6.0 i386

On the surface it seems like it works fine. But under heavy load strange things begin happening.

I have 2GB memory and 2 cores on my laptop and I have set 1515MB memory for Ubuntu and 2 CPUs (quite extreme setting but it should still work). When I run some compile with large memory and CPU consumption gnome terminal stops accepting keystrokes. System aborts randomly. Sound playing in the Chrome browser begins to play slower than its supposed to. Unable to close Chrome browser. ACPI shutdown signal doesn't cause full Ubuntu shutdown, only causes the shutdown window with options to appear.

Try using Ubuntu guest for various things plus run large compile and you will see the same issue.


VBox.log Download (47.1 KB) - added by yurivict 7 years ago.
log file

Change History

Changed 7 years ago by yurivict

log file

comment:1 Changed 7 years ago by frank

I don't agree that this should work. Note that your host needs a notable amount of RAM as well. Furthermore, the guest RAM is not allocated immediately but only on demand. That explains why you don't observe these problems when just starting the VM but when executing some memory-intensive jobs. The warning in the GUI is not there for fun, it actually makes sense.

If the system aborts due to this memory condition then please attach a proper VBox.log and a crash log to this ticket. The attached VBox.log does not show any problem.

comment:2 Changed 7 years ago by yurivict

I agree that this is not an optimal condition, but its good to stress test the system. It should maybe work slower but should never abort.

I will attach the log when this happens next.

In general its hard to understand what time vbox log records refer to since they only have some numbers in there like this: 00:00:03.734

comment:3 Changed 7 years ago by frank

Quite easy :-) This is the time since the start of the VM (hours:minutes:seconds:milliseconds).

comment:4 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use