From: Anthony Liguori <anthony@codemonkey.ws>
To: xen-devel@lists.xensource.com
Subject: Re: Multiple PVM consoles
Date: Fri, 15 Sep 2006 08:55:18 -0500 [thread overview]
Message-ID: <pan.2006.09.15.13.55.16.458198@codemonkey.ws> (raw)
In-Reply-To: 60D45469A1AAD311A04C009027B6BF6805FE0237@server20.inside.oracorp.com
On Thu, 14 Sep 2006 11:21:59 -0400, Steve Brueckner wrote:
> A colleague of mine asked this question on xen-users, but it may be more
> of a developer question. We need to make multiple independent console
> connections to a paravirtualized VM (not 2 windows sharing a single
> console), and without using the network (no telnet or ssh solutions).
> Searching the archives I've found about 6 threads discussing this, among
> them:
>
> This one, which says it was on the roadmap for versions 2 and/or 3:
> http://lists.xensource.com/archives/html/xen-devel/2006-07/msg00424.html
>> [quoted text muted]
>
> And these, opening the possibility of 2 consoles (on the paravirt
> framebuffer and on a virtual serial port):
> http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00170.html
> http://lists.xensource.com/archives/html/xen-devel/2006-09/msg00072.html
>
> Can anyone tell me if and when it will be possible to get 2 independent
> consoles into a paravirtualized guest? Or will the kernel always have
> only one input/output stream, resulting in behavior similar to the
> "multiple windows to a shared console" scenario we have now?
This feature has been discussed repeated but AFAIK noone has stepped up to
actually implement it.
Regards,
Anthony Liguori
> Thanks,
>
> - Steve
>
> Stephen Brueckner, ATC-NY
prev parent reply other threads:[~2006-09-15 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 15:21 Multiple PVM consoles Steve Brueckner
2006-09-15 13:55 ` Anthony Liguori [this message]
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=pan.2006.09.15.13.55.16.458198@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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.