fedora 20

[chaplspike]

i recently installed fedora 20 on virtualbox 4.2.18. after updating i installed the guest additions. now when it boots all i get is a black screen. does anyone know how to fix this?

[noteirak]

Minimum information needed for assistance

[pfinnigan]

I have just tested out a Fedora 20 alpha guest on VirtualBox, as preperation for the Beta. I too encountered the same problems.

I was using virtualBox 4.3.0 r89960 on Fedora 19 x64, installed from the yum repositories. I had attempted to instal the Guest Additions using Host+D. I used the Fedora 20 Alpha Live CD and installed to hard disk on my VirtualBox system. This all went without problems. I updated just the kernel and installed the headers and gcc, requirements for the Guest Additions. I then performed the Host+D and rebooted to a blank screen.

It looks like it is not a VirtualBox problem. After the failure I booted into runlevel 3 and removed the additions. I thern performed "yum update -y" and reinstalled the guest additions and everything worked fine.

This means the source of our problem is in original Alpha release of Fedora 20, not unexpected. However, as always the Fedora team have come up tumps and fixed the problem.

[ssantosh1978]

I have tested out a Fedora 20 final release guest on VirtualBox no issues observed. Installation was straight forward no black screen..

http://www.vmwareandme.com/2013/12/inst ... ox-43.html

[evansri]

I've just installed Fedora 20 on VirtualBox 4.3.6. All is OK except with I change the virtual machine to use 2 monitors. Then it boots to a black screen with no login dialogue.

Can others try to see if this is repeatable? I have the latest guest additions inatalled and the latest Fedora updates.

One additional fact - if I turn off 3D acceleration in the virtual machine settings, then it is OK - after boot I get the login screen.

Richard

[JungleJim]

I tried to instal Fedora 20 under the latest edition of Virtual Box. I got a black screen when I selected the install option.

Eventually I figured out that I had set the type of the virtual machine to Fedora whereas I was using a 64 bit image. I changed the type to Fedora 64 bit, in the settings of Virtual Box for this image, and it worked.

[skinflint]

JungleJim, Which version of VBox are you running? The current version of VirtualBox (4.3.6) does not offer an option for "Fedora 64", just "Fedora". I ran into the black screen during installation of Fedora 20 on VBox 4.3.6 on Windows 7. I also have 3D acceleration turned off. I will post log files shortly.

[socratis]

The current version of VirtualBox (4.3.6) does not offer an option for "Fedora 64", just "Fedora"

Yes it does. Your host doesn't offer it because VT-x is disabled or in use:

1. 64-bit guests need hardware-virtualzation enabled in the hosts BIOS.
2. If running Windows as host you must make sure Hyper-V or XP-mode is not enabled on the host.

[evansri]

My problem with blank screen with 2 virtual monitors seems to be a manifestation of bug 9124 - https://www.virtualbox.org/ticket/9124. Raised two years ago and still not fixed.

[skinflint]

JungleJim and Socrats. Thanks and My bad. Fedora 64 bit is listed. When I originally attempted the install it failed because, as you rightly point out, I needed to enable virtualization in the BIOS. After enabling virtualization in the BIOS, the 64 bit option appeared in the list. I only needed to scroll down one click to see it.

After setting the VM to Fedora 64 bit, I plugged in the Fedora 20 Live DVD, restarted the VM and the installation process restarted up on it's own. It didn't ask for the ISO path, didn't display the Welcome graphic asking if I want to Try Fedora to Install to Hard Disk. It was hard to tell if Fedora was trying to install or startup. After displaying a progress bar for a minute or two, the screen went black again. The log file shows a disk read error on the source media DVD.

I burned a new DVD and retried the install. TSC Fast "calibration failed. Bug Software lockup. cpu unresponsive for more than 20 seconds. From that point the install process ran smoothly, albeit slowly, up until the last step, Set Root Password. At this point the process slowed to a crawl and eventually stalled completely. The system seemed to be thrashing itself to death as it evaluated the strength of the password character by character. Again the log showed disk read errors on the DVD. So after about 30 minutes of trying to enter a password I ended up restarting the VM.

I tried one last time burning a new DVD. When inserting the new blank DVD, Windows 7 pops up a screen that says "Would you like to use this new disk as a USB, or as a CD?" In previous attempts I think I skipped this step, assuming that the Live CD creator would format as needed. After selecting "Use as a USB / rewritable disk" the disk was then formatted for use. Of course Live CD creator still asked if I wanted to erase everything on the disk, but no big deal. I inserted the newly created DVD, started the VBox VM and the install ran like a dream.

[Cubytus32]

Fedora 20 just installed on VirtualBox 4.3.6. Can't get past a command line screen saying:

Code: Select all

Starting Dracut Emergency Shell...
Warning: /dev/fedora/root does not exist
Warning: /dev/fedora/root does not exist
Warning: /dev/mapper/fedora-root does not exist
Warning: /dev/mapper/fedora-root does not exist
Warning: /dev/mapper/fedora-root does not exist

Generating "/run/initramfs/rdsoreport.txt"

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsoreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.

dracut:/#

[Nexxuz]

I've just installed Fedora 20 on VirtualBox 4.3.6. All is OK except with I change the virtual machine to use 2 monitors. Then it boots to a black screen with no login dialogue.

Can others try to see if this is repeatable? I have the latest guest additions inatalled and the latest Fedora updates.

One additional fact - if I turn off 3D acceleration in the virtual machine settings, then it is OK - after boot I get the login screen.

Richard

The problem occurs for me when I had another VM running that was already 3D enabled. I turned off 3D on this one and it started to work. I do not think that you can have 2 VMs running at the same time both 3D enabled. (Have not tested thoroughly)

[socratis]

I do not think that you can have 2 VMs running at the same time both 3D enabled. (Have not tested thoroughly)

I have tried it with at least 3 guests and it works flawlessly. All of them were running 3D benchmarks. Yes, I was goofing, trying to push the system(s) to its limits. Only my host CPU was affected...

[jagg2014]

I installed Fedora20 on a vm created on virtualbox4 .3 on windows 7, everything works however my root has 4GB space with the mount being /dev/mapper/live-rw, i had given a total of 40GB to the VM, I was wondering how i can allot more than 4GB at the time of install or resize after the install to the root. The reason i am trying to have more space is i am trying to install openstack on fedora and the install hangs due to no space on root

[loukingjr]

I installed Fedora20 on a vm created on virtualbox4 .3 on windows 7, everything works however my root has 4GB space with the mount being /dev/mapper/live-rw, i had given a total of 40GB to the VM, I was wondering how i can allot more than 4GB at the time of install or resize after the install to the root. The reason i am trying to have more space is i am trying to install openstack on fedora and the install hangs due to no space on root

as far as when you are installing, I would think the Fedora installer has a custom install option where you can set what partitions you want and their sizes etc. Once it's already installed, you would need something like the GParted.iso, mount it to the CD controller for your guest in the VirtualBox settings and start it. You can use it to resize partitions but I would make a back up of your Fedora guest first.