Bug 8667

Summary:	3.8 kernel has issues displaying virtual console in VMWare
Product:	Mageia	Reporter:	David Walser <luigiwalser>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	kernel-3.8.0-0.rc3.1.mga3.src.rpm	CVE:
Status comment:

Description David Walser 2013-01-11 20:12:58 CET

Upgraded a Mageia 2 VM to Cauldron with the net installer.  Booting the upgraded system hangs with:

Starting udev Wait for Complete Device Initialization...

I went to rescue mode and did chroot /mnt systemctl disable systemd-udev-settle.service, but it still does the same thing.  (BTW, it'd be nice if that was aliased to its old name, udev-settle.service.  The systemd- in front is cumbersome and superfluous).

Comment 1 David Walser 2013-01-16 00:58:19 CET

This is a much stranger issue than it initially seemed.

I have two VMWare VMs I use for testing upgrades, one with a desktop install and one more of a server install.

On the desktop one, I did the upgrade and was able to reproduce this.  Then I booted the mga2 kernel, which worked fine.  I installed kernel-desktop-latest, and rebooted to the 3.8 desktop kernel, and it worked fine.  Then I rebooted to the 3.8 server kernel (the one I got initially from the upgrade) and all of a sudden it now worked fine too!

So I tried the same on the server VM.  The mga2 kernel did in fact work, but the 3.8 kernels would not.  Playing around with the boot options, I discovered that it would boot fine if I removed the vga=791 (1024x768 16bpp) from the kernel in grub.  This is strange though, because I'm also using vga=791 on the desktop VM.

Finally I tried my normal boot options with the 3.8 kernel one more time (on the server VM) and it still *appears* to hang somewhere around udev-settle and fedora-loadmodules, but if I wait a minute, I can ping it and ssh into it!  I can also pretend I have a virtual console login in the VM itself and type in a username and password, and through my ssh session, I can see that I'm logged in there!

So, what's really happening is at some point during boot, when using a different resolution virtual console, it just stops updating the display.  I don't understand why I was able to shake it out of this on one VM and not another.

CC: (none) => mageia
Assignee: mageia => tmb
Summary: systemd-udev-settle does not allow upgraded Mageia VM to boot => 3.8 kernel has issues displaying virtual console in VMWare
Source RPM: systemd-195-6.mga3.src.rpm => kernel-3.8.0-0.rc3.1.mga3.src.rpm

Comment 2 David Walser 2013-04-15 23:45:40 CEST

As I told Thomas on IRC, I'm having a similar issue in Virtualbox now, but with current (as of Friday) Cauldron, I don't have these issues in VMWare.

Status: NEW => RESOLVED
Resolution: (none) => FIXED