From: Nikita A Menkovich <menkovich@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: libvirt-users@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [libvirt-users] SSH console for qemu
Date: Fri, 8 Jul 2011 00:55:08 +0400 [thread overview]
Message-ID: <CAGjwFiP5K+Ody0xhf8PTYmUCUkW7Psapz3EOiho+N_bbCCrmhQ@mail.gmail.com> (raw)
In-Reply-To: <4E15F8CB.1010404@redhat.com>
I want to launch very minimal ssh daemon (that listen on selected port
and allows only input commands and read output from console) that
launch when guest started, and this not run inside a guest.
Thanks to the link for patch
On 7 July 2011 22:19, Eric Blake <eblake@redhat.com> wrote:
> On 07/07/2011 02:36 AM, Nikita A Menkovich wrote:
>> 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.
>
> If you're trying to capture boot events, then you have to have an SGA
> (serial graphics adaptor) capable BIOS that can output boot events on
> the serial console. There's recent work underway to add that feature to
> qemu, and to expose that feature from libvirt:
>
> https://www.redhat.com/archives/libvir-list/2011-July/msg00174.html
>
> Setting up an ssh daemon in the guest is too late - the daemon won't be
> set up until the guest has already booted, so there's no way to have
> that daemon forward boot messages back to the host in a timely manner.
> I think you're trying too hard - 'virsh console' really is the way to
> read all messages output to the guest's console, and your only missing
> piece is that you also appear to want BIOS to output to the console.
>
> --
> Eric Blake eblake@redhat.com +1-801-349-2682
> Libvirt virtualization library http://libvirt.org
>
>
--
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 20:55 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
2011-07-07 18:19 ` [Qemu-devel] [libvirt-users] " Eric Blake
2011-07-07 20:55 ` Nikita A Menkovich [this message]
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=CAGjwFiP5K+Ody0xhf8PTYmUCUkW7Psapz3EOiho+N_bbCCrmhQ@mail.gmail.com \
--to=menkovich@gmail.com \
--cc=eblake@redhat.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).