WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] error on booting XenLinux

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] error on booting XenLinux
From: Brian Wolfe <brianw@xxxxxxxxxxxx>
Date: Fri, 20 Aug 2004 18:46:57 -0500
Cc: Mike Waychison <Michael.Waychison@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 21 Aug 2004 00:49:17 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1ByHeB-0003td-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: TerraBox.com Inc.
References: <E1ByHeB-0003td-00@xxxxxxxxxxxxxxxxx>
Reply-to: brianw@xxxxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Interesting. So if I use the serial port driver as a module, then I
*should* be able to get to com2 while com1 is in use by xen as a serial
console?

On Fri, 2004-08-20 at 17:14, Ian Pratt wrote:
> > > Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
> > > Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
> > 
> > You currently have to keep the 8250 driver disabled.  Unfortunate, as it
> > means you can't get to real serial ports afaict, and it means that
> > drivers like mwave just won't work.
> 
> You've pointed out Brian's problem, but the situation isn't as
> bad as you think.
> 
> If you want to have the domain access the serial port directly
> rather than going via Xen then:
>  1) *don't* have a com1= entry on the Xen command line
>  2) Have "xencons=off" on the linux command line
> 
> You can then configure the serial port however you like (though I
> haven't tested it under 2.6).
> 
> For most users, I think it makes more sense to have Xen own the
> serial port and for dom0 to send its output via the xencons
> driver registered on ttyS0. That way you get the ouput from both
> dom0 and Xen.
> 
> Best,
> Ian
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel