[SOLVED] Problems booting Mageia 3 in Virtualbox guest

[billr]

I did a search of the forums for related problems and found a few things to try, which I did, but I'm still stuck. I have Virtualbox 4.2.16 installed on a Windows 7 32-bit host. I previously had a Mageia 2 guest that was working fine, which I decided to upgrade to Mageia 3. I ran the upgrade from the DVD and afterwards the system would boot up part way then hang. It did boot into safe mode ok.

Taking a clue from another post, I booted into safe mode, brought up the networking and ran 'urpmi --auto-update' and let it update everything. After rebooting, it still hangs during boot up. I tried to capture a screenshot of the point where it is hanging using the Virtualbox take snapshot option, but all i captures is a blank screen. I've typed in the essence below. I did see the lm_sensors error message earlier and ran 'sensors-detect' from the safe mode command line and it said no sensors were found.

Does anyone have any ideas of things to try or do?

Startup messages:
:

Code: Select all

[OK] Started Display Manager
[FAILED] Failed to statr Initialize hardware monitoring sensors.
See 'systemctl status lm_sensors.service' for details
[OK] Started LSB: Checks for full partition
[OK] LSB: lock numlock key
[OK] LSB: update microcode
[OK] LSB: VitualBox Linux Additions kernel modules.
[OK] LSB: VitualBox Linux Additions kernel modules. (yes, it did print it twice)
        LSB: VitualBox Additions service...
[OK] Avahi
[OK] Login Service
[OK] Daemon for power management
[OK] UDisks Daemon
[OK] LSB: Network monitoring daemon
        Starting Authorization manager...
[OK] LSB: Nameserver information manager
[OK] Started LSB: VirtualBox Additions service
[OK] Sensor Information Logging
[OK] Started Authorization Manager
        Starting Bluetooth Manager...
[OK] Starting Network Manager
        Starting LSB: Bring up/down networkking...
        Starting Netowrk Manager Wait Online...

<end of displayed information>

[wintpe]

looks like its having issues with the network.

boot in safe mode

run ifconfig -a eth0

see if it has detected a network card.

regards peter

[billr]

Yes, it detects that a network card is present. 'ifconfig -a' shows both eth0 (and its MAC address) and lo. Previously, in safe mode, I was able to run the network startup scripts, get an IP address and reach the Internet.

I suspect it's something earlier in the startup sequence running in the background finally did something that caused it to hang, or maybe something after the networking startup that hung before it was able to print its startup message (less likely).

This shouldn't be that difficult. I've upgraded tons of systems in the past and not had a problem quite like this. Unfortunately, I didn't make a clone of the Mag2 VM before I did the upgrade, so if I can't get this working I'll have to do a new Mag2 install as I'm leaving on a business trip Monday and need some kind of Linux VM owrking.

[wintpe]

ok then from safe mode run init 2 and see if it makes it that far.

if it does not then it sounds like a similar post i replied to yesterday, in the mac equiv of virtualbox, parallels.

it seems mageia 3 is having issues in some cases with these.

try running each startup process one by one until you find the one that hangs.

read up on systemd or just use its backwards compatibility layer of chkconfig --list

followed by

service servicename start

for every one that has an on set for level 2

regards peter

[billr]

Thanks, Peter, I will do that this morning!

[billr]

Thanks to Peter's suggestions, I was able to find the problem and fix it. I booted into safe mode and ran 'init 2' and that worked fine. I then ran 'init 3' and it also worked fine and gave me a login prompt. I logged in, then ran 'startx' from the command line. The window increased in size then went blank and stayed blank. It was unresponsive to the keyboard.

I restarted in safe mode again and checked the Xorg.0.log file and found it tried to start aiglx and failed because dri2 was not supported. I edited the /etc/X11/xorg.conf file and added the line:
Option "AIGLX" "false"
in the ServerOptions section and started X again. This time X11 came up just fine.

Finally, I rebooted with the default configuration and it came all the way up to the graphical login screen. Everything seems to be just fine now.