[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
  • Date: Fri, 9 Jan 2009 19:34:45 +0200
  • Delivery-date: Fri, 09 Jan 2009 09:35:12 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Tue, Dec 30, 2008 at 04:18:13PM +0200, Pasi Kärkkäinen wrote:
> On Tue, Dec 30, 2008 at 03:20:36PM +0200, Pasi Kärkkäinen wrote:
> > 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? 
> > 
> 
> I still haven't gotten VGA console to work, but now _serial_ console seems to 
> work
> using this configuration:
> 
> title dom0-test (2.6.28-rc8-tip) / serial console
>       root (hd0,0)
>       kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all 
> com1=19200,8n1 console=com1
>       module /vmlinuz-2.6.28-rc8-tip.gz ro root=/dev/vg00/lv01 console=hvc0 
> earlyprintk=xen xencons=ttyS0,19200 pci=nomsi
>       module /initrd-2.6.28-rc8-tip.img
> 

Actually xencons= doesn't seem to be needed for the Linux kernel.

So here's more simple working grub configuration for using serial console
with Xen and pv_ops dom0 kernel:


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


That works for me. 

-- Pasi

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.