From: Avi Kivity <avi@redhat.com>
To: Asias He <asias.hejun@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
Sasha Levin <levinsasha928@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Cyrill Gorcunov <gorcunov@gmail.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] kvm tools: Export DISPLAY ENV as our default host ip address
Date: Mon, 10 Sep 2012 11:19:04 +0300 [thread overview]
Message-ID: <504DA278.3040505@redhat.com> (raw)
In-Reply-To: <CAFO3S40DSyfHCsiezthegYmO41MyhF3RHFMfruyyHSH47YhPiw@mail.gmail.com>
On 09/10/2012 04:26 AM, Asias He wrote:
>>
>>>
>>>> Or you can
>>>> make the guest talk to an internal unix-domain socket, tunnel that
>>>> through virtio-serial, terminate virtio-serial in lkvm, and direct it
>>>> towards the local X socket.
>>>
>>> Doesn't this require some user agent or config modification to the guest?
>>
>> It does, a daemon that listens locally and forwards data over
>> virtio-serial. But you build your own initrd anyway, don't you?
>
> Using our custom init file is one use case. User may use distro disk
> image as guest also.
We could push it into the distros, it should be useful for qemu as well.
This could be done even more properly by adding support for
virtio-serial in X itself (is anything really needed on the client side?)
The only problem is that it is insecure, but maybe
http://www.nsa.gov/research/_files/selinux/papers/x11/t1.shtml can help.
I don't know if it's integrated yet.
>
>> Another option is ppp-over-virtio-serial.
>
> Seems this still uses tcp where the link layer changes from ethernet to serial.
Right, you have to terminate it on the host side without routing.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-10 8:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 11:29 [PATCH 1/2] kvm tools: Export DISPLAY ENV as our default host ip address Asias He
2012-08-24 11:29 ` [PATCH 2/2] kvm tools: Mount devpts to /dev/pts Asias He
2012-09-04 13:07 ` [PATCH 1/2] kvm tools: Export DISPLAY ENV as our default host ip address Avi Kivity
2012-09-05 6:03 ` Asias He
2012-09-05 7:56 ` Avi Kivity
2012-09-05 9:19 ` Asias He
2012-09-05 9:29 ` Avi Kivity
2012-09-05 9:46 ` Asias He
2012-09-05 9:53 ` Avi Kivity
2012-09-05 10:14 ` Asias He
2012-09-05 11:56 ` Avi Kivity
2012-09-06 3:32 ` Asias He
2012-09-06 7:59 ` Avi Kivity
2012-09-10 1:26 ` Asias He
2012-09-10 8:19 ` Avi Kivity [this message]
2012-09-05 8:00 ` Pekka Enberg
2012-09-05 8:09 ` Ingo Molnar
2012-09-05 9:16 ` Asias He
2012-09-05 9:13 ` Asias He
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=504DA278.3040505@redhat.com \
--to=avi@redhat.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
/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.