Ticket #1972 (closed defect: fixed)

Opened 11 years ago

Last modified 10 years ago

A CEntOS 4.6 VM never finish to boot.

Reported by: svbu12 Owned by:
Component: other Version: VirtualBox 1.6.4
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by frank) (diff)

The PC's hardware:

  • CPU: Intel Pentium 4 3.2 GHz Dual Core.
  • RAM: 3 GB
  • OS: Linux CEntOS 4.6 With all patches.
  • VM RAM: I assigned a whole GB of RAM just for the VM.

Problem Description:

  1. I downloaded a DVD-ROM .ISO of CentOS-4.6-i386-binDVD.iso from the  CentOS mirror
  2. I start Sun VBox.
  3. I create a new VM.
  4. I install CEntOS 4.6 from the DVD image.
  5. I follow directions and install a CEntOS 4.6 into a logical VM 30 GB disk.
  6. The install process works properly until the end.
  7. Once it is completed, I reboot the VM, Then I change the boot order from DVD image to VM 30 GB hdd.
  8. I click on the start button to restart the CEntOS 4.6 VM.
  9. All we see is a black screen. even after an hour, it never change.

Other info:
I know the DVD image run properly. I used it to install the physical machine.

I know Sun VBox works properly too. I can run Linux DSL, Ubuntu 8.08, CentOS 5.2 And a few other very properly...


2008-08-17-19-30-32.024-VirtualBox-24536.log Download (17.7 KB) - added by svbu12 11 years ago.
Virtual Box 1.6.4 log of a session with CEntOS 4.6

Change History

Changed 11 years ago by svbu12

Virtual Box 1.6.4 log of a session with CEntOS 4.6

comment:1 Changed 11 years ago by svbu12

When the VM is trying to boot, the CPU on the physical computer is used to 100%. Each cores of the CPU are sharing the load.

Thanks for the Good Job.

comment:2 Changed 11 years ago by frank

  • Description modified (diff)

Please could you

  • retry the installation with VirtualBox 1.6.6 and/or VirtualBox 2.0.2 and then
  • attach the correct VBox.log file. You will find the file when going to the main selector window and selecting Machine / Show Log ...

comment:3 Changed 11 years ago by nosrednakram

I believe this is because PAE/NX is not enabled in advanced, general settings. I just had the same issue until I enabled PAE/NX.

comment:4 Changed 10 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

No response, closing. Before re-opening make sure that you checked the latest release 2.2.2.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use