Ubuntu
ubiquity package

Oneiric: Install GUI never starts when run under Hyper-V VM

Asked by Mike Sterling

If I take the ubuntu-11.10-desktop-i386 or the xubuntu-11.10-desktop-i386 ISO file and attach it to a Hyper-V VM (to do the install in a Hyper-V virtual machine), the GUI portion of the installer never starts. I see many of the services start, but I never get to the GUI portion of the installer.

Screen display on ubuntu-11.10-desktop installer when it hangs: http://dasko.pgcenarius.com/images/hv_install_failure.png
Screen display on subuntu-11.10-desktop installer when it hangs: http://dasko.pgcenarius.com/images/hv_install_failure_2.png

I've also confirmed that the MD5SUM of the downloaded ISO's are good.

If I use the ubuntu-11.10-alternate-i386 ISO file, I'm able to install fine in text mode, and then after the install completes, I boot up fine into runlevel 5.

How can I troubleshoot what the installer is doing or why it's hanging?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu ubiquity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
delance (olivier-delance) said : 		#1

Hyper-V is known to have issues with Ubuntu. VmWare and VirtualBox work perfectly. Do you really need to use Hyper-V ?

Revision history for this message
Mike Sterling (mike-sterling) said : 		#2

Well, I work for Microsoft, and my team is responsible for the device drivers that are present in the kernel - so I do have a vested interest in it. :)

We've fixed one bad issue with 10.10, and 11.04 works perfectly. 11.10 works fine if you install using the alternative ISO, but I want to figure out what the issue is with 11.10 and the normal installer.

Revision history for this message
Colin Watson (cjwatson) said : 		#3

It isn't clear whether the installer is even being started properly, although from your Ubuntu screenshot clearly Upstart did try. You might try:

 * The '--verbose' option on the kernel command line, which will cause Upstart to spew lots more information to the system log
 * The 'debug-ubiquity' option on the kernel command line, which will cause the installer to dump debugging information under /var/log/installer/
 * Checking /var/log/installer/dm and /var/log/Xorg.0.log to see if there are any errors there

Can you use Alt-F2 or similar to get a shell so that you can do non-trivial investigation?

(This may not be the right forum for this discussion, as this is really for end-user support, but we can run with it for now ...)

Revision history for this message
Colin Watson (cjwatson) said : 		#4

Incidentally, I wouldn't normally bother saying this since you clearly meant that it gets up to a graphical desktop, but if you're debugging this kind of thing, it may be worth adjusting a misconception - Ubuntu boots into runlevel 2 by default (although runlevels are becoming decreasingly relevant with event-based init, but nevertheless 2 is the default where it still matters). Runlevel 5 is the graphical runlevel only in Red Hat-derived systems.

Revision history for this message
Mike Sterling (mike-sterling) said : 		#5

Colin, if it makes sense to move it somewhere else, I'd be happy to do so.

I booted with debug-ubiquity, and checked both /var/log/installer/dm as well as the Xorg.0.log - it appears that it wasn't able to open a screen on the framebuffer:

/var/log/installer/dm:

X.Org X Server 1.10.4
Release Date: 2011-08-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-29-server i686 Ubuntu
Current Operating System: Linux ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC 2011 i686
Kernel command line: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- debug-ubiquity
Build Date: 29 September 2011 12:48:48AM
xorg-server 2:1.10.4-1ubuntu4 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.22.2
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 9 19:12:33 2011
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
vesa: Ignoring device with a bound kernel driver
(EE) open /dev/fb0: No such file or directory
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

/var/log/Xorg.0.log:

[ 24.278] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 24.278] vesa: Ignoring device with a bound kernel driver
[ 24.278] (WW) Falling back to old probe method for vesa
[ 24.278] (II) Loading sub module "fbdevhw"
[ 24.278] (II) LoadModule: "fbdevhw"
[ 24.278] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 24.278] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 24.278] compiled for 1.10.4, module version = 0.0.2
[ 24.278] ABI class: X.Org Video Driver, version 10.0
[ 24.278] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 24.278] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 24.278] (EE) open /dev/fb0: No such file or directory
[ 24.278] (WW) Falling back to old probe method for fbdev
[ 24.278] (II) UnloadModule: "vesa"
[ 24.278] (II) Unloading vesa
[ 24.278] (II) UnloadModule: "fbdev"
[ 24.278] (II) Unloading fbdev
[ 24.278] (II) UnloadModule: "fbdevhw"
[ 24.278] (II) Unloading fbdevhw
[ 24.278] (EE) Screen(s) found, but none have a usable configuration.
[ 24.278]
Fatal server error:
[ 24.278] no screens found
[ 24.278]
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[ 24.278] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 24.278]
[ 24.289] ddxSigGiveUp: Closing log

Revision history for this message
Launchpad Janitor (janitor) said : 		#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.