F20 in VirtualBox VM

David dgboles at gmail.com
Mon Dec 23 17:37:23 UTC 2013


On 12/23/2013 9:11 AM, Greg Woods wrote:
> On Mon, 2013-12-23 at 09:57 +0800, Ed Greshko wrote:
> 
>> The OP is not a newbie.  He has stated that he has run VBox "since forever" and that F20 works fine in virt-manager. 
>>
>> The last significant post from the OP would indicate he has it running under virt-manager and is not concentrating on trying to find a method to convert VBox VM's to run under virt-manager.
> 
> Just to clarify: I am not a newbie, I have been a Unix sysadmin for
> almost 30 years, and been a Linux sysadmin for almost 15 years. I also
> run Xen virtualization systems at work that implement critical services
> such as DNS and authentication, so I am not new to the concept of
> virtualization either. I use VirtualBox at home just to run a couple of
> Windows VMs. All that said, it still often happens that someone else
> will think of something that I have not, or have a piece of knowledge
> that I lack, so even very experienced people may occasionally ask for
> help on a mailing list. I am not afraid to do that and I have often
> received very helpful advice.
> 
> 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.
> 
> As a workaround, I attempted to install F20 on a VM under KVM. The
> install works, but the VM runs dog slow (so slow that it's useless). 
> 
> So as of now, I still do not have a usable F20 VM. But I have moved on
> to other projects, since this wasn't something that was critically
> important. And this thread has now degenerated into something that is no
> longer related to the actual topic.
> 
> --Greg
> 
> 


I stand corrected. My bad. Sorry.

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' or to 'set
the resolution' in the boot.

I do *not* know if these work, I never needed to try it.

Good luck.

-- 

  David


More information about the users mailing list