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
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.
On Wed, Nov 17, 2010 at 5:44 AM, Veiko Kukk veiko.kukk@krediidipank.ee wrote:
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.
That was it - thanks.
Funny, though, my WinXP VB VM works fine without it. Seems like VB should have some intelligent defaults built in since it already "needs" to know what OS one is installing, but that's probably better aimed at a VB discussion list....
-
Greg Bailey -
Mark -
Veiko Kukk