Re: [Xen-devel] reg dom0 console

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Thu, 2011-10-06 at 01:05 +0100, Prasad B wrote:
> Hello All,
> 
> After a few months of hiatus, we have resumed working on mips port of
> Xen. We are at the point of booting dom0 userland (init process and
> its children). 

That sounds awesome! Are you close to having any initial patches for
submission?

> The init process gets spawned and in turn forks off processes to run
> commands in /etc/rc.d/init.d/rcS. However, the getty process does not
> seem to run subsequently and hence the login prompt is not displayed.
> Dom 0 does not use the uart and uses the hvc0 driver.
> 
> I searched the web for hints and there were suggestions to add
> directives such as 
> 
> 1:2345:respawn:/sbin/getty 38400 hvc0 
> 
> to /etc/inittab file. But that does not seem to help. 
> 
> Could you please give any pointers to get getty talk to the console
> driver correctly ?

Do you have something which is creating the actual /dev/hvc0 node? You
can probably boot with init=/bin/sh in order to get a shell to poke
around and check this with, run the getty by hand etc.

I had a vague recollection that the busybox inittab syntax was a little
different to standard sysvinit but google threw up various things which
suggest that what you've got is OK. Are you maybe in runlevel 1? You
could try changing the 2345->12345 to be sure. You probably want this
getty in single user mode anyway. Alternatively lots of example busybox
configurations I see on google seems to omit the runlevels, which I
guess means "all"?

Ian.

> 
> Screenshot of the tail
> -------------------------------
>   
> 0:<6>console [hvc0] enabled, bootconsole disabled
> 0:<6>console [hvc0] enabled, bootconsole disabled
> 0:Delay calibration in progress:
> 0:<6>Calibrating delay using timer specific routine..   0:<c>3211.14
> BogoMIPS (lpj=1605570)
> 0:<6>Security Framework initialized
> 0:Mount-cache hash table entries: 4096
> 0:Checking for the daddi bug...   0:no.
> 0:<6>NET: Registered protocol family 16
> Booting paravirtualized kernel on Xen  0:<6>Xen version: 3.4.0 (dom0)
> 
> ...
> 
> init started: BusyBox v1.14.0 (2009-05-01 15:38:41 PDT)
> Mounting all Filesystems...
> ... mounting done
> 
> <at this point cpu_idle() gets called and the processor waits
> indefinitely in a wait state>
> 
> thank you,
> Prasad.



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