I am running VirtualBox under F19, and I wanted to try F20 in a VM, but I can't get it to install. With both the Live ISO and the full DVD iso, if I point the virtual DVD drive at the ISO, it boots into the main syslinux/Anaconda menu, but as soon as I select "Install Fedora", the screen goes black and nothing ever happens. Has anyone installed F20 into a VirtualBox VM?

Yes. Been installing and testing F20 on a VM for a while now. But make sure you're running VirtualBox 4.3.6

At some point I'd like to move away from depending on Oracle

On 12/20/13 09:26, Greg Woods wrote: > On Fri, 2013-12-20 at 08:04 +0800, Ed Greshko wrote: > >> Yes. Been installing and testing F20 on a VM for a while now. >> >> But make sure you're running VirtualBox 4.3.6 > Thanks for the tip, I was on 4.3.4 . So I upgraded to 4.3.6, installed > the extension pack, and... I still get a black screen after selecting > "install Fedora 20" from the Anaconda/syslinux boot menu. > That is odd..... FWIW, my F19 host is 64bit and I'm using the rpmfusion nVidia stuff to drive the host system video. Also, I've only installed/tested F20 in 64 bit.

When I select Install the screen goes black for about 5 seconds, then goes white for about 10 seconds and then black with scrolling messages.

You have verified the checksums of the downloaded ISO's?

Am 20.12.2013 00:50, schrieb Greg Woods: > I am running VirtualBox under F19, and I wanted to try F20 in a VM, but > I can't get it to install. With both the Live ISO and the full DVD iso, > if I point the virtual DVD drive at the ISO, it boots into the main > syslinux/Anaconda menu, but as soon as I select "Install Fedora", the > screen goes black and nothing ever happens. Has anyone installed F20 > into a VirtualBox VM? > > Thanks, > --Greg I had success with VirtualBox and F20 on two machines, after initially having this very black screen on several trials. So please don't mind my question: When creating the new VM in VBox Manager, did you choose the correct version of Fedora? I clicked on "Fedora" and I missed that there was an entry "Fedora (64bit)" ...

It worked for me when I selected "Red Hat (64 bit)" as the OS type.

On 12/20/2013 11:28 AM, Klaus-Peter Schrage wrote:

> my question: When creating the new VM in VBox Manager, did you choose > the correct version of Fedora? I clicked on "Fedora" and I missed that > there was an entry "Fedora (64bit)" ... > It worked for me when I selected "Red Hat (64 bit)" as the OS type.

> Something may be more fundamentally wrong than I thought. I don't see > "64 bit" as a choice anywhere in Vbox Manager.

Which repo is your virtualbox from?

On 12/22/13 22:53, Greg Woods wrote: > The RPM I have installed is VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64 > (they don't seem to have one for Fedora 19). Yes, but the download is labeled for "Fedora 18 ("Spherical Cow") / 19 ("Schrödingers Cat")"

From the Menu > New > 'enter the name you want' > next line "Type" means

On 12/23/13 06:40, David wrote: > You guys are making this much, much more difficult than it is. Not really. The OP is using VBox from the Oracle site on F19 and is wanting to run F20 in a VM and he can't get it to install. Others, including myself, have had no problems. So.....trying to help find the reason.

On 12/22/2013 6:07 PM, Ed Greshko wrote: > On 12/23/13 06:40, David wrote: >> You guys are making this much, much more difficult than it is. > Not really. > > The OP is using VBox from the Oracle site on F19 and is wanting to run F20 in a VM and he can't get it to install. Others, including myself, have had no problems. So.....trying to help find the reason. > Hi Ed, I did not mean to be 'nasty' here. But? I often see people that *think* that they know a lot or people that actually *do* know a lot confuse Newbies, either to Linux in general or some program, with all kinds of (he ducks under the desk here) *Geek Speak!* Do this!!. Try this!! Try that!! All written in *Geek Speak!* to a Newbie. IMHO? Sometimes, many times, the *Geek Speak!* folks make things too hard. Think about it. Two possibilities. PEBCAC or his hardware. My guess would be the first. Newbie stuff. Whic is in now way bad. Everyone has to start somewhere. But First question? user experience? Second? What hardware? there are others. They depend on the answers to the first ones. Virtualbox is the most thoroughly documented program I have ever since ever. The "Help File" is a searchable PDF. If 'your system' can read a PDF and if 'you' can read and comprehend all will be revealed. But? Once again it is written in *Geek Speak!*. Honest. Read the 'help me' question. Is it a Newbie or 'knida Newbie' or 'I think I know what I am doing' question. And then> Don' everyon jump on him/er with tons of suggestions. Ya' think?

On 12/23/13 09:57, Ed Greshko wrote: > 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 Should read.... The last significant post from the OP would indicate he has it running under virt-manager and is NOW concentrating on trying to find a method to convert VBox VM's to run under virt-manager

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

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@meimei ~]$ rpm -qa | fgrep VirtualBox VirtualBox-4.3-4.3.6_91406_fedora18-1.x86_64 [egreshko@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

maybe, there is a bug in VBox running on your F19 system that fails to detect your hardware/OS is 64 bit?

I guess I'd be interested in the output of cat /proc/cpuinfo

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid bogomips : 6995.85 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: > > And maybe > > > > lshw -C processor | grep width > > lscpu | grep "CPU op-mode" [root@mongoliad mythtv]# lshw -C processor | grep width width: 64 bits [root@mongoliad mythtv]# lscpu | grep "CPU op-mode" CPU op-mode(s): 32-bit, 64-bit