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-users

Re: [Xen-users] SuSE 9.3 serial bus problem

To: Robert Welz <r_welz@xxxxxx>
Subject: Re: [Xen-users] SuSE 9.3 serial bus problem
From: Robbie Dinn <robbie@xxxxxxxxxxxx>
Date: Fri, 07 Oct 2005 18:18:45 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 07 Oct 2005 17:16:20 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5C985D5A-40D5-40B5-B55A-09A75B7AEA64@xxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <9A3A8B25-1D5E-4B69-A065-3CF0FEC39660@xxxxxx> <5C985D5A-40D5-40B5-B55A-09A75B7AEA64@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20041207)
Robert Welz wrote:
Hello!
I am sucessfully running 2 domains but I cannot use the serial bus for my Belkin Universal UPS.

I have not tried this, but there is some info in the user documentation
(rpm xen-doc-{pdf,html,ps}, /usr/share/doc/packages/xen).

see section 2.4.2 Serial Console (optional)

In boot.msg I see:
8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled

I think this might be slightly misleading. I believe this
message is being printed by a driver in xen, and not by the
domO kernel at all.

but later on I see dozends of:
modprobe: FATAL: Error inserting 8250 (/lib/modules/2.6.11.4-21.9-xen/ kernel/drivers/serial/8250.ko): Device or resource busy

Xen has already grabbed the serial hardware (uart) so when the dom0
kernel tries by loading the 8250.ko module, it can't see the hardware.
Xen has hidden it from view I believe. You can't have both Xen and Dom0
trying simultaneously to use the bare harware or chaos follows.

Now, quoting from the docs...
One can also configure XenLinux to share the serial console;
to achieve this append ``console=ttyS0'' to your module line.

Robert Welz wrote:
My /boot/grub/menu.lst looks like:
###Don't change this comment - YaST2 identifier: Original name: xen###
title XEN
    kernel (hd0,11)/xen.gz dom0_mem=261000 xencons=off sched=bvt
module (hd0,11)/vmlinuz-xen root=/dev/Leia/root vga=0x317 selinux=0 splash=silent resume=/dev/md0 showopts
    module (hd0,11)/initrd-xen


Maybe if you change you module line to read
  module (hd0,11)/vmlinuz-xen .... console=ttyS0

..that will do it (I have not test this).

I think that option to the DomO kernel means "don't try to touch
the serial harware yourself, hand the serial data to xen, and xen
will use it's serial driver".

I would be glad to know if that works or not.

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

<Prev in Thread] Current Thread [Next in Thread>