From: "Jan Kundrát" <jan.kundrat@fzu.cz>
To: aq <aquynh@gmail.com>
Cc: Mark Williamson <maw48@cl.cam.ac.uk>, xen-devel@lists.sourceforge.net
Subject: Re: Cannot connect to console?
Date: Wed, 22 Dec 2004 21:22:13 +0100 [thread overview]
Message-ID: <41C9D775.5010801@fzu.cz> (raw)
In-Reply-To: <9cde8bff041222065949b169d2@mail.gmail.com>
aq wrote:
>>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?
no. something is wrong :-). I'm not a xen developer, but I'll suggest
you to try to run xend with some debugging options...
Aren't you trying to access domain's console twice at once? I mean
console opened from "-c" option and then issuing `xend console ...`. It
shouldn't work, AFAIK.
jkt
--
cd /local/pub && more beer > /dev/mouth
-------------------------------------------------------
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/
next prev parent reply other threads:[~2004-12-22 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 2:50 Cannot connect to console? aq
2004-12-22 13:17 ` Jan Kundrát
2004-12-22 14:59 ` aq
2004-12-22 20:22 ` Jan Kundrát [this message]
2004-12-23 4:31 ` aq
2004-12-23 4:56 ` Derrik Pates
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=41C9D775.5010801@fzu.cz \
--to=jan.kundrat@fzu.cz \
--cc=aquynh@gmail.com \
--cc=maw48@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.