From: Gerd Hoffmann <kraxel@bytesex.org>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] uml FB
Date: Mon, 03 Dec 2007 10:38:22 +0100 [thread overview]
Message-ID: <4753CE8E.9030305@bytesex.org> (raw)
In-Reply-To: <4752C626.4050000@nagafix.co.uk>
Antoine Martin wrote:
> This would allow the guest to have a framebuffer and if we need to
> actually see its contents, it could easily be exposed using shared
> memory. This would completely de-couple the framebuffer from the host,
> allowing us to attach/detach as needed: start session, detach, log out
> of X, log in, attach to guest framebuffer (although this doesn't address
> the mouse/keyboard issue).
Havn't looked at it for ages. Should be doable though. Note just some
shared memory area isn't enougth, you need also some channel for screen
updates (guest->host) and mouse/kbd events (host->guest). One possible
approach would be coding up a vnc server, so you can use any vnc client
to see the uml framebuffer and talk to the virtual machine. This would
also allow remote access to the display. uml-x11-fb never worked with a
remote display, probably because it grooks when it can't write to the
X11 socket buffer, which quickly happens without the MIT-SHM extention.
cheers,
Gerd
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2007-12-03 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 14:50 [uml-devel] uml FB Antoine Martin
2007-12-03 9:38 ` Gerd Hoffmann [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=4753CE8E.9030305@bytesex.org \
--to=kraxel@bytesex.org \
--cc=antoine@nagafix.co.uk \
--cc=user-mode-linux-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.