CentOS - Nov 2010 - Snag installing CentOS in a VirtualBox VM

I spent most of the evening trying to boot a new install of CentOS in a
VirtualBox VM.  The VM recognizes the install DVD, runs it, asks for me to
boot it and I type in <return> (or any number of other combinations, all
of
which fail in exactly the same way) and it continues to run up to the point
shown in the attached screenshot.

I've tried numerous different combinations of device alternatives, even
turned off the virtual NIC, and no joy.  I tried marking it as a Red Hat
Linux and as Other Linux - same results.

I know this isn't a VB forum, but I'm just wondering....

Thanks.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20101117/0a3e21f5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: VBCentOSFail.png
Type: image/png
Size: 31031 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20101117/0a3e21f5/attachment-0001.png>

Mark wrote:
> I spent most of the evening trying to boot a new install of CentOS in 
> a VirtualBox VM.  The VM recognizes the install DVD, runs it, asks for 
> me to boot it and I type in <return> (or any number of other 
> combinations, all of which fail in exactly the same way) and it 
> continues to run up to the point shown in the attached screenshot.
>
> I've tried numerous different combinations of device alternatives, 
> even turned off the virtual NIC, and no joy.  I tried marking it as a 
> Red Hat Linux and as Other Linux - same results.
The only problem I've had running stuff on VirtualBox is that you have 
to manually enable PAE if you're booting a kernel that uses it.  What 
architecture are you running?  How much memory do you have assigned to 
the VM?

-Greg

On 17/11/10 11:36, Mark wrote:
> I spent most of the evening trying to boot a new install of CentOS in a
> VirtualBox VM.  The VM recognizes the install DVD, runs it, asks for me
> to boot it and I type in <return> (or any number of other
combinations,
> all of which fail in exactly the same way) and it continues to run up to
> the point shown in the attached screenshot.
I know this error. Workaround is to enable IO APIC in the virtual 
machine configuration.

-- 
Veiko