Description of problem:
Doing upgrade from fedora 26 workstation to fedora 27 on virtualbox
After the upgrade i got a black screen after the os start. Console are accessible and useable.
I have the same issue if i launch a workstation fedora 27 live image on virtualbox. The work around is to start the live image with basic graphic mode, do the installation and after the reboot the install work find without black screen.
Same issue from fedora 25 workstation to fedora 27
I can reproduce this issue with today's Fedora-27-20171015.n.0 Workstation Live compose
Ubuntu disabled the new upstreamed VirtualBox drivers in the Linux 4.13 kernel for Ubuntu 17.10 because of a similar issue.
Proposed as a Blocker for 27-final by Fedora user jbicha using the blocker tracking app because:
This is a regression from Fedora 26 and VirtualBox is a popular way to use Fedora desktop.
Contingency mechanism: The proposal owner will remove the VirtualBox Guest Additions package from the default package list for the Workstation product if it is not working properly
Contingency deadline: Beta Freeze
This is fixed by this Fedora kernel commit:
We are just waiting for the kernel team to kick of a new build, once that is done this is resolved.
I can confirm the fix in Ubuntu (cherry-picked from your patch)
Should be fixed in the 4.13.7-300 kernel
kernel-4.13.8-300.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-aa9927961f
Discussed during the 2017-10-23 blocker review meeting: 
The decision to classify this bug as a RejectedBlocker and an AcceptedFreezeException was made as vbox isn't one of the officially-blocking virt technologies and a workaround is available. This is widely used however, and so warrants a FreezeException.
kernel-4.13.8-300.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
Pushed to stable, closing.
Today's workstation live Fedora-27-20171026.n.0 compose works great. Thanks!
*** Bug 1506056 has been marked as a duplicate of this bug. ***
so no longer needs CommonBugs.