From: Nikita A Menkovich <menkovich@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: libvirt-users@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SSH console for qemu
Date: Thu, 7 Jul 2011 12:36:28 +0400 [thread overview]
Message-ID: <CAGjwFiM-mx51wxnVG2V2p7dDGJ+W7bJzN4ONbue+MRLqFki2OQ@mail.gmail.com> (raw)
In-Reply-To: <CAJSP0QU7JJ1QS9ZK9Gxh7eK=xjHBMvnSJfR7NhdL93JMe00PTg@mail.gmail.com>
Seems no, I think, that the best way is running some kind of ssh
daemon, that connects to console (/dev/vcsa1 for example), that listen
on port and send to output console events on boot, and allow to work
with server with simple ssh client. Also important feature will be
saving history of output.
On 6 July 2011 19:27, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Wed, Jul 6, 2011 at 3:08 PM, Nikita A Menkovich <menkovich@gmail.com> wrote:
>> I'm using qemu with libvirt and I want to create SSH emergency console
>> to linux/unix guests, same way as it is realized in qemu VNC.
>> Maybe someone could help me to determine a place to dive in this question.
>>
>> I think the best way to make it - extend qemu API. But if this could
>> be made with libvirt - this will be also fine.
>
> Serial console and the "virsh console" command?
>
> Stefan
>
--
Nikita A Menkovich
http://libc6.org/
JID: menkovich@gmail.com
Tel: +7 (921) 423-96-48
next prev parent reply other threads:[~2011-07-07 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 14:08 [Qemu-devel] SSH console for qemu Nikita A Menkovich
2011-07-06 15:27 ` Stefan Hajnoczi
2011-07-07 8:36 ` Nikita A Menkovich [this message]
2011-07-07 18:19 ` [Qemu-devel] [libvirt-users] " Eric Blake
2011-07-07 20:55 ` Nikita A Menkovich
2011-07-07 18:47 ` [Qemu-devel] " Stefan Hajnoczi
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=CAGjwFiM-mx51wxnVG2V2p7dDGJ+W7bJzN4ONbue+MRLqFki2OQ@mail.gmail.com \
--to=menkovich@gmail.com \
--cc=libvirt-users@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).