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

Re: [Xen-devel] dom0 won't boot

> On Thursday 29 July 2004 08:29 pm, Ian Pratt wrote:
> > All of that output is from grub, you're not seeing anything from
> > Xen.
> >
> > Try "com1=115200,8n1" and make sure that you've got the baudrate
> > at the other end set correctly (I thought grub defaulted to 9600?)
> It's set correctly -- I had never done this before, so there was a bit of a 
> learning curve.  I practiced on the smp kernel that I usually boot into and 
> when I was able to capture everything in minicom there I switched over to 
> xen.  If I had gotten no output at all, it would have been suspicious.  
> However, I did get output, no characters were garbled, no sentences cut in 
> half, etc.
> For whatever it's worth, here's the entry in grub:
> title Xen-Serial
> serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1
> terminal serial
> kernel (hd0,4)/boot/xen.gz dom0_mem=131072 com1=115200 noht noreboot
> module (hd0,4)/boot/vmlinuz-2.4.26-xen0 root=/dev/sda5 ro console=ttyS0

You're setting the serial baud rate to 9600 in grub, then 115200
in Xen? That doesn't sound sane. The baudrate mismatch is so
gross that you probably wouldn't even see garbage.

Try com1=9600,8n1   (I can't remember whether the ',8n1' is
mandatory but let's assume it is...)


This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
Xen-devel mailing list



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