From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ferenc Wagner <wferi@niif.hu>
Cc: xen-devel@lists.xensource.com
Subject: Re: dom0 serial input overruns
Date: Sun, 20 Mar 2011 16:43:21 -0400 [thread overview]
Message-ID: <20110320204321.GE3948@dumpdata.com> (raw)
In-Reply-To: <87zkoq6onj.fsf@tac.ki.iif.hu>
On Sun, Mar 20, 2011 at 12:02:08PM +0100, Ferenc Wagner wrote:
> (no dice on xen-users, let's try xen-devel...)
>
> Hi,
>
> I'm running a HA Xen cluster, where the dom0s are crosslinked via a null
> modem serial cable for heartbeat redundancy. This works most of the
> time, but the serial connection is very unreliable, dropping characters
If you use the hypervisor serial connection "console=com1 com1=11152..."
and re-route the console output in Linux kernel to it (console=hvc0)
does this problem disappear?
> all the time, with lot of messages like "ttyS0: 2 input overrun(s)" in
> dmesg. No such problem when running the same kernel on bare metal. The
> link is running at 9600 baud, so the system should easily cope, but it
> looks like the serial interrupt isn't serviced timely enough under Xen.
> I'm running Xen 4.0.1 now with kernel 2.6.32 (stock Debian squeeze), but
> the problem isn't specific to this setup, Xen 3.2 with kernel 2.6.18 had
> much the same issue. Raising dom0's scheduling weight didn't help much
> (or at all), pinning all domUs to CPU1-3 and vcpu0 of dom0 to CPU0
> actually made the problem worse.
>
> $ cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3
> 1: 9 0 0 0 xen-pirq-ioapic-edge i8042
> 4: 31712520 0 0 0 xen-pirq-ioapic-edge serial
> [...]
>
> Is there some known solution to this problem? It feels like overly big
> dom0 interrupt latency... maybe caused by the single-threaded hypervisor?
> Comments more than welcome!
> --
> Thanks,
> Feri.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-03-20 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 11:02 dom0 serial input overruns Ferenc Wagner
2011-03-20 20:43 ` Konrad Rzeszutek Wilk [this message]
2011-03-21 16:32 ` Ferenc Wagner
2011-03-22 15:27 ` Konrad Rzeszutek Wilk
2011-03-22 15:48 ` Trolle Selander
2011-03-22 22:08 ` Ferenc Wagner
2011-03-23 18:57 ` Ferenc Wagner
2011-03-24 11:54 ` Konrad Rzeszutek Wilk
2011-03-24 14:07 ` Ferenc Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110320204321.GE3948@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=wferi@niif.hu \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.