When adding the keyword serial="pty" to a xen cfg file, I am able to open /dev/ttyS0 in my dom-U linux kernel environment and send serial data to a /dev/pts/x port in my dom-0 linux environment. If I happen to have have multiple dom-U''s configured this way, what is the best way to determine how these ports will be mapped so I will know which /dev/pts port belongs to which dom-U''s /dev/ttyS0 port? Thanks, Larry White
On Tue, Jul 31, 2012 at 11:08:41PM +0000, lmw@satx.rr.com wrote:> When adding the keyword serial="pty" to a xen cfg file, I am able to open /dev/ttyS0 in my dom-U linux kernel environment and send serial data to a /dev/pts/x port in my dom-0 linux environment. If I happen to have have multiple dom-U''s configured this way, what is the best way to determine how these ports will be mapped so I will know which /dev/pts port belongs to which dom-U''s /dev/ttyS0 port? >You can see that info at least from xenstore, dunno if there are other ways.. -- Pasi
On Wed, 2012-08-01 at 09:27 +0100, Pasi Kärkkäinen wrote:> On Tue, Jul 31, 2012 at 11:08:41PM +0000, lmw@satx.rr.com wrote: > > When adding the keyword serial="pty" to a xen cfg file, I am able to open /dev/ttyS0 in my dom-U linux kernel environment and send serial data to a /dev/pts/x port in my dom-0 linux environment. If I happen to have have multiple dom-U's configured this way, what is the best way to determine how these ports will be mapped so I will know which /dev/pts port belongs to which dom-U's /dev/ttyS0 port? > > > > You can see that info at least from xenstore, dunno if there are other ways..If you are using xl the "xl console <dom>" will get you the serial console by default (use -t option to force). I don't know if "xm console" had the same behaviour. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel