3

I have VM running with following configurations:

RAM : 1000MB
Video Memory : 128MB
Enabled : 3D accleration
Guest OS : Ubuntu 13.10 (guest additions)

However my ubuntu is not working fine. I login VirtualBox crashes.

If I decrease RAM to 512MB, I get login loops. Over 1.5GB Virtual box always crashes.

Host System spects :

Intel core i5 @ 2.4GHz quad core,
6GB RAM,
1.6GB Intel HD Graphic 3000,
Windows 7 Home Premium x64

Please tell me what to do.

Thanks

Rajxelton
  • 33
  • 1
  • 1
  • 5
  • Thanks for reply..... here are my system spects : Intel core i5 @ 2..4GHz quad core, 6GB RAM, 1.6GB Intel HD Graphic 3000, Windows 7 Home Premium x64 – Rajxelton Dec 16 '13 at 19:14
  • The best way to add additional information to your question is by editing it, with the edit button. It is better visible that way, and comments are mainly for secondary, temporary purposes. Comments are removed under a variety of circumstances. Anything important to your question should be in the question itself. – guntbert Dec 16 '13 at 19:42

2 Answers2

3

This is a short guide on what to do first when a fresh Ubuntu installation crashes in Virtual Box:

  • Make sure you had enabled VT-x/AMD-V in BIOS.
  • Leave some CPU power for the host (if all cores were assigned, define an execution cap).
  • Leave enough RAM for the host OS (how much depends on the OS and applications running).
  • Install the guest additions.
  • Update your guest Ubuntu for bugfixes:

    1. Boot Ubuntu to the login screen.
    2. Press HOST + F1 for a terminal.
      (alternatively to 1.- 2. we may also boot to a root shell with networking. Then no sudo is needed for commands below)
    3. Type the following commands:

      sudo apt-get update
      sudo apt-get dist-upgrade
      
    4. Enter your password (nothing is displayed!).

    5. Answer Y to download and install updates & bugfixes.
    6. After done type reboot.

    7. In case dkms Install dkms was not installed in the guest we will have to re-install the guest additions.

Takkat
  • 142,284
0

I had the same problem, and was able to solve it by disabling 3D acceleration for the VirtualBox guest.

Eliah Kagan
  • 117,780
Kthxbye
  • 11