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

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

Alex --

So after recent changes in xen-unstable, can I enable
CONFIG_XEN_CONSOLE_INPUT, leave CONFIG_SERIAL_8250_ACPI
enabled in the xen0 and xenU config files and, possibly,
enable CONFIG_VT in xenU?  And, if so, do I need to specify
something different on Xen's boot line?

Or is this still work in progress?

Thanks,
Dan 

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Williamson, Alex (Linux Kernel Dev)
> Sent: Tuesday, December 13, 2005 2:51 PM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-ia64-devel] Console investigation.
> 
> 
>    A little progress update.  With the patch in this message:
> 
> http://lists.xensource.com/archives/html/xen-devel/2005-12/msg
> 00491.html
> 
> I can move xencons to use any reasonable ttyX or ttySX value.  On my
> xen0 domain, I can add "xencons=ttyS8 console=ttyS8" which 
> skips me over
> the range of ttyS devices claimed by the 8250 serial driver 
> (I'm leaving
> out CONFIG_SERIAL_8250_ACPI to prevent having both xen and 
> dom0 claim my
> serial console UART, leaving the PCI UARTs).  Furthermore, I can boot
> domU with the same trick, skipping over the 8250 claimed ports and
> avoiding the conflict with CONFIG_VT.
> 
>    I guess maybe it's time to hide the serial console UART from dom0.
> I'd really prefer some way that the hypervisor could do it
> automagically, but I guess I'll settle for a boot time option.
> 
>       Alex
> 
> -- 
> Alex Williamson                             HP Linux & Open Source Lab
> 
> 
> _______________________________________________
> 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