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] Cannot connect to console?

To: Jan Kundrát <jan.kundrat@xxxxxx>, Mark Williamson <Mark.Williamson@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Cannot connect to console?
From: aq <aquynh@xxxxxxxxx>
Date: Wed, 22 Dec 2004 23:59:35 +0900
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Dec 2004 15:03:04 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=WP8PQitLSCEOtVoEBtzzlxC2yDOwr2OQ50WNZfTfLkfK612G3hnKmU8fKEF/rnJHf0nOwLDNWjqjpaAzbb5uXd4F/2K+96LucH6dLOAU6mla2GCSz1kc69/8oOV83buWldh+Yj5sgTLtcXyqb1a7hSXKYHUotNKbtsv9AJ+iUOY=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <41C973D3.1040007@xxxxxx>
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>
References: <9cde8bff04122118507b161323@xxxxxxxxxxxxxx> <41C973D3.1040007@xxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > Here is how I connect to console (my Xen installation is from Xen
> > 2.0.1 binary tarball):
> > ---
> >  $ xm list
> > Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> > Domain-0           0      245    0  r----    271.4
> > tty               13       64    0  -b---      0.5    9613
> > $ xm console tty
> > ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> > Cannot connect to console 13 on domain 13
> >
> > ************ REMOTE CONSOLE EXITED *****************
> > $ xm console 13
> > ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> > Cannot connect to console 13 on domain 13
> >
> > ************ REMOTE CONSOLE EXITED *****************
> > $
> 
> what does `nc localhost 9613`? in other words, are you able to connect
> to the TCP port that console is bound to? does option "-c" for `xend
> create` work?

ah, I forgot to tell you that the problem I got was with -c option (xm
create tty.xen -c)

here is the output of my attempt to connect to tcp socket, as suggested by Jan:
---
$ nc localhost 9602
Cannot connect to console 13 on domain 2
---
as you see, the problem still occurs.

then I tried again, this time without -c option. and I was surprised
to see that "xm console tty" works (!!).

so I conclude that this is the expected behaviour of Xen: if I want to
connect to console with "xm console", then I must not use "-c" option?

Thank you,
AQ


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel