RE: [Xen-ia64-devel] Console investigation.

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

> So, why do we wan to set CONFIG_VT in dom0 or domU ?

One goal is to allow a single binary to run both on
bare metal and on top of Xen.  If a CONFIG option that
is normally used by a standard Linux config file doesn't
work for Xen, then one can't run that binary in both
places.

Thanks,
Dan 

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Tristan Gingold
> Sent: Friday, December 09, 2005 7:59 AM
> To: Williamson, Alex (Linux Kernel Dev)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-ia64-devel] Console investigation.
> 
> Hi,
> 
> here are my first results.
> Kernel is compiled with CONFIG_VT and without CONFIG_SERIAL_8250.
> 
> On the first boot, I got error messages such as:
> Warning: dev (ttyS-1) tty->count(7) != #fd's(1) in tty_open
> 
> The reason is that kcons_info.index is -1 (which is wrong), 
> because kcons is 
> not the first console and its index field is set to -1.
> Indeed, the first console is hpsim_cons, which has no tty.
> 
> Maybe kcons should be enabled early and hpsim_cons completly disabled.
> 
> After disabling hpsim_cons, /dev/ttyS0 now works, but 
> /dev/console prints to 
> nowhere.  The reason is that /dev/console is vt, which does not work.
> 
> My fix is to add console=ttyS0 on the command line.
> 
> Now, domU console does not work, because /dev/console is vt.  
> My fix is to 
> undef CONFIG_VT, which also fix the previous problem.
> 
> So, why do we wan to set CONFIG_VT in dom0 or domU ?
> 
> Tristan.
> 
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

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