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 [email protected] https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
