F20 in VirtualBox VM

[Ed Greshko]

On 12/24/13 09:31, Greg Woods wrote:
> On Mon, 2013-12-23 at 12:37 -0500, David wrote:
>> On 12/23/2013 9:11 AM, Greg Woods wrote:
>>> I started this thread because I was trying to install an F20 VM under
>>> VirtualBox on an F19 system.  I do know how to use VB to connect the DVD
>>> ISO to the VM and install an OS. The problem is that when I do this with
>>> the F20 ISO, syslinux boots and the first Anaconda selection screen
>>> comes up. I select "Install Fedora", and I get nothing but a black
>>> screen after that. I still have not solved this problem.
>> I have never had this problem but I see several users post about it. As
>> I recall it the suggestions were 'to install in text mode' 
> Thanks for that idea. It didn't work, but it did tell me what's wrong.
> Somehow, the version of VirtualBox that I have doesn't actually support
> 64-bit VMs, even though it comes from an x86_64 RPM:
>
> # rpm -qa | fgrep VirtualBox
> VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64
>
> But when I do start the install in text mode (and erase "quiet" from the
> kernel command line), the error message is that it's a 32-bit CPU and
> I'm trying to boot a 64-bit kernel. Is it actually possible to install a
> 64-bit VM in VirtualBox, and if so, where do I get a version that
> supports it? The one I got came straight from the Downloads page at
> virtualbox.org, and when creating the VM by pressing the New button, it
> doesn't give any "64 bit" choices, just "Fedora".
>

FWIW.....  On my F19 system....

[egreshko at meimei ~]$ rpm -qa | fgrep VirtualBox
VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64
[egreshko at meimei ~]$ uname -a
Linux meimei 3.12.5-200.fc19.x86_64 #1 SMP Tue Dec 17 22:21:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

On the F20 VM .....

[egreshko at f20f ~]$ uname -a
Linux f20f.greshko.com 3.12.5-302.fc20.x86_64 #1 SMP Tue Dec 17 20:42:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

So, with the same rpm from Oracle that you have, I have no problem.....

I guess you're 100% certain your host system is running a 64bit F19? :-) :-)   Or, maybe, there is a bug in VBox running on your F19 system that fails to detect your hardware/OS is 64 bit?





-- 
Getting tired of non-Fedora discussions and self-serving posts