Graphical server of Ubuntu 14.10 daily build does not start in Virtualbox

Bug #1380005 reported by Diego Germán Gonzalez
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Graphical server does no start in Ubuntu 14.10 daily build (9/10) instead of the installer screen appears multicolored pixels. The problem seems to be resolved by closing Virtualbox and waiting. The problem seems to be resolved by closing Virtualbox and waiting a few minutes to try again.
Virtualbox 4.3.16 installing from deb package

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: virtualbox (not installed)
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 11 02:21:58 2014
InstallationDate: Installed on 2014-09-23 (17 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: virtualbox
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Diego Germán Gonzalez (diegogermangonzalez) wrote :
Revision history for this message
Diego Germán Gonzalez (diegogermangonzalez) wrote :

the problem affects Ubuntu 14.10 Daily build of 9 october. not 10 september

Revision history for this message
Axel (naxel) wrote :

Still reproducible with VirtualBox 4.3.18.

For other people running into the same issue: adding the kernel bool param vga=791 helps start up the live image; the installed kernel does not need any extra boot param.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Diego Germán Gonzalez (diegogermangonzalez) wrote :

In Spain / Latin America
Press F2 to change the language
f3 to change keyboard settings
F6 / intro to select Expert Mode . ESC and add vga = 791 . Then press enter

Revision history for this message
Diego Germán Gonzalez (diegogermangonzalez) wrote :

Problem solved in Daily build October 22

Changed in virtualbox (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Ole Jon Bjørkum (olejonbj) wrote :

Having this problem on OS X when trying to boot Ubuntu 14.10 64-bit in VirtualBox. Downloaded today from releases.ubuntu.com.

Screenshot:
http://i.imgur.com/ChcXFsY.png

Revision history for this message
Ole Jon Bjørkum (olejonbj) wrote :

Ok, so managed to get it to boot into the installer after like 5-6 reboots. Seemed totally random. Installed and booted into LightDM at first try.

Revision history for this message
maxk (maxk-6) wrote :

VBox on 14.04 AMD64 host. Guest 14.10 AMD64. Having this problem.

Revision history for this message
pavel bursa (bursap) wrote :

Vbox 4.3.16 on Win 7 host. Guest 14.10 AMD64 have the issue. The F6 and vga=791 solution works for me.

Revision history for this message
Diego Germán Gonzalez (diegogermangonzalez) wrote :

Install latest virtuabox 4.3.18

Revision history for this message
xxvirusxx (condor20-05) wrote :

This bug still exist in ISO (x64) from 23 october. Tested on latest virtualbox.

Also vga=791 work fine.

Revision history for this message
ATIpro (somebody2112) wrote :

Same problem booting Lubuntu 14.10 AMD64 in Lubuntu 14.04 AMD64 (Virtualbox 4.3.10). It can be fixed with vga=791 kernel parameter.

Revision history for this message
Diego Germán Gonzalez (diegogermangonzalez) wrote :

Sorry.
The error seemed to have been solved, but after the other reports to the contrary redid the test and the problems persist

Changed in virtualbox (Ubuntu):
status: Fix Released → New
Revision history for this message
Diego Germán Gonzalez (diegogermangonzalez) wrote :

Please try this
After configuring the virtual machine go to Menú Settings. Select Screen
Select the maximum allowed memory
Enable 3D acceleration
Start the virtual machine

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.