<div class="gmail_quote">On Wed, Jul 8, 2009 at 3:29 PM, Pasi Kärkkäinen <span dir="ltr"><<a href="mailto:pasik@iki.fi" target="_blank">pasik@iki.fi</a>></span> wrote:<br> <blockquote class="gmail_quote" style="padding-left:1ex;margin:0px 0px 0px 0.8ex;border-left:#ccc 1px solid"> <div>On Wed, Jul 08, 2009 at 02:05:35PM -0400, Lester M. wrote:<br>><br>> Hello Pasi,<br>><br>> Unfortunately with adding "loglvl=all guest_loglvl=all noreboot" and<br>> removing "rhgb quiet" from the vmlinuz the result stayed the same.<br> ><br>> After the boot process gets to the "(XEN) Scrubbing Free RAM:<br>> ..........done." the screen still goes blank, and the system ceases to<br>> respond. This forces me to do a "hard reset" on my laptop. :-(<br> ><br><br></div>Hmm.. The boot process should look something like this:<br> <div><br>..<br>(XEN) Scrubbing Free RAM: ..........done.<br></div>(XEN) Xen trace buffers: disabled<br>(XEN) Std. Loglevel: All<br>(XEN) Guest Loglevel: All<br>(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)<br> (XEN) Freed 104kB init memory.<br>mapping kernel into physical memory<br>Xen: setup ISA identity maps<br>about to get started...<br>Reserving virtual address space above 0xf5800000<br>PAT disabled on Xen<br>Initializing cgroup subsys cpuset<br> Initializing cgroup subsys cpu<br>Linux version 2.6.30-rc6-tip (root@dom0test.localdomain) (gcc version 4.4.0<br>20090506 (Red Hat 4.4.0-4) (GCC) ) #15 SMP T<br>ue Jun 9 19:36:50 EEST 2009<br>KERNEL supported cpus:<br> Intel GenuineIntel<br> AMD AuthenticAMD<br> NSC Geode by NSC<br> Cyrix CyrixInstead<br> Centaur CentaurHauls<br> Transmeta GenuineTMx86<br> Transmeta TransmetaCPU<br> UMC UMC UMC UMC<br>BIOS-provided physical RAM map:<br> Xen: 0000000000000000 - 000000000009f400 (usable)<br> Xen: 000000000009f400 - 0000000000100000 (reserved)<br> Xen: 0000000000100000 - 0000000040000000 (usable)<br> Xen: 000000007f6e0000 - 000000007f6e3000 (ACPI NVS)<br> Xen: 000000007f6e3000 - 000000007f6f0000 (ACPI data)<br> Xen: 000000007f6f0000 - 000000007f700000 (reserved)<br> Xen: 00000000e0000000 - 00000000f0000000 (reserved)<br> Xen: 00000000fec00000 - 0000000100000000 (reserved)<br>console [xenboot0] enabled<br><br>etc<br><br>So the dom0 kernel should get booted up pretty shortly after that Scrubbing Free RAM..<br> <div><br><br>> This is my grub entry with the "loglvl=all guest_loglvl=all noreboot" added:<br>><br>> title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE)<br>> root (hd0,0)<br> > kernel /xen-3.4.1-rc6.gz dom0_mem=1024M loglvl=all guest_loglvl=all<br>> com1=19200,8n1 console=com1<br>> module /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro<br>> root=/dev/mapper/vg01-lv_root<br> > module /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img<br>><br><br></div>You shouldn't have the "com1=19200,8n1 console=com1" there if you want to use<br>the VGA text console..<br> <div><br>><br>><br>> When I set up a serial console and boot the system, the screen immediately<br>> goes "blank" and the system ceases to function as well. The difference is<br>> that this occurs sooner using the serial console than after the "(XEN)<br> > Scrubbing Free RAM: ..........done." occurrence.<br>><br><br></div>When you have a serial console in use, the screen _should_ go blank immediately,<br>because the console output is redirected to the serial port/console.<br> <br>So the behaviour you're seeing there is expected.<br> <div><br>> This is my grub entry with the serial console setup from the xenpvops page:<br>><br>> title Fedora (2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE)<br>> root (hd0,0)<br>> kernel /xen-3.4.1-rc6.gz dom0_mem=1024M loglvl=all guest_loglvl=all<br> > com1=19200,8n1 console=com1<br>> module /vmlinuz-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE ro<br>> root=/dev/mapper/vg01-lv_root console=hvc0 earlyprintk=xen<br>> module /initrd-2.6.31-0.1.2.37.rc1.git5.xendom0.fc12.i686.PAE.img<br> ><br><br></div>That looks correct, if your laptop serial port actually is com1.<br>Do you see the Xen and dom0 kernel boot messages on the serial console?<br> <div><br>><br>> So all of this works on your system and not mine. Unfortunately this is all<br>> the hardware I am able to test on at this time. I don't know how many people<br>> are running this xen configuration on a Lenovo T60 laptop but there is<br> > clearly something missing.<br>><br>> What more should I test to get this working? :-) Anything goes at this<br>> point, but I do hope the developers / maintainers are reading this thread.<br>> :-P<br><br> </div>Do you have to specify any non-default parameters to xen or dom0 kernel when<br>you use RHEL 5.3 on the laptop?<br><font color="#888888"><br>-- Pasi<br></font></blockquote></div> <div> </div> <div>Pasi, and M A Young;</div> <div> </div> <div>Thank you so much for the information thus far, I really appreciate the feedback in resolving this. :-)</div> <div> </div> <div>What Kernel options should I use to get a vga console? (to just have *everything* dump on my screen?) I do not have a "real" serial console on my consumer laptop.</div> <div> </div> <div>On RHEL 5.3 I have no extra options than the defaults (which includes the "rhgb quiet" on the vmlinuz line), it just boots! I took a look at that earlier. </div> <div> </div> <div>I will try out your 32bit .config, did you get your kernel checkout from: (git clone git://<a href="http://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git" target="_blank">git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git</a> linux-2.6-xen) ?</div> <div> </div> <div>Also, did you use the latest branch? (from: <span style="word-spacing:0px;font:16px 'Times New Roman';text-transform:none;color:rgb(0,0,0);text-indent:0px;white-space:normal;letter-spacing:normal;border-collapse:separate"><span style="font-size:13px;color:rgb(51,51,51);font-family:'Courier New';text-align:left">git checkout origin/xen-tip/next -b xen-tip/next</span></span>) ?</div> <div> </div> <div> </div>