Re: [Xen-devel] pv_ops dom0 and kernel console output problem

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Tue, Dec 30, 2008 at 03:07:03PM +0200, Pasi Kärkkäinen wrote:
> On Tue, Dec 30, 2008 at 10:02:18PM +1100, Jeremy Fitzhardinge wrote:
> > Todd Deshane wrote:
> > >Actually no. I just tested now. The screen goes blank during the dom0 
> > >kernel
> > >boot and then shows back up when I get a login: prompt.
> > >
> > >I have done most of my testing over a serial console and with the serial
> > >console it shows up.
> > >
> > >Jeremy: would you expect this to work? Were there recent patches that
> > >we could be missing?
> > >  
> > 
> > Nothing I can think of; it works for me.  I don't have my test machine 
> > on hand, so I'm not sure what the exact kernel command line is.  But 
> > perhaps booting without "console=hvc0" would work, and "earlyprintk=vga".
> > 
> 
> Thanks!
> 
> "earlyprintk=vga" solved the problem.. now I can see pv_ops dom0 kernel boot
> messages on the VGA console after Xen hypervisor messages.
> 

Or actually.. 

I can see the pv_ops dom0 kernel detect and print the (Xen) memory layout for
dom0, then some misc information and then the console is cleared and nothing
happens anymore.. I'm not sure if it gets to initrd yet at that point.. at
least I don't see any disk activity (based on the hdd LED).

My grub configuration atm:

title dom0-test (2.6.28-rc8-tip)
        root (hd0,0)
        kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all
        module /vmlinuz-2.6.28-rc8-tip.gz ro root=/dev/vg00/lv01 
earlyprintk=vga pci=nomsi
        module /initrd-2.6.28-rc8-tip.img

What is "earlyprintk=xen" supposed to do? 

-- Pasi

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel