I tried to install 2 virtual machines on 2 different x4200-M2 machines. The weird thing is both virtual machines could boot up correctly this time. It looks like the XWindow could not start up occasionally on xVM as I hit last time.
jan damborsky wrote: >> 1. Is this "console=graphic" used by "virtual console" module? Obviously it >> hinder the machine from booting. Or maybe this keywords redirect console to >> a kind >> of GUI mode which console or kmdb could not show? >> > So there are 2 issues here: > In general "Happy face boot" itself shouldn't hinder machine from > booting unless the boot process goes into interactive mode or some > other type of hang occurs (As you are describing below). > To be honest, the underlying implementation is not known to me, > I will let Jan Setje-Eilers comment on this. > I am still not sure what the "console=graphic" means. When I remove the "splashimage, foreground and background" and leave "console=graphic" intactly, then boot the kernel/OS， the monitor still shows nothing at all, but finally, X could start up correctly. What does mean for the "console=graphic" item? Thanks! > >> 2. Another issue here is the XWindows depends on multi-user and the >> multi-user >> normally depends on network/service. I think if there is no DHCP or the >> network/ >> service would not start up correctly, the X/gdm service will never start up. >> In the >> mean time, the booting process is hidden behind the "splashimage" of GRUB. >> The result is users never could access to console and they might confuse why >> the >> OS could not boot up as I hit in xVM machine this time. So it might be good >> not show >> splashimage on GRUB when trying to boot. >> As following: >> ################################ >> svc:/network/service:default (layered network services) >> State: offline since Wed Nov 05 09:38:33 2008 >> Reason: Start method is running. <---- The service is running here, >> not never done in a very long time(a few hours on my xVM now) >> See: http://sun.com/msg/SMF-8000-C4 >> See: man -M /usr/share/man -s 1M ifconfig >> See: /var/svc/log/network-service: default.log >> Impact: 7 dependent services are not running: >> svc:/network/smtp:sendmail >> svc:/milestone/multi-user:default >> ...... >> svc:/application/graphical-login/gdm:default: >> ...... >> >> ################################ >> After I manual set IP Address, the X/gdm service start correctly >> and the whole OS could work as expected, too. >> > > On my test machine disconnected from network I have tried > to do first boot after the installation - DHCP timeout > was applied correctly and Desktop came up. > > That said, the problem you are seeing might be specific > to your particular environment, which is xVM in your case. > If the issues is reproducible, could you please file > bug for this in opensolaris/networking category ? > > Could that possible that after the network service timeout, then the gdm start fail or time out, already? It looks like last time I might meet with the issue. That is, after DHCP timeout, the gdm also could not start up correctly. Anyway, I could not reproduce the issue in these 2 tests today, I would like to file a bug next time when I hit it. thanks Jason > >> Thanks >> Jason >> >> >> >>> Hi Jason, >>> >>> could you please try without "happy face" (that progress bar) >>> in order to see, why/where the machine is hanging ? >>> >>> When in GRUB, press 'e' and using 'd' remove following lines from >>> GRUB menu: >>> >>> splashimage /boot/solaris.xpm >>> foreground d25f00 >>> background 115d93 >>> >>> Also remove ",console=graphics" from kernel$ line. >>> >>> Optionally, you might add "-kvd" to the kernel$ line >>> in order to enable kmdb and obtain more information - >>> if it turns out, it is not quite obvious, why machine >>> hung. >>> >>> Then press 'b' in order to boot - progress bar shouldn't be there >>> and you could observe what's going on. >>> >>> Also, could you please attach "install_log" file ? >>> >>> Thank you, >>> Jan >>> >>> >>> >>> Jason Zhao wrote: >>> >>>> Forgot to mention, the build is based on snv_100a. >>>> >>>> And I installed the virtual machine on X4200 M2 with 2G RAM >>>> and 34G disk which is a large file. >>>> >>>> Thanks >>>> Jason >>>> Jason Zhao wrote: >>>> >>>>> Hi, All >>>>> >>>>> >>>>> I pulled over the 1031 nightly image from indiana-build.central. >>>>> And I tried to install it on xVM virtual machine through HVM mode. >>>>> The installation process is quite well, but after installation, >>>>> >>> when>> the GUI or X try to start, it shows a slider which is never >>> end, and it >>> >>>>> is to say, the GUI desktop could never start. As the screen picture >>>>> in attachment. So far, it is about 14 hours after installation, the >>>>> desktop still could not start. >>>>> >>>>> I am not sure what it try to do when GUI or X start, and I guess >>>>> >>> it is >>> >>>>> trying to get DHCP address. But in our test environment, the >>>>> >>> machine>> could not be dispatched an IP address automatically by >>> DHCP server. >>> >>>>> On real machine, the slider process after installation is also >>>>> >>> quite>> long in our test environment. It is about 15 minutes in all >>> on Lenovo >>> >>>>> T61 laptop. >>>>> >>>>> Any suggestion, please? >>>>> >>>>> Great Thanks >>>>> Jason >>>>> >>>>> >>>>> _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
