Re: [Xen-users] Booting dom0 on OMAP5432 board

[Chen Baozi <baozich@xxxxxxxxx>]

On May 16, 2014, at 9:50, Chen Baozi <baozich@xxxxxxxxx> wrote:

> Hi John,
> 
> On May 15, 2014, at 23:33, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> 
>> On Thu, 2014-05-15 at 11:10 -0400, John Paul Walters wrote:
>>>> 
>>>> This is the point where you would normally start to see dom0 output.
>>>> 
>>>> Have you enabled the XEN HVC driver in your kernel and passed
>>>> console=hvc0 to the kernel?
>>>> 
>>>> If you have then you could trying pressing CTRL-A three times to enable
>>>> Xen debug keys, then try various keys to see if you can see if/where
>>>> dom0 has crashed ('h' lists them, 'q' is a good one, there is also one
>>>> to dump the dom0 state).
>>>> 
>>>> After that I think it would be a case of adding calls to xen_raw_printk
>>>> in the kernel and building a hypervisor with debuging enabled to get
>>>> some kernel output -- which will hopefully show where things go wrong.
>>>> 
>>>> Ian.
>>>> 
>>>> 
>>> Thanks for the suggestions.
>>> 
>>> It looks like the HVC driver is enabled, and I've included the output
>>> of both "q" and "0" below as well as my u-boot version and parameters.
>>> It might be helpful if someone could chime in with the versions (Xen
>>> and kernel) that have been shown to boot successfully.  I bring this
>>> up because the FTD patch didn't apply cleanly against any of the
>>> kernels that I tried, so I ended up manually applying the patch.
> 
> I’ve used the latest xen and linux git tree when writing the wiki.
> 
> Here is a hack to make dom0 write to the hvc console directly (can’t
> remember why I didn’t put it on wiki…).

IIRC, this patch is to just enable earlyprintk for dom0. Without this patch,
the normal printk should work also.

Baozi
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users